https://github.com/paddor/djb-crypto

Pure Ruby implementations of Daniel J. Bernstein's cryptographic primitives and protocols. DO NOT USE IN PRODUCTION!
https://github.com/paddor/djb-crypto

Last synced: 12 days ago
JSON representation

Pure Ruby implementations of Daniel J. Bernstein's cryptographic primitives and protocols. DO NOT USE IN PRODUCTION!

• Host: GitHub
• URL: https://github.com/paddor/djb-crypto
• Owner: paddor
• Created: 2015-06-07T12:45:36.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2015-06-17T13:57:00.000Z (over 9 years ago)
• Last Synced: 2024-11-11T23:53:44.176Z (about 2 months ago)
• Language: C
• Size: 219 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
DjbCrypto

=========

DO NOT USE IN PRODUCTION! This is just an experiment for me to learn more about cryptography.

Even though these implementations should produce correct results, they

still don't provide high security because of possible side-channel attacks. So

"offline" usage should be okay, but still. I'm by no means a cryptography

expert.

If you're interested in using any of these primitives or sane combinations

of them in Ruby, please refer to the excellent library [RbNaCl](https://github.com/cryptosphere/rbnacl).

Coding rules

------------

I tried to respect the coding rules from 

https://cryptocoding.net/index.php/Coding_rules

Good:

* most of them are already met by the design of the algorithms (rule 1, 2, 3, 4)

* I tried to keep the API as easy and safe as possible (rule 6, 7)

* only unsigned integers have been used in the C extensions (rule 8)

* Ruby's GC will clean secret data, the C extensions won't hold anything in memory (rule 11)

* for random data, the Ruby standard library's SecureRandom is used (rule 12)

Bad:

* I'm not going to verify the assembly code for this experiment (rule 5)

* I guess did use the same types for different things, duh? Rules are incomplete. (rule 9, 10)