[Ssc-dev] Authentication, Authorization and Architecture
Harlo Holmes
harlo.holmes at gmail.com
Wed Mar 6 21:26:10 EST 2013
it is! I was hoping that was clear, but it's good to reestablish our goals.
On Mar 6, 2013 9:24 PM, "Lee Azzarello" <lee at rockingtiger.com> wrote:
> This sounds like a very important difference to me.
>
> Lee
> On Mar 6, 2013 9:20 PM, "Harlo Holmes" <harlo.holmes at gmail.com> wrote:
>
>> I think this part of the project refers only to properly authenticating
>> IBA staff members as they interact with already-submitted media. (like, who
>> on the IBA team has access to view encrypted metadata, and keeping logs of
>> who viewed what and when.)
>>
>> it should be outside the loop we established previously and has nothing
>> to do with the mobile client or its users. But Barbra can explain more...
>>
>> Thanks,
>> Harlo
>> On Mar 6, 2013 9:03 PM, "Nathan of Guardian" <nathan at guardianproject.info>
>> wrote:
>>
>>>
>>>
>>> Lee Azzarello <lee at rockingtiger.com> wrote:
>>>
>>> >Nathan,
>>> >
>>> >
>>> >Can you describe the level of detail for authorization of roles from
>>> >client to server? I don't think I understand the scope of this project
>>> >not the requirements to ensure a chain of custody in a court of law.
>>>
>>> This is what the entire InformaCam IBA project has been doing for the
>>> last year. The Chain Of Custody issue is solved based on the signing and
>>> encryption Harlo has already implemented. You should be able to post
>>> informacam blobs into the public internet, as long as they have been signed
>>> by the submitters key and encrypted to the trusted parties key. We also
>>> have the file hash submission process that is again, already designed and
>>> implemented.
>>>
>>> The only roles there were ever meant to be were 1) known or unknown
>>> person submitting a report from their device and 2) trusted party receiving
>>> report and being able to unpack and verify integrity of report blob.
>>>
>>> I know we have added additional function to the server to allow
>>> searching and browsing of reports, but super complex roles and distributed
>>> computing authenticating mechanisms seems like we are way way out of any
>>> design goals I am familiar with.
>>>
>>> Harlo, Bryan - can you provide some clarity here? Are we getting pushed
>>> in directions by the IBA that I am not aware of?
>>>
>>> +n
>>> _______________________________________________
>>> Ssc-dev mailing list
>>>
>>> Post: Ssc-dev at lists.mayfirst.org
>>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev
>>>
>>> To Unsubscribe
>>> Send email to: Ssc-dev-unsubscribe at lists.mayfirst.org
>>> Or visit:
>>> https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com
>>>
>>> You are subscribed as: harlo.holmes at gmail.com
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20130306/18a81c34/attachment-0001.html>
More information about the Ssc-dev
mailing list