Indulge me here... Take a step back. Basically you're heading down a road towards a closed system.
Spending a lot of time inventing encryption methods to limit access to your data when your competitor might just buy a legitimate copy of your software and get your data anyway... Disassemble your executables, run memory debuggers and step through your decrypted code and look at your decrypted data pages in memory. Primarily you need to understand why people would buy your software and not your competitors, and invest time and money in that direction, making it better. I can quote the Msn Vs Google/Yahoo tirade. Facebook and myspace are extremely popular. MS wanted to buy facebook for a billion and they said no (eventually bought a 1.6% stake for 240mil). Facebook have now released an API and documentation on how to do stuff with their site. How popular will this become? Massive! Myspace (which has more users) is now duplicating that. Let's bring it back to your app. How would your business change if it became the facebook of pi? :P Chay -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Subject: Re: [ADVANCED-DOTNET] Storing shared secrets >> What you don't want: the key used for signing is available to anyone who >> installs your client, so Bans Frouma can get at it and use it in his Pi >> Komputing Klient. > >I hear this Bans Frouma guy is pretty smart. If he had administrative >access to a machine where "Pi Computing Client" is installed, there's >little you could do to prevent him from getting your key. So I hope -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as "KBC FP"). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided "as is", without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
