<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Maynor goes for a do-over</title>
	<atom:link href="http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/</link>
	<description>Apple news and analysis from everyone's favorite mythical Mac user</description>
	<pubDate>Wed, 07 Jan 2009 08:46:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: aelx</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8348</link>
		<dc:creator>aelx</dc:creator>
		<pubDate>Mon, 05 Mar 2007 06:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8348</guid>
		<description>Bottom Line: He still has not confirmed that the the crash happened with a stock wifi card. I don't care if it's a third party card. Nobody puts in a hacked card. If it's a third party card rigged to a macbook, is it still a mac? Or a hacked mac on purpose to exploit it. harumph.</description>
		<content:encoded><![CDATA[<p>Bottom Line: He still has not confirmed that the the crash happened with a stock wifi card. I don&#8217;t care if it&#8217;s a third party card. Nobody puts in a hacked card. If it&#8217;s a third party card rigged to a macbook, is it still a mac? Or a hacked mac on purpose to exploit it. harumph.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rip Ragged</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8321</link>
		<dc:creator>Rip Ragged</dc:creator>
		<pubDate>Sun, 04 Mar 2007 22:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8321</guid>
		<description>A good observation, Don.

If you wouldn't object, I'd like to add that if the quality of his work, and the nature and intent of his disclosures is only what we've seen so far then he really doesn't count as a white-hat &lt;i&gt;or&lt;/i&gt; a black-hat. Just an asshat.</description>
		<content:encoded><![CDATA[<p>A good observation, Don.</p>
<p>If you wouldn&#8217;t object, I&#8217;d like to add that if the quality of his work, and the nature and intent of his disclosures is only what we&#8217;ve seen so far then he really doesn&#8217;t count as a white-hat <i>or</i> a black-hat. Just an asshat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8310</link>
		<dc:creator>Don</dc:creator>
		<pubDate>Sun, 04 Mar 2007 20:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8310</guid>
		<description>"Maynor said this experience has led him to have no interest in providing information to Apple again about security flaws. That's to all our detriment."

Maybe it is and maybe it isn't.  It depends on whether he keeps trying to break Mac OS X or not, and if he does, how he makes his findings public.

If Maynor stops trying to break Mac OS X, then that's a minor loss.  It means that one researcher has stopped trying to break Mac OS X.  If he were the only person doing this, it would be a loss, but he's not, so this seems like one of those "If you don't, someone else will" situations.

If Maynor continues trying to break Mac OS X, and he reports all his results on any public forum, then that's no worse than the Month Of Apple Bugs.  Either Apple will monitor his public disclosures, or someone else will and send them to Apple.  In other words, Maynor would just be switching from "responsible disclosure" (notify vendor first), to "full disclosure" (everyone is notified at the same time).  If he does that, he can't claim to be doing "responsible disclosure", but so what?  Other breaks of Mac OS X have been released as full disclosure and the world hasn't ended.

If Maynor continues trying to break Mac OS X, and he only reports results or exploits privately, or only provides only partial reports, then that *IS* to all our detriment.  But that's because he's gone from being a white-hat security researcher to being a black-hat malicious cracker.  He's the one to make that choice, and no one can stop him from doing that, not even Apple.</description>
		<content:encoded><![CDATA[<p>&#8220;Maynor said this experience has led him to have no interest in providing information to Apple again about security flaws. That&#8217;s to all our detriment.&#8221;</p>
<p>Maybe it is and maybe it isn&#8217;t.  It depends on whether he keeps trying to break Mac OS X or not, and if he does, how he makes his findings public.</p>
<p>If Maynor stops trying to break Mac OS X, then that&#8217;s a minor loss.  It means that one researcher has stopped trying to break Mac OS X.  If he were the only person doing this, it would be a loss, but he&#8217;s not, so this seems like one of those &#8220;If you don&#8217;t, someone else will&#8221; situations.</p>
<p>If Maynor continues trying to break Mac OS X, and he reports all his results on any public forum, then that&#8217;s no worse than the Month Of Apple Bugs.  Either Apple will monitor his public disclosures, or someone else will and send them to Apple.  In other words, Maynor would just be switching from &#8220;responsible disclosure&#8221; (notify vendor first), to &#8220;full disclosure&#8221; (everyone is notified at the same time).  If he does that, he can&#8217;t claim to be doing &#8220;responsible disclosure&#8221;, but so what?  Other breaks of Mac OS X have been released as full disclosure and the world hasn&#8217;t ended.</p>
<p>If Maynor continues trying to break Mac OS X, and he only reports results or exploits privately, or only provides only partial reports, then that *IS* to all our detriment.  But that&#8217;s because he&#8217;s gone from being a white-hat security researcher to being a black-hat malicious cracker.  He&#8217;s the one to make that choice, and no one can stop him from doing that, not even Apple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8210</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Sun, 04 Mar 2007 07:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8210</guid>
		<description>Rus: Oh puh-lease. OS X isn't open source; it's not the security researcher's/hacker's responsibility to fix it. Even if it was, it wouldn't necessarily be. 

I still agree with other people here: Put up (the whole thing) or shut up. If Apple's fixed the bug and made the fix freely and publicly available, let the exploit hang out there. If people don't patch their systems, it's their own damn fault at this point. 

If you don't have a full on rooting exploit, shut up and go away.</description>
		<content:encoded><![CDATA[<p>Rus: Oh puh-lease. OS X isn&#8217;t open source; it&#8217;s not the security researcher&#8217;s/hacker&#8217;s responsibility to fix it. Even if it was, it wouldn&#8217;t necessarily be. </p>
<p>I still agree with other people here: Put up (the whole thing) or shut up. If Apple&#8217;s fixed the bug and made the fix freely and publicly available, let the exploit hang out there. If people don&#8217;t patch their systems, it&#8217;s their own damn fault at this point. </p>
<p>If you don&#8217;t have a full on rooting exploit, shut up and go away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BKWatch</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8157</link>
		<dc:creator>BKWatch</dc:creator>
		<pubDate>Sat, 03 Mar 2007 16:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8157</guid>
		<description>Maynor is now claiming that he had the ability to hack the Broadcomm drivers back in August -- the Broadcom drivers are used in PPC Macs.   Apple did release one of the wireless updates that patched the PPC Broadcom drivers.  The problem is that Maynor DENIED that he had the ability to hack into Broadcom drivers when he first talked with Krebs.</description>
		<content:encoded><![CDATA[<p>Maynor is now claiming that he had the ability to hack the Broadcomm drivers back in August &#8212; the Broadcom drivers are used in PPC Macs.   Apple did release one of the wireless updates that patched the PPC Broadcom drivers.  The problem is that Maynor DENIED that he had the ability to hack into Broadcom drivers when he first talked with Krebs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8066</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sat, 03 Mar 2007 00:00:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8066</guid>
		<description>Will I must say that Maynor has seemed more reasonable over the last few months than he did at first. If he keeps improving at this rate I may just trust something he says, oh, about another year from now. It takes a lot longer to build a reputation than to throw it away. 
I also find it interesting that a proponent of responsible disclosure is so keen on asking people not to disclose stuff! If you can't talk about it- don't talk about it. Saying that you know something but you can't tell anyone is useless to everyone and further obscures an already cloudy issue.</description>
		<content:encoded><![CDATA[<p>Will I must say that Maynor has seemed more reasonable over the last few months than he did at first. If he keeps improving at this rate I may just trust something he says, oh, about another year from now. It takes a lot longer to build a reputation than to throw it away.<br />
I also find it interesting that a proponent of responsible disclosure is so keen on asking people not to disclose stuff! If you can&#8217;t talk about it- don&#8217;t talk about it. Saying that you know something but you can&#8217;t tell anyone is useless to everyone and further obscures an already cloudy issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rus</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8016</link>
		<dc:creator>Rus</dc:creator>
		<pubDate>Fri, 02 Mar 2007 15:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8016</guid>
		<description>I'm not sure if "trying to find and not to fix" vulnerabilities isn't considered hacking which is a felony.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if &#8220;trying to find and not to fix&#8221; vulnerabilities isn&#8217;t considered hacking which is a felony.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fudo</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8012</link>
		<dc:creator>fudo</dc:creator>
		<pubDate>Fri, 02 Mar 2007 15:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8012</guid>
		<description>Fake Steve

"The Mayntard is at it again."

/Fake Steve</description>
		<content:encoded><![CDATA[<p>Fake Steve</p>
<p>&#8220;The Mayntard is at it again.&#8221;</p>
<p>/Fake Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John C. Welch</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-8002</link>
		<dc:creator>John C. Welch</dc:creator>
		<pubDate>Fri, 02 Mar 2007 14:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-8002</guid>
		<description>Here's one. Let someone who isn't Maynor or Ellich provide the details. Right  now, Maynor's showing an exploit. Is it the same one he claimed he had originally? Well, he says it is, but he's no credibiity. Where's the proof that what he's showing today is the EXACT SAME CODE he used then? 

Even reading your article Glenn, you point out that he's still not being straightforward about this.

So he has no credibility. At this point, he's shot himself so badly that even *legitimate* work he's done or will do will be questioned, because he's demonstrated that he's perfectly willing to dissemble to make himself look good. 

Even now, he can't stop. "Well, I can also take over a Mac, but i'm not going to show that...yet." What's he waiting for? More publicity so he can get more jobs as a l33t s3cur1tee d00d? Bullshit. He's been playing this game since the beginning, and it's just publicity hounding at this point.

the other issue is this statement:

"Maynor said this experience has led him to have no interest in providing information to Apple again about security flaws. That’s to all our detriment."

No, it doesn't. If he can't handle the fact that sometimes things don't work the way you want them too, and companies have a high asshole quotient, then he was never the kind of person you wanted doing security research. "I'm taking my ball and going home" is what seven year olds say when they don't get their way. It's not what grownups say. Waaah, Apple didn't do what he wanted the way he wanted. Get over it.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s one. Let someone who isn&#8217;t Maynor or Ellich provide the details. Right  now, Maynor&#8217;s showing an exploit. Is it the same one he claimed he had originally? Well, he says it is, but he&#8217;s no credibiity. Where&#8217;s the proof that what he&#8217;s showing today is the EXACT SAME CODE he used then? </p>
<p>Even reading your article Glenn, you point out that he&#8217;s still not being straightforward about this.</p>
<p>So he has no credibility. At this point, he&#8217;s shot himself so badly that even *legitimate* work he&#8217;s done or will do will be questioned, because he&#8217;s demonstrated that he&#8217;s perfectly willing to dissemble to make himself look good. </p>
<p>Even now, he can&#8217;t stop. &#8220;Well, I can also take over a Mac, but i&#8217;m not going to show that&#8230;yet.&#8221; What&#8217;s he waiting for? More publicity so he can get more jobs as a l33t s3cur1tee d00d? Bullshit. He&#8217;s been playing this game since the beginning, and it&#8217;s just publicity hounding at this point.</p>
<p>the other issue is this statement:</p>
<p>&#8220;Maynor said this experience has led him to have no interest in providing information to Apple again about security flaws. That’s to all our detriment.&#8221;</p>
<p>No, it doesn&#8217;t. If he can&#8217;t handle the fact that sometimes things don&#8217;t work the way you want them too, and companies have a high asshole quotient, then he was never the kind of person you wanted doing security research. &#8220;I&#8217;m taking my ball and going home&#8221; is what seven year olds say when they don&#8217;t get their way. It&#8217;s not what grownups say. Waaah, Apple didn&#8217;t do what he wanted the way he wanted. Get over it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn Fleishman</title>
		<link>http://www.macalope.com/2007/03/01/maynor-goes-for-a-do-over/comment-page-1/#comment-7948</link>
		<dc:creator>Glenn Fleishman</dc:creator>
		<pubDate>Fri, 02 Mar 2007 06:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.macalope.com/?p=182#comment-7948</guid>
		<description>WH: "now, after Apple has patched up the OS, he demonstrates that he was right, by crashing a Mac using AirPort": Not quite. He also has a number of emails, including some back from Apple, that he says show that he sent information to them about the precise nature of what he found.

BLATTAPUS: Maynor confirmed what has been known during this whole time. He had an exploit against the native driver that comes with OS X. He and Ellch screwed up. They had meant to show and discuss only a third-party hack, and they got too excited, let Krebs see what was going on, and then all hell broke loose.

This does boil down to just two things: Did Apple knowingly lie about a security issue, which is a significant lapse on their part, and I still think unlikely; did Maynor and Ellch try to help the user community by NOT releasing details, which I think is likely based on their subsequent actions.</description>
		<content:encoded><![CDATA[<p>WH: &#8220;now, after Apple has patched up the OS, he demonstrates that he was right, by crashing a Mac using AirPort&#8221;: Not quite. He also has a number of emails, including some back from Apple, that he says show that he sent information to them about the precise nature of what he found.</p>
<p>BLATTAPUS: Maynor confirmed what has been known during this whole time. He had an exploit against the native driver that comes with OS X. He and Ellch screwed up. They had meant to show and discuss only a third-party hack, and they got too excited, let Krebs see what was going on, and then all hell broke loose.</p>
<p>This does boil down to just two things: Did Apple knowingly lie about a security issue, which is a significant lapse on their part, and I still think unlikely; did Maynor and Ellch try to help the user community by NOT releasing details, which I think is likely based on their subsequent actions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
