A teenager could also crack your app and use the key he found to gain access. If you want to prevent that, I guess you need to rethink the way you store access credentials. I wonder how [Snow] Leopard Parental Controls do that.
You should also use Mac OS Keychain API and not reinvent the wheel if at all possible. I'm not an expert on Keychain, so I can't point you to the right API calls, sorry. -- Gleb Dolgich http://pixelespressoapps.com On 30 Dec 2009, at 19:23, Mr. Gecko wrote: > But then the child/teenager, if they know about keychain they could check it > and find the key. Unless there is a way to prevent them from seeing it. > Speaking of keychain, can you recommend me a good public domain keychain > framework? I currently wrote my own and on some computers, the keychain > didn't work, the only thing they all had in common was 1password. > > On Dec 30, 2009, at 1:19 PM, Gleb Dolgich wrote: > >> You could store the generated key in a keychain. This way you wouldn't have >> to ask for the password to access the encryption key. >> >> On 30 Dec 2009, at 18:58, Mr. Gecko wrote: >> >>> But then how would I get the data? If the key has to do with the password, >>> then how can I get the parental settings and respond to them. >>> >>> On Dec 30, 2009, at 12:51 PM, Gleb Dolgich wrote: >>> >>>> Perhaps a better way would be to ask for a password once the user is >>>> authenticated, and then generate an AES key using that password, instead >>>> of storing encryption key inside your program. With you current scheme, if >>>> anyone breaks your 'common' key, everyone will be able to circumvent your >>>> parental protection. >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
