-
Notifications
You must be signed in to change notification settings - Fork 10
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
Running on Hololens UWP #32
Comments
You know, I coded very early on the Hololens and didn't think to try this library on it... The issue is with trying to be fancy in assuring memory gets locked and zeroed with SecureArray by calling into the OS. I'll work on getting that working in the Hololens. |
Maybe the issue is with Hololens2 which is ARM-based. Is there a way to help you with that issue. I think the file system of the hololens is not open, so I cannot check dlls easily. |
I don't think it is an ARM vs Intel issue because P/Invoke works on both (according to interwebs and my initial fiddling). And, I've found contradictory documentation about calling these things. I did find https://docs.microsoft.com/en-us/previous-versions/mt186421(v=vs.85) which, I think, lists some of the things I can P/Invoke. I’m pretty sure that isn’t all the things because the stackoverflow tells me to detect if the code is running on UWP is to P/Invoke GetCurrentPackageFullName(). That isn’t in the list. As a workaround for now, you can create your own Argon2Config and set the SecureArrayCall field to an instance of DefaultWebSecureArrayCall. Then use that Argon2Config in calls to hash and verify. That uses the version of SecureArray that runs in webassembly. That version doesn't attempt to lock memory in RAM and only hopes to zero the memory. It is hard to zero memory when you are done with it in light of optimizers and such that notice "you are trying to zero the memory but you don't use it afterwards so I'm going to help you by not eating CPU performing that action" :-) |
Hi everyone,
I tried using Argon2 on Hololens, but there seem to be problems accessing the windows api from a UWP project. Sometimes Hololens is a bit special...so not sure, if it is a general UWP Problem.
Here is the stack trace I got. I think UWP is restricted on accessing native APIs, but I did not dig into this. Do you have any experience on this?
Thanks
Alex
The text was updated successfully, but these errors were encountered: