The encryption layer is simply an application of the mirage-block-ccm library, which you can find here: https://github.com/sg2342/mirage-block-ccm
I have a forked version of the repository which is required for running my project. Rupert On Thu, Feb 18, 2016 at 10:44 AM Thomas Gazagnaire <[email protected]> wrote: > Hi, > > That looks great! Your slides mention block encryption but a (very) quick > glance at the source code didn't seem to show an obvious place where this > is done. Can you detail a bit more how the block encryption works or will > work? > > Thanks, > Thomas > > On 18 Feb 2016, at 06:28, Rupert Horlick <[email protected]> wrote: > > Hi all, > > I just wanted to let you know that I made the code for my Part II project > publicly available at: https://github.com/ruhatch/mirage-oram > > It is an implementation of the cryptographic primitive Path ORAM, > satisfying Mirage's V1_LWT.BLOCK interface. > > On top of BLOCK, I built an implementation of BTrees, which I then used > for the inode index of a small File System. On top of that I built an > indexing and search module that keeps an inverted index in the file system > and does some simple phrase-query based search. > > Currently this is all in one repo, but I plan to break it out into > individual repos and push them to OPAM once I'm done with the project. > > Feel free to take a look around and please let me know if you spot > anything obviously wrong! > > Kind regards, > > Rupert > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > >
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
