[guardian-dev] idea for managing multiple virtual disks in IOCipher

[Hans of Guardian]

In this use case, would you need to access multiple virtual disks at the same time?  In the Storymaker case, I think that it could make sense to just have a single virtual disk open at a time, and that virtual disk could serve as the over-arching per-project container.

.hc

On Jun 25, 2013, at 6:24 PM, Josh Steiner wrote:

> Another use case for multiple virtual disks is in StoryMaker we might like to add sometime in the future the ability to have each story in it's own disk, could be attractive for some orgs that don't want media created on their dime to leak out of their official channels.  In this case having no copy method is a feature :)
> 
> -Josh
> 
> 
> On Tue, Jun 25, 2013 at 12:42 PM, Hans of Guardian <hans at guardianproject.info> wrote:
> 
> I just had a thought for a simple way to manage multiple virtual disks in the same process when using IOCipher.  If there was just a ChangeVirtualDisk() method that you give the path too, that would change the context of any following IOCipher calls.  It would not work for copying between to the two virtual disks, but we could provide a special method for that too.
> 
> This could be useful to support temporary virtual disks to do things like secure scratch space for things that need to be rapidly deleted.
> 
> .hc
> _______________________________________________
> Guardian-dev mailing list
> 
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
> 
> To Unsubscribe
>         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>         Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/josh%40vitriolix.com
> 
> You are subscribed as: josh at vitriolix.com
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20130626/992636b7/attachment.html>