And note how many DRM solutions have stood the test of time against motivated hackers. My inclination (not knowing how valuable these digits of pi really are, or how motivated/resourceful this Bans Frouma guy really is) would be to get a good IL obfuscator and leave it at that.
But nobody's ever trusted me with data that could be converted into $$$ either. ;-) -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Friday, March 28, 2008 9:59 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Storing shared secrets On Fri, Mar 28, 2008 at 9:32 AM, Per Bolmstedt <[EMAIL PROTECTED]> wrote: > > 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 that you're really just trying to prevent access for Hurt Cagenlocher -- a casual hacker at best, and one with an insufficient attention span to crack your key. What you're describing is a pretty classic DRM kind of problem and it requires something like a Trusted Computing platform: http://en.wikipedia.org/wiki/Trusted_computing -- Curt Hagenlocher [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
