On Sep 5, 2014, at 10:15 , Britt Durbrow <bdurb...@rattlesnakehillsoftworks.com> wrote:
> If I can’t find an officially supported way to do this, then yeah - that’s > what I figure I’ll have to do. I was trying to avoid it due to user > experience issues; requiring a second login, etc is cumbersome every time > somebody wants to record something in the app… <sigh> Oh well... It was never a workable idea, though. It’d be just as bad for a user to set a password of ‘123456’ as having no password, for example, and there’d never be an API that *told* you what the password was so you could check if it was good enough. Similarly, you’d never have a way of checking that the current screensaver actually *obscured* the screen contents. Given the rumors floating around about next week’s grand revelation event, you might also want to hold off making any decisions until you see what Apple will have to offer. With Health Kit, Home Kit, wearables and payments being bruited, there might turn out to be something secure that would ease the second-login problem. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
