Index

Subject : Re: LUG: C++/C question

From : Daniel Underwood <daniel.underwood@ncsu.[redacted]>

Date : Wed, 07 Dec 2011 09:14:55 -0500

Parent

Yes, that's true.  There's probably some threshold of due diligence to prevent theft of the records.  I don't know what that threshold is, but just defining the encryption key explicitly in a header file may be sufficient.  Also, maybe just explicitly defining all the data in a header file is sufficient to meet that threshold.  I'll have to discuss the options with the property owners.  Right now I'm just looking at all my options--thanks for all the suggestions, by the way!

Sent from my iPhone

On Dec 7, 2011, at 8:47 AM, Stephen Bryant < stephen@stephenbryant.[redacted] > wrote:

Your primary concern there would be the encryption key -- you'd have to find some way to hide that in the program. Should be simpler to hide that much smaller piece of data though.

--
Stephen Bryant



On Wed, Dec 7, 2011 at 6:45 AM, Daniel Underwood < daniel.underwood@ncsu.[redacted] > wrote:
What about encrypting the data (text files), reading the encrypted data at runtime, decrypting in memory, and then assigning to the variables?  (Yes, someone skilled enough could extract the decrypted data from RAM, but let's assume that's a necessary casualty.)

On Wed, Dec 7, 2011, at 12:19 AM, Ian Kilgore wrote:
> On Tue, Dec 6, 2011 at 10:12 PM, Daniel Underwood
> < daniel.underwood@ncsu.[redacted] > wrote:
> > The point of the program is to generate a sample of a random variable with distribution defined by the input data I'm trying to conceal from the user.
>
> The best you can do is make it kind of annoying for a skilled user to
> recover the data, period.
> Unless you make it a client-server thing, which is rarely practical
> and usually slightly more annoying.
> --
> ik
>
--
Daniel Underwood
North Carolina State University
PhD Student - Industrial Engineering
email: daniel.underwood@ncsu.[redacted]
phone: XXX.302.3291
fax: XXX.515.5281
web: http://www4.ncsu.edu/~djunderw/