<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-9881230</id><updated>2012-01-22T17:16:25.173-05:00</updated><title type='text'>Blog on Cyberterror</title><subtitle type='html'>Blogging on Security efforts in Open Source Software</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>32</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9881230.post-113774490744745943</id><published>2006-01-20T02:45:00.000-05:00</published><updated>2006-01-20T03:15:07.460-05:00</updated><title type='text'>Project Eva</title><summary type='text'>
I've began work on "Project Eva," a personal project to design a new, secure Linux distribution.  This is not a typical distribution; it will base neither on Red Hat, Gentoo, or Debian GNU/Linux.  Instead, I will be building from the ground up, using a package manager I'm designing and coding myself in a project called "Project Coon Fox."



Project Eva will not be a simple hack-up job of </summary><link rel='related' href='http://www.google.com/' title='Project Eva'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/113774490744745943/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=113774490744745943' title='41 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/113774490744745943'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/113774490744745943'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2006/01/project-eva.html' title='Project Eva'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>41</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112909909555577050</id><published>2005-10-12T02:14:00.000-04:00</published><updated>2005-10-12T02:39:18.456-04:00</updated><title type='text'>Java v. C continued</title><summary type='text'>
Looks like I got slashdotted on that one.  I wasn't trying to particularly bash Java, more the concept of one language being "secure" over another.  Java just makes a good example of a language people believe will solve all their problems for them.



With the responses I've seen both here and on slashdot, I feel I should make a follow-up post.  I'll point out a few interesting things that have </summary><link rel='related' href='http://it.slashdot.org/article.pl?sid=05/10/10/110239&amp;tid=172' title='Java v. C continued'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112909909555577050/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112909909555577050' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112909909555577050'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112909909555577050'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/10/java-v-c-continued.html' title='Java v. C continued'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112893085481804046</id><published>2005-10-06T17:46:00.000-04:00</published><updated>2005-10-10T14:12:18.730-04:00</updated><title type='text'>Security in a language?</title><summary type='text'>
Lately I've taken more notice into the debates over programming languages.  People often claim that Java is inherently more secure than C; C is faster than Java; C++ is easier than C; C++ is slow and has an over-bloated syntax that makes it confusing; or any number of other things about languages.  Looking at C and Java, I'd like to make a quick point.



In gcc 4.1, a re-implementation of </summary><link rel='related' href='http://www.grsecurity.net/' title='Security in a language?'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112893085481804046/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112893085481804046' title='10 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112893085481804046'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112893085481804046'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/10/security-in-language.html' title='Security in a language?'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>10</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112753883688465837</id><published>2005-09-24T00:57:00.000-04:00</published><updated>2005-09-24T01:14:08.206-04:00</updated><title type='text'>Virtual worlds</title><summary type='text'>
Here's a question.  If you found a virtual world in a video game, would you think much of what you did in it?  What if you found a computer in the virtual world?  What if that computer ran like an actual computer and you were able to get X up and run OpenOffice.org?



I wonder, really I do, about the implications of a computer game that would spawn computers inside it using, say, a hypervisor </summary><link rel='related' href='http://www.planeshift.it/' title='Virtual worlds'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112753883688465837/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112753883688465837' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112753883688465837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112753883688465837'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/09/virtual-worlds.html' title='Virtual worlds'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112657819830001382</id><published>2005-09-12T22:13:00.000-04:00</published><updated>2005-09-12T22:26:08.060-04:00</updated><title type='text'>Revisiting copy protection...</title><summary type='text'>
I e-mailed the MPAA today on their Report Piracy Hotline about copy protection.  Pretty much, I'm annoyed by it, and it's useless.  Now we all should know that any copy protection can be broken; and track records for breaking it typically range from several months before a copy protection method is deployed in a product to a few weeks after something on the market uses it.  Millions of dollars </summary><link rel='related' href='http://www.mpaa.org/' title='Revisiting copy protection...'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112657819830001382/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112657819830001382' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112657819830001382'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112657819830001382'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/09/revisiting-copy-protection.html' title='Revisiting copy protection...'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112588094104332157</id><published>2005-09-04T19:54:00.000-04:00</published><updated>2005-09-08T12:30:53.330-04:00</updated><title type='text'>Mozilla and Firefox dumping SSL2.0</title><summary type='text'>
Well, it looks like Mozilla is dumping SSL2.0, and with that comes the loss of SSL2.0 in Firefox as well.  This means supporting code will be gone, and a very few sites will break; but fortunately, most sites support SSL3.0.



I say good riddance to bad rubbish, and may it rot in Hell forever.  Some info about SSL2.0, it can be attacked a lot easier than SSL3.0.  A man-in-the-middle attack can </summary><link rel='related' href='http://www.mozillazine.org/talkback.html?article=7252' title='Mozilla and Firefox dumping SSL2.0'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112588094104332157/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112588094104332157' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112588094104332157'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112588094104332157'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/09/mozilla-and-firefox-dumping-ssl20.html' title='Mozilla and Firefox dumping SSL2.0'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112347528171639441</id><published>2005-08-07T23:02:00.000-04:00</published><updated>2005-08-08T00:28:01.736-04:00</updated><title type='text'>Zombie Hacker Survival!</title><summary type='text'>
I have just read Jon Erickson's excellent book, Hacking:  The Art of Exploitation published by No Starch Press; followed closely by Max Brooks' The Zombie Survival Guide:  Complete Protection from the Living Dead published by Three Rivers Press.  Coming from someone who hates reading books, these are two select reads.  The first was a detailed but introductory technical reference on exploiting </summary><link rel='related' href='http://en.wikipedia.org/wiki/Hacking:_The_Art_of_Exploitation' title='Zombie Hacker Survival!'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112347528171639441/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112347528171639441' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112347528171639441'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112347528171639441'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/08/zombie-hacker-survival.html' title='Zombie Hacker Survival!'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112345646885799518</id><published>2005-08-07T19:01:00.000-04:00</published><updated>2005-08-07T19:14:28.866-04:00</updated><title type='text'>Phresh Phish</title><summary type='text'>
I recently posted a bug on mozdev about TrustBar.  TrustBar is an anti-phishing toolbar that tells you when the current loaded https:// page is using a valid certificate; who verified it; and who it was verified as.  This means that when you log into something like eBay or ThinkGeek, you're told that you are indeed logging into them.



What TrustBar will not do is check who a regular http:// </summary><link rel='related' href='http://bugzilla.mozdev.org/show_bug.cgi?id=11160' title='Phresh Phish'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112345646885799518/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112345646885799518' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112345646885799518'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112345646885799518'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/08/phresh-phish.html' title='Phresh Phish'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-112321717803637518</id><published>2005-08-04T23:13:00.000-04:00</published><updated>2005-08-05T00:46:18.043-04:00</updated><title type='text'>I Will Be Out of the Office</title><summary type='text'>
I haven't blogged in a long time.  I guess I should have caught up with this blog with the recent goings on, specifically the OK to commit that a cleaned-up version of ProPolice, the IBM stack smash protector research project, got from the gcc mailing list.



As of late I've been working and not working (depending on mood) on a paper about designing a secure and user friendly operating system.</summary><link rel='related' href='http://gcc.gnu.org/ml/gcc-patches/2005-07/msg00069.html' title='I Will Be Out of the Office'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/112321717803637518/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=112321717803637518' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112321717803637518'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/112321717803637518'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/08/i-will-be-out-of-office.html' title='I Will Be Out of the Office'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-111904247607511284</id><published>2005-06-17T17:07:00.000-04:00</published><updated>2005-06-17T17:48:44.990-04:00</updated><title type='text'>Wireless Discoveries</title><summary type='text'>
I bought myself a Linksys WRT54G Router-AP last night and wired it up, giving a good kick to my network and finally getting behind a dedicated device rather than a Windows workstation pretending to be one.  I decided to give it a spin, and found a few nice things in it.



The first thing I noticed was that my Internet connection was visibly more responsive, something I had not anticipated.  </summary><link rel='related' href='http://linksys.com/' title='Wireless Discoveries'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/111904247607511284/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=111904247607511284' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111904247607511284'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111904247607511284'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/06/wireless-discoveries.html' title='Wireless Discoveries'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-111120926422215507</id><published>2005-03-18T23:40:00.000-05:00</published><updated>2005-03-19T00:38:02.583-05:00</updated><title type='text'>Hardened Ubuntu officially Hardened Ubuntu</title><summary type='text'>
Nobody had a laptop or projector at BaltoLUG this tuesday, so I didn't manage to give my presentation there.  Next month I will try again, April 19 guys.  :)  I also might pick up The Art of Intrusion and The Art of Deception, just nice books to have (even though I hate reading).



You may have noticed I've been fairly obsessed with Ubuntu Linux.  I was a Hardened Gentoo user originally, </summary><link rel='related' href='http://www.ubuntulinux.org/wiki/UbuntuHardened' title='Hardened Ubuntu officially Hardened Ubuntu'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/111120926422215507/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=111120926422215507' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111120926422215507'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111120926422215507'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/03/hardened-ubuntu-officially-hardened.html' title='Hardened Ubuntu officially Hardened Ubuntu'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-111022006567833440</id><published>2005-03-07T12:43:00.000-05:00</published><updated>2005-03-07T13:33:01.076-05:00</updated><title type='text'>Firewalls aren't so magic</title><summary type='text'>
A recent post on Slashdot brings the LAND attack, an attack from eight (8) years ago in which a connection is initiated to a service with a SYN packet with the source and destination IP address set to the server's address.  These attacks cause the server to infinitely loop and become nonresponsive for 15-30 second.  Repeted attack can prove to be a fairly effective DoS.



In response, the </summary><link rel='related' href='http://it.slashdot.org/article.pl?sid=05/03/07/1414234&amp;from=rss' title='Firewalls aren&apos;t so magic'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/111022006567833440/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=111022006567833440' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111022006567833440'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111022006567833440'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/03/firewalls-arent-so-magic.html' title='Firewalls aren&apos;t so magic'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-111003709657457922</id><published>2005-03-05T10:00:00.000-05:00</published><updated>2005-03-05T10:50:55.180-05:00</updated><title type='text'>PaX changing hands</title><summary type='text'>
Due to a spectacular fuckup, PaX will be changing hands on April 1, 2005.  The GrSecurity team will be picking up the PaX code base after then.



A little background, PaX and GrSecurity are each run by one developer, in reality.  "The PaX Team" is made up of a single anonymous entity who took the initiative in 2000 to create what may very well be capable of stopping over half of security </summary><link rel='related' href='http://lists.netsys.com/pipermail/full-disclosure/2005-March/032240.html' title='PaX changing hands'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/111003709657457922/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=111003709657457922' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111003709657457922'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/111003709657457922'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/03/pax-changing-hands.html' title='PaX changing hands'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110999695239384843</id><published>2005-03-04T23:13:00.000-05:00</published><updated>2005-03-04T23:29:12.396-05:00</updated><title type='text'>Blogging in Real Life</title><summary type='text'>
I will be speaking at BaltoLUG on Thursday, March 15.  Originally I didn't want to do it; but this is a good public speaking opportunity and would look very nice on my resume.  I may even give the speech a few more times and refine it afterwards.



I've been working on a paper for my presentation, from which I will be taking my major talking points.  I will be distributing the paper at BaltoLUG</summary><link rel='related' href='http://www.baltolug.org/' title='Blogging in Real Life'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110999695239384843/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110999695239384843' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110999695239384843'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110999695239384843'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/03/blogging-in-real-life.html' title='Blogging in Real Life'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110878646766646026</id><published>2005-02-22T15:06:00.000-05:00</published><updated>2005-02-22T15:28:16.846-05:00</updated><title type='text'>Which OS is more secure?</title><summary type='text'>
Well, the argument came up again. I've been busy playing Xenosaga 2, and haven't been blogging much; but not much has been happening, unless you want me to start blogging security notices or something. In that case you can just check the RSS feeds, which are visible if you click the text above the ads on this blog; icetalk should suffice for that.



The main argument I keep hearing is between "</summary><link rel='related' href='http://linux.slashdot.org/article.pl?sid=05/02/17/1616232&amp;amp;tid=172' title='Which OS is more secure?'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110878646766646026/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110878646766646026' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110878646766646026'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110878646766646026'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/02/which-os-is-more-secure.html' title='Which OS is more secure?'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110798179708199079</id><published>2005-02-09T14:59:00.000-05:00</published><updated>2005-02-09T16:53:26.580-05:00</updated><title type='text'>The buddy system</title><summary type='text'>
Recently I've been exploring extreme programming, a concept I was introduced to by college students, and was recently reminded of by some comments on a slashdot post.  Today I would like to propose a pair programming utility to help apply the concept of pair programming to a distributed working team, such as those which drive most Open Source Software.



Pair programming is a simple </summary><link rel='related' href='http://www.extremeprogramming.org/index2.html' title='The buddy system'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110798179708199079/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110798179708199079' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110798179708199079'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110798179708199079'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/02/buddy-system.html' title='The buddy system'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110763049230851286</id><published>2005-02-05T13:13:00.000-05:00</published><updated>2005-02-05T14:15:33.873-05:00</updated><title type='text'>Non-root viruses for Linux</title><summary type='text'>
I had earlier mentioned that local exploits are remote exploits, and now come back to finish that thought.  To complete the idea, I'll bring in the concept of computer viruses, which in general rely on local users running them.  This is unlike worms, which propagate on their own via e-mailing themselves around or using remote exploits.



Today I've chosen a simple local root exploit and a </summary><link rel='related' href='http://seclists.org/lists/bugtraq/2005/Jan/att-0070/elflbl_v108.c' title='Non-root viruses for Linux'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110763049230851286/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110763049230851286' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110763049230851286'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110763049230851286'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/02/non-root-viruses-for-linux.html' title='Non-root viruses for Linux'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110685046648053034</id><published>2005-01-27T15:45:00.000-05:00</published><updated>2005-02-05T14:18:42.046-05:00</updated><title type='text'>Smoke and Mirrors Awareness Day</title><summary type='text'>
Today is Smoke and Mirrors Awareness Day!  No, not really, but I'd like to point out various pieces of junk that pretend to be secure.



We've already passed over Microsoft's Data Execution Prevention and why it doesn't work without real Address Space Layout Randomization.  This is because a simple ret2libc attack can be used to evade normal memory space protections that systems such as </summary><link rel='related' href='http://lists.netsys.com/pipermail/full-disclosure/2005-January/031264.html' title='Smoke and Mirrors Awareness Day'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110685046648053034/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110685046648053034' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110685046648053034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110685046648053034'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/smoke-and-mirrors-awareness-day.html' title='Smoke and Mirrors Awareness Day'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110660580500734755</id><published>2005-01-24T17:08:00.000-05:00</published><updated>2005-01-24T17:30:05.006-05:00</updated><title type='text'>GrSecurity as kernel hooks</title><summary type='text'>
I don't know why I did it, I don't know how I did it, but somehow I managed to reverse part of GrSecurity into a set of kernel hooks—only three right now—to implement GrSecurity with.  I know Brad isn't going to go along with it, nor will Linus; it's purely academic.



It took me about 5 minutes to design a stacking mechanism that modules don't have to be aware of, and 10 minutes to </summary><link rel='related' href='http://grsecurity.net' title='GrSecurity as kernel hooks'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110660580500734755/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110660580500734755' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110660580500734755'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110660580500734755'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/grsecurity-as-kernel-hooks.html' title='GrSecurity as kernel hooks'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110611870143165055</id><published>2005-01-19T18:57:00.000-05:00</published><updated>2005-01-19T18:59:57.856-05:00</updated><title type='text'>There's no such thing as a local exploit</title><summary type='text'>
Some people feel safe knowing that they have zero or only one remote exploit, even though they have 400 local ones, because they're the only local user on their local desktop box.  This is a falsehood.  Local exploits are just as dangerous if not moreso than remote exploits.



A remote exploit doesn't always mean root access.  If an attacker exploits Firefox or XMMS, he can get local user </summary><link rel='related' href='http://www.ubuntulinux.org/support/documentation/usn/usn-56-1' title='There&apos;s no such thing as a local exploit'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110611870143165055/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110611870143165055' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110611870143165055'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110611870143165055'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/theres-no-such-thing-as-local-exploit.html' title='There&apos;s no such thing as a local exploit'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110594639973009816</id><published>2005-01-17T01:31:00.000-05:00</published><updated>2005-01-17T02:53:51.783-05:00</updated><title type='text'>Most of it can be stopped now</title><summary type='text'>
To aid the Hardened Debian project, I wrote up an analysis of the Ubuntu Security Notice list.  The results are nice to look at, and a blog on them is deserved.  It appears that most USNs contain vulnerabilities which can be decreased to Denial-of-Service attacks, precluding any privilege escallation with simple crashes.



Below is a table aggregating the analysis of the first 60 USNs.  </summary><link rel='related' href='https://www.ubuntulinux.org/wiki/USNAnalysis' title='Most of it can be stopped now'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110594639973009816/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110594639973009816' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110594639973009816'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110594639973009816'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/most-of-it-can-be-stopped-now.html' title='Most of it can be stopped now'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110573183620468960</id><published>2005-01-14T14:08:00.000-05:00</published><updated>2005-01-14T15:47:49.663-05:00</updated><title type='text'>Time for a new Linux kernel development model</title><summary type='text'>
Earlier, I had discussed why changes to the Linux kernel development model were needed to better support third party development.  Now I feel it's time to sit down and discuss what key issues the current development model raises.



Brad Spengler of GrSecurity criticizes the Linux 2.6 development model in a post to Bugtraq.  He gives the following expression of his distaste for the model in</summary><link rel='related' href='http://kernel.org/' title='Time for a new Linux kernel development model'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110573183620468960/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110573183620468960' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110573183620468960'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110573183620468960'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/time-for-new-linux-kernel-development.html' title='Time for a new Linux kernel development model'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110558109974081485</id><published>2005-01-13T13:03:00.000-05:00</published><updated>2006-07-21T13:09:23.866-04:00</updated><title type='text'>A DEP evasion technique</title><summary type='text'>&lt;script&gt;
// policy issue
hide_googlead();
&lt;/script&gt;


In an earlier post, I pointed out a possible way to evade Data Execution Prevention in Microsoft Windows XP Service Pack 2.  I feel this deserves its own blog post, so I've decided to go on here.



I'd like to first point out that this is a speculative method to evade hardware-enforced DEP based on various documentation.  There is not yet a </summary><link rel='related' href='http://www.securityfocus.com/archive/1/386958' title='A DEP evasion technique'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110558109974081485/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110558109974081485' title='67 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110558109974081485'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110558109974081485'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/dep-evasion-technique.html' title='A DEP evasion technique'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>67</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110547116993409957</id><published>2005-01-12T13:46:00.000-05:00</published><updated>2005-01-12T19:59:46.553-05:00</updated><title type='text'>Review of Microsoft's DEP</title><summary type='text'>
After reading through a page on memory protection changes in Windows XP SP2, I e-mailed Microsoft's Technical Support for XP SP2 and requested confirmation on my understanding of the product.  This resulted in a support contact sending me a link to a detailed description of DEP.  The given page doesn't conflict with or add to my understanding of DEP, so I assume I have a fair grasp on how it </summary><link rel='related' href='http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx' title='Review of Microsoft&apos;s DEP'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110547116993409957/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110547116993409957' title='19 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110547116993409957'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110547116993409957'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/review-of-microsofts-dep.html' title='Review of Microsoft&apos;s DEP'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>19</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110541214077851026</id><published>2005-01-10T21:17:00.000-05:00</published><updated>2005-01-10T22:02:25.526-05:00</updated><title type='text'>Hardened 2.6.10 kernel from Gentoo soon</title><summary type='text'>
Linux users fall into three basic groups when it comes to the kernel.  First, there are those who just use what the distribution supplies.  Second, there are those who chose or build their own patchset.  And finally, there are vanilla users who just grab whatever from kernel.org and use that.



From a security standpoint, it is usually better to use a patchset, whether it be your </summary><link rel='related' href='http://hardened.gentoo.org/' title='Hardened 2.6.10 kernel from Gentoo soon'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110541214077851026/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110541214077851026' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110541214077851026'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110541214077851026'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/hardened-2610-kernel-from-gentoo-soon.html' title='Hardened 2.6.10 kernel from Gentoo soon'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110525371137860577</id><published>2005-01-09T01:54:00.000-05:00</published><updated>2005-01-09T01:57:02.466-05:00</updated><title type='text'>A living kernel</title><summary type='text'>
Recently, Jake Moilanen announced a set of patches to add a genetics algorithm library to the Linux kernel.  These patches supply functionality to modify the kernel's behavior experimentally and tune for peak performance.  The base patches can be combined with patches that enhance the Anticipatory IO Scheduler and the CPU scheduler (zaphod patch required) with the algorithms.



The last </summary><link rel='related' href='http://kernel.jakem.net/' title='A living kernel'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110525371137860577/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110525371137860577' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110525371137860577'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110525371137860577'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/living-kernel.html' title='A living kernel'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110479894106558064</id><published>2005-01-04T23:36:00.000-05:00</published><updated>2005-01-09T02:05:26.220-05:00</updated><title type='text'>Ubuntu Technical Board Meeting 2004.01.04</title><summary type='text'>
Ubuntu Linux has a strong community structure which involves the community in the development process via two types of meetings.  Ubuntu Linux Meetings take place every week on#ubuntu-meeting on freenode, and alternate between Technical Board and Community Council meetings.



Today was the Technical Board meeting, a discussion of the Ubuntu Linux technical direction.  The meeting was </summary><link rel='related' href='http://www.ubuntulinux.org/wiki/TechnicalBoardAgenda' title='Ubuntu Technical Board Meeting 2004.01.04'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110479894106558064/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110479894106558064' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110479894106558064'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110479894106558064'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/ubuntu-technical-board-meeting.html' title='Ubuntu Technical Board Meeting 2004.01.04'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110473270965629026</id><published>2005-01-03T01:12:00.000-05:00</published><updated>2005-01-09T02:07:14.993-05:00</updated><title type='text'>Finally a new PaX</title><summary type='text'>
PaX has been stuck at Linux 2.6.7 for a while now.  The author has been fairly active on the 2.4 branch; but 2.6 has been too volatile.  Between 2.6.7 and 2.6.8, major VM changes were put in which changed how PaX had to be written.  This delayed the release of a new PaX for 2.6 ever since, although the 2.4 branch still gets regular releases.



The PaX Team needs to do more work than just </summary><link rel='related' href='http://pax.grsecurity.net/' title='Finally a new PaX'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110473270965629026/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110473270965629026' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110473270965629026'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110473270965629026'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/finally-new-pax.html' title='Finally a new PaX'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110465254935362203</id><published>2005-01-02T02:32:00.000-05:00</published><updated>2005-01-09T02:06:33.810-05:00</updated><title type='text'>Policy on Web content</title><summary type='text'>
You may not think about it, but content filtering is a security issue!  Filtering out pornography is a major enforcement aid for many businesses and public institutions which do not allow access to such material from their network.  It is therefor interesting from a security standpoint that tools exist to facilitate the control and filtering of pornography, violence, and racist content, and </summary><link rel='related' href='http://thread.gmane.org/gmane.linux.ubuntu.devel/2840' title='Policy on Web content'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110465254935362203/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110465254935362203' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110465254935362203'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110465254935362203'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/policy-on-web-content.html' title='Policy on Web content'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110461010950394849</id><published>2005-01-01T14:41:00.000-05:00</published><updated>2005-01-09T02:09:13.970-05:00</updated><title type='text'>Hardened Ubuntu</title><summary type='text'>
Earlier I had blogged on a more secure setting that would be suitable for wide-spread distribution.  Such an environment can be created in Gentoo Linux relatively easily, if you're already a Gentoo user.  Unfortunately, the learning curve needed for Gentoo is out of the reach of many people, and Gentoo is not always feasible anyway.  Other distributions have to take up these enhancements in </summary><link rel='related' href='http://debian-hardened.org/' title='Hardened Ubuntu'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110461010950394849/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110461010950394849' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110461010950394849'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110461010950394849'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/hardened-ubuntu.html' title='Hardened Ubuntu'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110456856225388481</id><published>2005-01-01T02:55:00.000-05:00</published><updated>2005-01-09T02:09:59.033-05:00</updated><title type='text'>Spinning a secure setting</title><summary type='text'>
I've been a Hardened Gentoo user for a while. I don't use the full set with SELinux/GrSecurity, Prelude, and whatever else they like to throw at people; but instead use a few basic things like a security hardened gcc that produces PIE binaries with stack smash protection (paper).



It may come as a surprise to you, but these weren't terribly painful for me to get on my system.  I won't say</summary><link rel='related' href='http://lwn.net/Articles/106214/' title='Spinning a secure setting'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110456856225388481/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110456856225388481' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110456856225388481'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110456856225388481'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/spinning-secure-setting.html' title='Spinning a secure setting'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9881230.post-110456576152741468</id><published>2005-01-01T02:10:00.000-05:00</published><updated>2005-01-09T02:10:29.923-05:00</updated><title type='text'>Blogging on Cyberterror</title><summary type='text'>
The Blog on Cyberterror is now up.  This blog is made by the same person who runs the War on Cyberterror Web site, an informational site which attempts to pool together information related to security and security efforts.



The purpose of the Blog on Cyberterror is to give me a place to vent and talk about things going on. This is a very informal setting; I may get into observations that </summary><link rel='related' href='http://woct.sourceforge.net/' title='Blogging on Cyberterror'/><link rel='replies' type='application/atom+xml' href='http://woct-blog.blogspot.com/feeds/110456576152741468/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9881230&amp;postID=110456576152741468' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110456576152741468'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9881230/posts/default/110456576152741468'/><link rel='alternate' type='text/html' href='http://woct-blog.blogspot.com/2005/01/blogging-on-cyberterror.html' title='Blogging on Cyberterror'/><author><name>John</name><uri>http://www.blogger.com/profile/04330716591714765149</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry></feed>
