On Feb 20, 2014, at 2:39 PM, Jens Alfke wrote: > > On Feb 20, 2014, at 11:58 AM, Bradley O'Hearne <[email protected]> > wrote: > >> The app is delivering tests remotely — some of which are not your typical >> classroom college exams, but very privately held, very expensive >> certification tests which clients have spent many thousands of dollars to >> create. This test content needs to be secured, and not easily copied while >> the app is running. Yes, I am aware of various hardware hacks or video >> options that can be accomplished external to the machine — those are out of >> scope for this question. > > If I were trying to circumvent this I'd just use my iPhone camera to take a > photo or video of the screen. (Or open my web browser and search for pictures > taken by someone else who did.) As there's no way to block that, why bother? > > Yes, this isn't a direct answer to your question. But I feel that any attempt > to protect content this way becomes a race to the bottom, with ever more > onerous restrictions in the OS (viz. the Windows kernel stuff Doug mentioned) > that still don't end up deterring people who are determined to copy. > > Why not follow the proverb "Locks are there to keep honest people out", and > put in some basic guards against screen-shots, maybe like capturing the > Cmd-Shift-3 / 4 keystrokes? Going further would IMHO be a time- and > money-sink for you, and still wouldn't prevent copying. > > I understand your frustration that people keep telling you "don't do this" > instead of helping you do it, but that's actually one of the things I like > about this list: people will look beyond the immediate question and give > advice on the big picture. Some things just aren't worth doing. > > —Jens
I don't know if you have this in place or not, but what about embedding some identifying information in the midst of the important content, such that if posted images were discovered, they could be traced back? -Stevo Brock Sunset Magicwerks, LLC www.sunsetmagicwerks.com 818-478-9758 > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > 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/devlists%40sunsetmagicwerks.com > > This email sent to [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
