<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;Dk4BQXw9fCp7ImA9WxBWE0o.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580</id><updated>2010-02-05T21:02:30.264+08:00</updated><title>Eon Security Blog</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.eonsec.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>44</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EonSecurityBlog" /><feedburner:info uri="eonsecurityblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><entry gd:etag="W/&quot;DEMDRng8fip7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-8395501505695049831</id><published>2008-03-13T16:03:00.006+08:00</published><updated>2008-12-09T15:07:57.676+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:57.676+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="dns" /><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><category scheme="http://www.blogger.com/atom/ns#" term="ssl" /><category scheme="http://www.blogger.com/atom/ns#" term="web" /><title>MITM, almost: Redux</title><summary>Apparently one of my OpenWRT boxes still uses OpenDNS. I was checking my Godaddy account then a Mozilla Firefox security error popped up. Note the https at the end of the host.I didn't accept the certificate since I was already logged in. Unfortunately it didn't happen again so I was not able to verify. Was it a one time or erratic glitch? I'm not very sure who is at fault here, Godaddy or </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=8395501505695049831" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/8395501505695049831?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/8395501505695049831?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/mitm-almost-redux.html" title="MITM, almost: Redux" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_gScM6JZQQqQ/R9jgz53wL0I/AAAAAAAAAJY/DuclZy24hoo/s72-c/god1.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;D0QHQns_eSp7ImA9WxZWEk4.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-5786915456764094094</id><published>2008-03-10T12:13:00.014+08:00</published><updated>2008-03-11T19:35:33.541+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-11T19:35:33.541+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="gcc" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="icc" /><category scheme="http://www.blogger.com/atom/ns#" term="vulndev" /><title>ICC stack-security-check</title><summary>Recently I've been playing with the Intel C++/C Compiler. Code produced by the compiler reportedly are optimized better than GCC's. I'd say it's overrated and only gives perceived speed increase for common use. I noticed that by default it produces AT&amp;T assembly instead of Intel. Anyway, I'm more interested in its security feature.$ icc -help...-fstack-security-check              enable overflow </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=5786915456764094094" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5786915456764094094?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5786915456764094094?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/icc-stack-security-check.html" title="ICC stack-security-check" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDRnc5fyp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-691142637150184982</id><published>2008-03-07T15:35:00.014+08:00</published><updated>2008-12-09T15:07:57.927+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:57.927+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ddos" /><category scheme="http://www.blogger.com/atom/ns#" term="gambling" /><title>DDoS progress</title><summary>The Gala Coral Group reported that last year their gambling sites got hit by a 10Gb DDoS attack. The Information Security Officer spoke at the recently concluded e-Crime Congress 2008. I'm not sure of the exaggerations but an interesting part is:Attackers disguised the build up of traffic from up to 30,000 PC and Apple Mac botnet computers during the attack by analysing and reproducing the </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=691142637150184982" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/691142637150184982?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/691142637150184982?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/ddos-progress.html" title="DDoS progress" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/__leF4OjbGPE/R9D3-lXjdEI/AAAAAAAAACY/2IEBjsReGQE/s72-c/DevilJoker.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSX4-eip7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-3777543813142369169</id><published>2008-03-07T00:29:00.006+08:00</published><updated>2008-12-09T15:07:58.052+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:58.052+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web" /><category scheme="http://www.blogger.com/atom/ns#" term="pwned" /><title>Recycle</title><summary>Easily recycle thousands of compromised boxes using these easy stepsSearch for commonly used defacer messagesPick a defaced siteFind out how they got inPatch the entrance (optional)RepeatBecause of forgotten web applications lying around web directories not updated those steps can be very effective. Some defacements can go undetected for many years. If someone can create or edit files in web </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=3777543813142369169" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/3777543813142369169?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/3777543813142369169?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/recycle.html" title="Recycle" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/__leF4OjbGPE/R9AlYFXjdCI/AAAAAAAAACI/9hf_kHP-NZ0/s72-c/recycling.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEIGSHwyfCp7ImA9WxZXFkU.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-4813129604113942581</id><published>2008-03-04T11:05:00.009+08:00</published><updated>2008-03-05T11:08:49.294+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-05T11:08:49.294+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="dns" /><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><category scheme="http://www.blogger.com/atom/ns#" term="ssl" /><title>MITM, almost</title><summary>Yesterday I wanted to check my bank balance. Clicked on the my bank's ebanking interface but I was presented to what looks like a self-signed certificate warning. Not a good sign as this means a possible MITM. For comparison the self-signed certificate is here. A legit certificate from the bank is here.I proceed to accept the self-signed certificate to see if it's really a MITM. To my </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=4813129604113942581" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4813129604113942581?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4813129604113942581?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/mitm-almost.html" title="MITM, almost" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DEMDSXg9fSp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7053059578246228670</id><published>2008-03-03T13:20:00.012+08:00</published><updated>2008-12-09T15:07:58.665+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:58.665+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="openbsd" /><category scheme="http://www.blogger.com/atom/ns#" term="pax" /><title>Holes</title><summary>A week ago the OpenBSD 4.2 errata page have been updated with two fixes or vulnerabilities, depending on who you ask. In case you are not aware, OpenBSD doesn't have formal or official security advisories. You have to check the errata page for security vulnerabilities.008: RELIABILITY FIX: February 25, 2008 All architecturesMalformed IPv6 routing headers can cause a kernel panic.007: RELIABILITY </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7053059578246228670" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7053059578246228670?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7053059578246228670?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/holes.html" title="Holes" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/__leF4OjbGPE/R8vJcP2NE2I/AAAAAAAAABg/EbBZJdDp31g/s72-c/holes.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSXY9cSp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-2201804224052724435</id><published>2008-03-01T14:25:00.008+08:00</published><updated>2008-12-09T15:07:58.869+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:58.869+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><title>Violent Upgrade Cycle</title><summary>A RedHat fan visited the NASA Telescience Lab to check out the RHEL and Fedora Core installations. One of the pictures caught my attention.If it ain't broke, don't upgrade it, right? Actually one of the guys in the lab told me they are in the process of upgrading to Fedora 8 and playing with 9 alpha.This machine is possibly http://countdown.ksc.nasa.gov/. I'm not sure what's their policy for </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=2201804224052724435" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2201804224052724435?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2201804224052724435?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/03/violent-upgrade-cycle.html" title="Violent Upgrade Cycle" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_gScM6JZQQqQ/R8kCoODxjoI/AAAAAAAAAJQ/i2_quFR5blY/s72-c/Fedora4-NASA.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;D08GR3o4fSp7ImA9WxZXE0g.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7408140051738811447</id><published>2008-02-29T22:31:00.005+08:00</published><updated>2008-03-01T15:17:06.435+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-01T15:17:06.435+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><category scheme="http://www.blogger.com/atom/ns#" term="mac" /><category scheme="http://www.blogger.com/atom/ns#" term="fraud" /><title>Big Mac</title><summary>PayPal warns against using Apple's Safari:Safari doesn't make PayPal's list of recommended browsers because it doesn't have two important anti-phishing security features, according to Michael Barrett, PayPal's chief information security officer.A perfectly valid reasoning. A couple of Mac users cannot seem to understand the precaution suggested.In other news, Apple customer service </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7408140051738811447" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7408140051738811447?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7408140051738811447?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/big-mac.html" title="Big Mac" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CEcCRng_cSp7ImA9WxZXEUU.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7618177979145905959</id><published>2008-02-28T13:57:00.004+08:00</published><updated>2008-02-28T15:01:07.649+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-28T15:01:07.649+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tcp" /><title>Revisiting OOB</title><summary>I was reading the entry for TCP at Wikipedia, one thing that caught my attention is the description of Out of Band data. The verbatim description:You are able to interrupt or abort the queued stream instead of waiting for the stream to finish. This is done by specifying the data as urgent. This will tell the receiving program to process it immediately, along with the rest of the urgent data. When</summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7618177979145905959" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7618177979145905959?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7618177979145905959?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/revisiting-oob.html" title="Revisiting OOB" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSXcyeCp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-4374668133245899558</id><published>2008-02-26T11:53:00.011+08:00</published><updated>2008-12-09T15:07:58.990+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:58.990+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="vm" /><title>Point and Click Trojan</title><summary>SharK definitely dumbs down Trojan creation, requires no programming skill at all. It allows for the creation of malware with features such as:encryptionpolymorphismcustom payloadsvirtual machine detectioncompressiondebugger detectionpassword miningremote managementsoftware inventoryactive process and network connection informationcapture desktop and webcam imagesrecord audiolog keystrokesanalyze</summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=4374668133245899558" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4374668133245899558?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4374668133245899558?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/point-and-click-trojan.html" title="Point and Click Trojan" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_gScM6JZQQqQ/R8OalwkFwiI/AAAAAAAAAI4/WQmi0Tlhfkw/s72-c/sharksplash.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;AkcCQHk7eyp7ImA9WxZQF08.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-5450321223007862554</id><published>2008-02-23T08:20:00.003+08:00</published><updated>2008-02-23T08:54:21.703+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-23T08:54:21.703+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><title>Posix File Capabilities</title><summary>I mentioned before that suid binaries are getting scarce. In Linux, since 2.6.19-rc5-mm2 posix file capabilities are implemented. It was introduced into mainline in 2.6.24-rc2.As an example let's look at the ping program, as you may know ping needs CAP_NET_RAW to generate raw packets and the old practice is to make the ping executable binary suid root. Tinyping is a small assembly version of ping</summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=5450321223007862554" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5450321223007862554?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5450321223007862554?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/posix-file-capabilities.html" title="Posix File Capabilities" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;C0QARHc9cSp7ImA9WxZQFko.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-4914032795121685822</id><published>2008-02-21T11:50:00.008+08:00</published><updated>2008-02-22T17:09:05.969+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-22T17:09:05.969+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ddos" /><category scheme="http://www.blogger.com/atom/ns#" term="gambling" /><title>Post Valentine DDoS</title><summary>As seen from various sources such as Arbor, Shadowserver and a couple of gambling sites, DDoS is back in the limelight. Gambling sites were getting hit since around Valentine's day.I've noticed small 12-hour attacks from Feb 13-15 on a couple of gambling sites hosted here in the Philippines. I reckon the attack is not directed to the sites I'm monitoring but is getting affected by attacks on </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=4914032795121685822" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4914032795121685822?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/4914032795121685822?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/post-valentine-ddos.html" title="Post Valentine DDoS" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Dk4DQHk9fSp7ImA9WxZQFEQ.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7201285388311755774</id><published>2008-02-20T10:53:00.007+08:00</published><updated>2008-02-20T16:09:31.765+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-20T16:09:31.765+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="offbeat" /><category scheme="http://www.blogger.com/atom/ns#" term="advisory" /><category scheme="http://www.blogger.com/atom/ns#" term="microsoft" /><title>No credit = exploit</title><summary>Because Microsoft refused to credit the researcher who reported MS08-011/CVE-2008-0108 a corresponding exploit was publicly released. A person or group going by the name chujwamwdupe chujwamwdupe posted the exploit to Full-disclosure.Unfortunately, Microsoft has refused to credit you using the name you requested.I think there's a mixup in the iDefense Labs advisory, unless sillypea is </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7201285388311755774" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7201285388311755774?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7201285388311755774?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/no-credit-exploit.html" title="No credit = exploit" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;CkIDR3s4eSp7ImA9WxZQE0o.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7523660069643522159</id><published>2008-02-18T14:42:00.020+08:00</published><updated>2008-02-19T05:36:16.531+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-19T05:36:16.531+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ddos" /><category scheme="http://www.blogger.com/atom/ns#" term="games" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="vm" /><category scheme="http://www.blogger.com/atom/ns#" term="botnets" /><title>Top 10 Podcast Episodes</title><summary>Over the years I have compiled my favorite security podcast episodes. Here is my list of top ten shows. Most of these episodes are interviews. Here they are in no particular order:The Silver Bullet Security Podcast, Show 013 - An Interview with Ross Anderson Gary McGraw interviews Ross Anderson author of the book Security Engineering. He is one of the researchers in the Security Group at the </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7523660069643522159" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7523660069643522159?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7523660069643522159?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/top-10-podcast-episodes.html" title="Top 10 Podcast Episodes" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;Ck4GQ304eyp7ImA9WxZQEUo.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-7474762601015317572</id><published>2008-02-16T17:48:00.006+08:00</published><updated>2008-02-16T22:08:42.333+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-16T22:08:42.333+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="rant" /><category scheme="http://www.blogger.com/atom/ns#" term="offbeat" /><category scheme="http://www.blogger.com/atom/ns#" term="dns" /><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><title>OpenDNS proxying</title><summary>An old issue but new to me. Their supposed to be reason for doing this is ridiculous. $ dig @resolver1.opendns.com www.google.com; &lt;&lt;&gt;&gt; DiG 9.4.1-P1 &lt;&lt;&gt;&gt; @resolver1.opendns.com www.google.com; (1 server found);; global options:  printcmd;; Got answer:;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 3375;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;</summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=7474762601015317572" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7474762601015317572?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/7474762601015317572?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/opendns-proxying.html" title="OpenDNS proxying" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;C04GQn05fCp7ImA9WxZQEUk.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-3013972041118919090</id><published>2008-02-16T11:19:00.013+08:00</published><updated>2008-02-16T14:05:23.324+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-16T14:05:23.324+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="freebsd" /><category scheme="http://www.blogger.com/atom/ns#" term="dragonfly" /><category scheme="http://www.blogger.com/atom/ns#" term="advisory" /><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="openbsd" /><title>Coredumps</title><summary>I noticed a design error similar to CVE-2007-6206 in DragonFly BSD. It is reported that OpenBSD and FreeBSD exhibit the same.   &lt;!-- &gt; id                                              uid=1001(user) gid=1001(user) groups=1001(user), 0(wheel)&gt; ./coredumperSegmentation fault (core dumped)syslog: Feb 16 09:40:22  kernel: pid 723 (coredumper),                          uid 1001: exited on signal 11 (</summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=3013972041118919090" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/3013972041118919090?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/3013972041118919090?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/coredumps_16.html" title="Coredumps" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSHw7fSp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-5743911824736026798</id><published>2008-02-13T16:57:00.011+08:00</published><updated>2008-12-09T15:07:59.205+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:59.205+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="offbeat" /><category scheme="http://www.blogger.com/atom/ns#" term="fraud" /><title>Have you seen her?</title><summary>If you ask me I have seen her countless times. I don't know her name and maybe she doesn't know she's very popular. If you don't know what I'm talking about read up on domaining and click fraud.Domaining is the business of acquiring domains for no actual use besides generating revenue through pay per click advertisements. Generic domains and domains that has been deleted but still retains </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=5743911824736026798" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5743911824736026798?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5743911824736026798?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/have-you-seen-her.html" title="Have you seen her?" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/__leF4OjbGPE/R7K5GyGcLkI/AAAAAAAAAA8/Zk0brHdpW44/s72-c/0012_female_student.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DEMDSHg5fip7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-673956072463388782</id><published>2008-02-12T10:17:00.000+08:00</published><updated>2008-12-09T15:07:59.626+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:59.626+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><category scheme="http://www.blogger.com/atom/ns#" term="pax" /><title>KERNEXEC vs CVE-2008-0600</title><summary>Besides ensuring that no untrusted user can execute arbitrary files via access control, rudimentary Unix permissions and TPE (Trusted Path Execution) PaX is effective in defeating some kernel exploits. PaX KERNEXEC is enough for mitigating the recently disclosed vmsplice() vulnerability specifically CVE-2008-0600. The exploit is reported to work since Linux 2.6.17. Here's the exploit ran on </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=673956072463388782" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/673956072463388782?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/673956072463388782?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/kernexec-vs-cve-2008-0600.html" title="KERNEXEC vs CVE-2008-0600" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/13917524490205842817</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="06376706739708101684" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/__leF4OjbGPE/R7Ep4SGcLiI/AAAAAAAAAAs/HMvxHXMW3mY/s72-c/1.gif" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;C0UAQnY8fCp7ImA9WxZQEU4.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-9118933173322463292</id><published>2008-02-11T12:13:00.001+08:00</published><updated>2008-02-16T11:07:23.874+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-16T11:07:23.874+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="advisory" /><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><title>Reliable root since 2006</title><summary>A couple of advisories detailing local privilege escalation vulnerabilities in the Linux kernel has been published. The CVE entries for these vulnerabilities are:CVE-2008-0009CVE-2008-0010CVE-2008-0600Both CVE-2008-0009 and CVE-2008-0010 was fixed upstream on February 8 with the following commit message:splice: missing user pointer access verificationvmsplice_to_user() must always check the user </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=9118933173322463292" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/9118933173322463292?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/9118933173322463292?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/reliable-root-since-2006.html" title="Reliable root since 2006" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;DEMDSHk-eip7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-2035925206787211034</id><published>2008-02-09T19:21:00.000+08:00</published><updated>2008-12-09T15:07:59.752+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:59.752+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><title>Amateur Malware Analysis</title><summary>A friend asked me to check his USB drive because it was not working. I attached it to my notebook and mounted it. Seems fine, I can access his files plus a bonus suspicious executable with a blurry folder icon. Apparently the USB port he was attaching the drive to is not working. I copied the executable and the autorun.ini from his drive.It's a Satuday evening and I have some time to spare so I </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=2035925206787211034" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2035925206787211034?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2035925206787211034?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/amateur-malware-analysis.html" title="Amateur Malware Analysis" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_gScM6JZQQqQ/R62i3QkFwfI/AAAAAAAAAIc/BhD-HTYZQJA/s72-c/scvhost.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSHY6fyp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-8881255461537275105</id><published>2008-02-06T16:51:00.000+08:00</published><updated>2008-12-09T15:07:59.817+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:59.817+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="web" /><title>Cheating the cheaters</title><summary>Web application security has a simple rule: "Never trust user input". This applies not only to applications but also games. Flash games are hard to secure and be made cheat-proof. It's like creating a JavaScript game and trusting the results from it. You should also take care of how the results are entered into your system.AkoModelo is a Filipino social networking website similar to MySpace, </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=8881255461537275105" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/8881255461537275105?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/8881255461537275105?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/cheating-cheaters.html" title="Cheating the cheaters" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_gScM6JZQQqQ/R6l6fg1ViZI/AAAAAAAAAIU/XHNQghlERmQ/s72-c/camgirl_100points.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;Ck4DRH08fip7ImA9WxZREUw.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-5526262571998847582</id><published>2008-02-04T15:28:00.000+08:00</published><updated>2008-02-04T15:42:55.376+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-04T15:42:55.376+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="netbsd" /><title>NetBSD security features</title><summary>The last NetBSD release I used was 3.0. Since then a couple of security mechanisms have been implemented and improved. In the recently released NetBSD 4.0 these are: kauthPaX mprotectfileassocThe kernel authorization framework or simply kauth(9) first appeared in Mac OS X 10.4 Tiger and later adapted by NetBSD. It was designed to implement access control lists (ACL). With kauth(9) you can create </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=5526262571998847582" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5526262571998847582?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5526262571998847582?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/netbsd-security-features.html" title="NetBSD security features" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDSHc-eyp7ImA9WxRbGE0.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-5450169436820393069</id><published>2008-02-02T16:42:00.000+08:00</published><updated>2008-12-09T15:07:59.953+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-09T15:07:59.953+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="games" /><category scheme="http://www.blogger.com/atom/ns#" term="analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="windows" /><category scheme="http://www.blogger.com/atom/ns#" term="web" /><title>Tongits is in the AIR</title><summary>Somebody made a card game that runs on Adobe AIR. Tongits is a popular card game played for pastime and also for gambling here in the Philippines. It is played like Mahjong with card rules similar to poker.What is the Adobe Integrated Runtime:Adobe® AIR lets developers use their existing web development skills in HTML, AJAX, Flash and Flex to build and deploy rich Internet applications to the </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=5450169436820393069" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5450169436820393069?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/5450169436820393069?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/02/tongits-is-in-air.html" title="Tongits is in the AIR" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_gScM6JZQQqQ/R6Q1ow1ViSI/AAAAAAAAAHc/YweMXeu2IMo/s72-c/tongits0.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total></entry><entry gd:etag="W/&quot;CkUERXcyfip7ImA9WxZSF0U.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-2315206522332489501</id><published>2008-01-31T19:37:00.000+08:00</published><updated>2008-01-31T19:50:04.996+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-31T19:50:04.996+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="rant" /><title>All bets are off</title><summary>I often hear or read this: if the user gets a shell all bets are off I find this claim ridiculous because it would only apply to improperly secured systems. The old folks would say that admin errors, programs ran as root and suid binaries (these are becoming scarce) are popular ways of getting root. If it is still the '90s I would agree. On recent systems there exist security mechanisms that a </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=2315206522332489501" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2315206522332489501?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/2315206522332489501?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/01/all-bets-are-off.html" title="All bets are off" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;CEcGQnc9eSp7ImA9WxZXEUU.&quot;"><id>tag:blogger.com,1999:blog-1057558964381897580.post-629460278079167658</id><published>2008-01-29T23:56:00.001+08:00</published><updated>2008-02-28T15:00:23.961+08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-28T15:00:23.961+08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="glibc" /><category scheme="http://www.blogger.com/atom/ns#" term="analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="gcc" /><category scheme="http://www.blogger.com/atom/ns#" term="linux" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="vulndev" /><title>SSP and _FORTIFY_SOURCE</title><summary>For overflow protection Stack Smashing Protector (formerly known as ProPolice) and _FORTIFY_SOURCE are two of the most prevalent extensions for GCC and Glibc. Both are independent of each other so they can be used together for an insanely paranoid setup.Here is a sample code which is easily overflowed.#include &lt;stdio.h&gt;#include &lt;stdlib.h&gt;#include &lt;string.h&gt;int main(int argc,char *argv[]) {  char </summary><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=1057558964381897580&amp;postID=629460278079167658" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/629460278079167658?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1057558964381897580/posts/default/629460278079167658?v=2" /><link rel="alternate" type="text/html" href="http://blog.eonsec.com/2008/01/ssp-and-fortifysource.html" title="SSP and _FORTIFY_SOURCE" /><author><name>Eduardo Tongson</name><uri>http://www.blogger.com/profile/10713501272894716059</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03419616053703054335" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry></feed>
