Re: Disabling screen capture
Re: Disabling screen capture
- Subject: Re: Disabling screen capture
- From: email@hidden
- Date: Fri, 21 Feb 2014 08:23:53 +0900
> On 2014/02/21, at 8:05, Stevo Brock <email@hidden> wrote:
>
>> On Feb 20, 2014, at 2:39 PM, Jens Alfke wrote:
>>
>>
>>> On Feb 20, 2014, at 11:58 AM, Bradley O'Hearne <email@hidden> 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
>
>> ___________________
That sort of thing is defeated easily by accident with image resizing alone.
Ultimately it sounds like you want to build a kiosk in a controlled environment.
You would need the following to succeed.
Managed user account.
Kiosk mode application.
Limited physical access to hardware including the power button and power supply.
Physical screening for camera devices on users.
(Difficult today. )
That's what would be required to achieve this.
Coming closer with less would mean installing and doing ridiculous things in the system that would likely reduce security or stability and be fragile to maintain.
So as always security is a trade off for user experience quality.
Really seriously evaluate the risks and trade offs before making commitments with these kind of requirements.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden