<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>toxicsoftware.com - Latest Comments in AquaticPrime Aftermath</title><link>http://toxicsoftware.disqus.com/</link><description></description><atom:link href="https://toxicsoftware.disqus.com/aquaticprime_aftermath/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 09 Jun 2006 12:54:50 -0000</lastBuildDate><item><title>Re: AquaticPrime Aftermath</title><link>http://toxicsoftware.com/aquaticprime-aftermath.html#comment-1655972</link><description>&lt;p&gt;"Any scheme accessed via Cocoa calls is vulnerable to attack via an InputManager"  and&lt;br&gt;Public-key encryption systems may be especially vulnerable to replacement of the public key,&lt;br&gt;unless it is obfuscated throughout the entire app" which are clearly documented in discussion on CocoaDev:MakingSecureRegistrationCodes shouldn't be the first time these guys have heard this.&lt;/p&gt;&lt;p&gt;I'm quite surprised you are getting such a reaction.  While you've taking the time to 'prove it'&lt;br&gt;and point at a specific product, none of this is new.  I suppose this is hush flame as we already know&lt;br&gt;but if you blog about it people will discover these deep dark secrets that already sit on other public&lt;br&gt;websites :/&lt;/p&gt;&lt;p&gt;I'm not watching your thread, but I'm sure it is the implementors that have banked on this scheme&lt;br&gt;that are seeing red as it COULD affect their financials.  However I'm sure we all know that if someone&lt;br&gt;is going to go to the trouble to write a SIMBL/InputManager plugin to runtime circumvent your registration&lt;br&gt;scheme, they probably won't be ponying up for a license anyway.  Most pirates take the use it for free&lt;br&gt;or don't use it at all mentality.&lt;/p&gt;&lt;p&gt;Otherwise MethodSwizzling is cool and fun :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Grimes</dc:creator><pubDate>Fri, 09 Jun 2006 12:54:50 -0000</pubDate></item><item><title>Re: AquaticPrime Aftermath</title><link>http://toxicsoftware.com/aquaticprime-aftermath.html#comment-1655971</link><description>&lt;p&gt;Because after pointing out a bug in an existing system it is now obviously my responsible to create a replacement for that system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">schwa</dc:creator><pubDate>Fri, 09 Jun 2006 09:20:46 -0000</pubDate></item><item><title>Re: AquaticPrime Aftermath</title><link>http://toxicsoftware.com/aquaticprime-aftermath.html#comment-1655970</link><description>&lt;p&gt;Jonathon,&lt;/p&gt;&lt;p&gt;We all look forward to your contribution of a usable, bullet-proof, uncrackable licensing scheme &lt;br&gt;(with source) for shareware developers to use.  After your critical analysis of Aquatic Prime, you&lt;br&gt;now know of at least one way that it shouldn't be done.  Good luck and godspeed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Some Guy</dc:creator><pubDate>Fri, 09 Jun 2006 08:02:33 -0000</pubDate></item></channel></rss>