[Building Sakai] Secure Delivery Service (SDS) in samigo

Adrian Fish adrian.r.fish at gmail.com
Fri Nov 8 06:32:58 PST 2013


I have no idea how these lock down scenarios are achieved. I'll be happy to
put some work into allowing the portal chat to be disabled for sessions in
some way.

By the way, those remote proctor things look like something out of an old
Doctor Who episode, respect :)

Cheers,
Adrian.


On 8 November 2013 14:04, Sam Ottenhoff <ottenhoff at longsight.com> wrote:

> No, the idea of a secure delivery service is to lock down the entire
> user's desktop to prevent the user from printing or opening up new tabs.
>  If the institution is using portal chat, it would currently be allowed as
> our portal chat has no code to prevent its use during high-stakes
> assessments.  To get around that, we would either have to write code to
> prevent portal chat from being used during high-stakes assessments, or we
> would have to ask the vendors of security delivery services to include
> portal chat's JS files in their block lists.
>
>
>
> On Fri, Nov 8, 2013 at 6:29 AM, Neal Caidin <neal.caidin at apereo.org>wrote:
>
>> Probably a stupid question, but does that  mean it could potentially be
>> used for Portal Chat to lock down this tool when students are taking an
>> exam?
>>
>> -- Neal
>>
>>
>>
>>
>> On Thu, Nov 7, 2013 at 10:05 PM, John Bush <jbush at anisakai.com> wrote:
>>
>>> https://jira.sakaiproject.org/browse/SAM-1205
>>>
>>> has anyone attempted to use this work for something other than
>>> respondus lockdown to date?  It looks generic enough to me that it
>>> could be applied to any 3rd party service of this sort like Remote
>>> Proctor for example.
>>>
>>>
>>> http://source.sakaiproject.org/viewsvn/sam/trunk/docs/locked_browser/README.txt?view=markup&pathrev=98172
>>>
>>> --
>>> John Bush
>>> 602-490-0470
>>>
>>> ** This message is neither private nor confidential in fact the US
>>> government is storing it in a warehouse located in Utah for future
>>> data mining use cases should they arise. **
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131108/a66507ab/attachment.html 


More information about the sakai-dev mailing list