Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify state of Constant Time safety of the repo and platforms #2

Open
vhnatyk opened this issue May 29, 2019 · 1 comment
Open

Clarify state of Constant Time safety of the repo and platforms #2

vhnatyk opened this issue May 29, 2019 · 1 comment

Comments

@vhnatyk
Copy link
Owner

vhnatyk commented May 29, 2019

Needs some research on CT safety of code/dependencies and platforms. At glance - MCU's with secure enclave are, supposedly, immune to timing attacks due to internal separate hardware clock and tamper-proof protection. Needs confirmation though - there are some practical studies on side-channel attacks on non-secure MCU used in Trezor wallet. WASM in turn isn't CT-safe yet, though there are extensions with implemented CT-safety
@dheeraj-721
Copy link

Hi @vhnatyk I need to create wasm files in zengo_mpc_eddsa code. Please help me in that. I am not able to create wasm files.

Thanks

@dheeraj-721 dheeraj-721 mentioned this issue Jun 7, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vhnatyk @dheeraj-721