-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design of Memory Locking #50
Comments
On Fri, Aug 09, 2013 at 12:17:40AM -0700, satvikc wrote:
Maybe we should try a simpler approach first. I think we should look Regards ppk |
I have a few questions
There is some code available at https://github.com/satvikc/raaz/blob/x-memory/raaz-primitives/Raaz/Util/SecureMemory.hs Right now I am just using list instead of a tree for simplicity. We can change that later once we get this working. |
On Mon, Aug 12, 2013 at 09:58:40PM -0700, satvikc wrote:
Regards ppk |
Yeah, mallocForeignPtr aligns at alignment of the datatype and not the page boundary. |
I have a way of doing that by defining the |
On Mon, Aug 12, 2013 at 10:59:41PM -0700, satvikc wrote:
I donot like this option see if there is some other way. For Ptrs |
But that has type `Int -> Int -> (Ptr a -> IO b) -> IO b). We want to On Tue, Aug 13, 2013 at 11:49 AM, Piyush P Kurur
Satvik Chauhan |
I have written some code for memory locking. Can you have a look. Also I am not sure how to write testcases for those. |
A high-level design for memory locking is given below. I am just mentioning types for brevity.
A problem with the approach is nothing restricts user from using
newMemory
andsecureMemory
in different monads. For example, user can useCryptoCell
returned fromnewMemory :: IO CryptoCell
insidesecureMemory
.The text was updated successfully, but these errors were encountered: