On 07/03/2013, at 4:21 PM, Brad O'Hearne <br...@bighillsoftware.com> wrote:
> But this is something far different from those -- security is imperative. Perhaps your app is not suited to having a graphical output or interface at all in that case? While I'm not a fan of "security through obscurity", you could arrange your programs output to be routed to a paper tape puncher maybe, or a hall of monkeys with typewriters being prodded with sharp sticks. Facetiousness aside, I'm trying to make a serious point - once your app writes its output to the screen, it's out there. The photons have left the monitor, carrying the output data of the app with them to whatever detector they are destined for, be it eyeballs or a camera. You can't get them back, all you can do is prevent them being emitted in the first place. All a screen shot is is a time-delayed version of the same. So the problem appears to be time, doesn't it? So how about you only show the output to the user for, say, 0.2 seconds? That will be very hard to capture. Hard to see too, but security always comes at the cost of usability. Just make sure you train users to pay attention FULLY to the screen. Another option, given that the screen shot feature writes files with particular file names to the desktop, you could monitor the desktop folder, detect the files and delete them. Or, perhaps you could collate all of these replies to your thread and present them to the arse who wrote the spec. --Graham _______________________________________________ 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
