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
OpenPGP: hardwareCrypto functions #167
Comments
From evn@google.com on August 11, 2014 21:19:37 Can you give a bit more detail Josh? |
From evn@google.com on August 11, 2014 23:47:04 Labels: Component-Logic Maintainability |
From jo...@google.com on August 12, 2014 09:11:59 In various places, primarily in schemes and key generation, we have places for code to interact with hardware. No code is written there yet since we are waiting on a CL to land that gives us an API we can use to talk to a hardware device. Once that CL is submitted and integrated into e2e, we should write code to interact with it. |
From jo...@google.com on August 15, 2014 12:24:12
|
Hi, |
From jo...@google.com on August 11, 2014 21:30:47
We need to write the functions that interact with the Chrome App API for hardware devices once that API is integrated into e2e
Original issue: http://code.google.com/p/end-to-end/issues/detail?id=130
The text was updated successfully, but these errors were encountered: