rogerioacp / oram Goto Github PK

The position map of position-based rams is currently being stored only in-memory or in an external file. There is no support for recursive ORAMS.

Create a position map that takes as input the location of a block to be accessed as input. This position map will contain a very small state that is updated dynamically by a client application that keeps track of the actual location of the blocks.

Sorry for uploading this stupid issue. I'm a stater of oram. Right now, I have a c++ program, can I use the API of this path oram to handle oblivious access? Or do I need to modify it?
Another question is do you know any existing oram implementations or libraries that could be directly used for the user's own program?
Looks like lots of oram implementations just build a "simulator", not a practicing system

Change the goal of logStashes function to a new function that takes as input the ORAMState and returns a struct with the current number of stash blocks.

The current interface and data structures of the ORAM implementations requires the compilation of a single binary for each implementation. Furthermore, it's not possible to compose ORAMs as block boxes. For instance, the Forest ORAM implements some of the same functionality as PATH ORAM when it could use it as a block box. To fix this, each ORAM implementation will have to return a public struct that contains the interface to read and write blocks.

With the issue #10 some detailed information, which was possible incorrect, on the number of stashes and blocks per partition on Forest ORAM were removed.

Add to the Forest ORAM the following statistics:

• Number of stashed nodes per partition.
• Number of maximum stashed nodes per partition at the end of execution.
• Number of blocks stored per partition.
• Maximum number of blocks stored per partition.

These statistics should be activated with different flags from the current --enable-stash-count

Replace the filename string in every AMOFile function with a generic struct that is only known and used by a client application.