Cryptography Self-encrypting deception: weaknesses in the encryption of solid state drives (SSDs) |
- Self-encrypting deception: weaknesses in the encryption of solid state drives (SSDs)
- Cryptography During the French and American Wars in Vietnam
- Good Applied Cryptography Books
- Is it safe to use a nacl.box private key as a seed to create a nacl.sign key?
| Self-encrypting deception: weaknesses in the encryption of solid state drives (SSDs) Posted: 05 Nov 2018 03:46 PM PST |
| Cryptography During the French and American Wars in Vietnam Posted: 05 Nov 2018 05:45 AM PST |
| Good Applied Cryptography Books Posted: 05 Nov 2018 04:58 PM PST I'm looking for good books about applied cryptophraphy. I have Serious Cryptography by Jean-Philippe Aumasson, and have been recommended Cryptography Engineering Principles which the note that the material is old and sometimes out of date. Are there any good current Applied Crypto texts? [link] [comments]  |
| Is it safe to use a nacl.box private key as a seed to create a nacl.sign key? Posted: 05 Nov 2018 11:34 AM PST In the golang library, the nacl.box private key is generated from 32 random bytes. In the nacl.sign package (using ed25519 package), the private key is also generated from 32 random bytes (used as the seed). The purpose of this, is so I can store a single 32 byte recovery "key" and then use it to derive both nacl.box and nacl.sign keys. This seems safe since both are generated from 32 random bytes. The only caveat I see from doing this is that if there is a flaw in one key it will break the other? Which I think I am ok with. So I would do: - privateKey = random 32 bytes - create nacl.box key, by doing curve25519.ScalarBaseMult(publicKey, privateKey) (this is what nacl.box.GenerateKey does) - create nacl.sign key, by doing ed25519.NewKeyFromSeed(privateKey) That way I can have both a nacl.box and nacl.sign key from the same 32 byte private key. I'm not a cryptographer, so I apologize if this is a weird question. [link] [comments]  |
| You are subscribed to email updates from Cryptography news and discussions. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment