Re: How difficult would it be to remove or replace the file name from the messages sent to the IMS service?

[toaster]

Hey Mike,
We could add an obfuscate option to collections, all we need is an
identifier to match, so timestamp, or a random string would work just as
well. That would hide the filename completely from the ims.

-Mike
(the other one)

On 28.01.2013 18:26, shake wrote:
> Hey Dave,
>
> We don't keep a copy of the filename on the IMS, so you don't need to
> worry about that -- we only store the id (just an integer), hash,
> time
> stamp, and token class for each round. For over the wire, we have
> recently looked into connecting to the IMS through https, which would
> protect any critical information held in the filename. This should be
> available the next minor release of ACE (which should be fairly
> soon).
>
> -Mike
>
> On Monday, January 28, 2013 2:55:27 PM UTC-5, Dave Rogers wrote:
>
>> We want to use ACE and IMS for our archives, but we may run into
>> privacy regulation issues when storing the file names on a third
>> party--out-of-country as it happens--server like ims.umiacs.umd.edu
>> [1]. For example, a file name could theoretically have a medical
>> patient's name and identifying number in it (not a good file naming
>> practice, but it happens nonetheless).
>>
>> After running a packet trace on ACE, I could see the file name
>> transmitted for a newly-audit file with every requestTokensImmediate
>> message and requestTokensImmediateResponse reply.
>>
>> One solution we bandied about was replacing the file name with a
>> hash of the name. That should serve whatever needs IMS has from a file
>> name, or so we imagine. Is that a reasonable assumption?
>
> --
> You received this message because you are subscribed to the Google
> Groups "ace-devel" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to ace-devel+...@googlegroups.com.
> To post to this group, send email to ace-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/ace-devel?hl=en
> [2].
> For more options, visit https://groups.google.com/groups/opt_out
> [3].
>
>
>
> Links:
> ------
> [1] http://ims.umiacs.umd.edu
> [2] http://groups.google.com/group/ace-devel?hl=en
> [3] https://groups.google.com/groups/opt_out

[Dave Rogers]

That's good news all around. Of course, for regulatory and legal reasons, we might still need proof that the names aren't being held by the IMS server (but, IANAL, so who knows?). The obfuscation option combined with HTTPS would be ideal.

While on the topic, is the IMS code available to look at? Or even to install ourselves to play with? We wouldn't want to use our own IMS to audit our own tokens for conflict of interest reasons, but I do find the theory behind it intriguing.

Thanks for the updates,

Dave