Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

Use the RustCrypto crates instead of ring? #13

Open
newpavlov opened this issue Nov 20, 2020 · 1 comment
Open

Use the RustCrypto crates instead of ring? #13

newpavlov opened this issue Nov 20, 2020 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@newpavlov
Copy link

This project already includes several RustCrypto crates via the dalek crates. As far as I can see from it you only use AES-GCM, SHA-256, HMAC, and HKDF. I think such migration will allow to simplify code and build process, as well as make the crate more portable. Of course the linked crates have several disadvantages compared to ring:

  • Lack of runtime CPUID-based detection in the aes-gcm crate.
  • A bit slower software implementation of SHA-256.

The latter issue can be compensated a bit by enabling the asm feature (though performance still will not be quite on par with ring). Also if CPU has SHA-extension, the crate will detect it during runtime and will use efficient intrinsic-based code.

If you have any questions regarding RustCrypto crates, I will be glad to answer them.

@woodruffw
Copy link
Collaborator

Thanks for the information! We don't currently have any engineers working on molasses, but we'd be happy to review any PRs that simplify both the code and the build.

@woodruffw woodruffw added enhancement New feature or request help wanted Extra attention is needed labels Nov 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants