7 Commits (ea3851d15f263a79e1a414bdd4c4842f10eb7134)

Author	SHA1	Message	Date
Jason Rhinelander	860c5efd47	Derived key fixes ... The reason things weren't working here is because libsodium does something completely unintuitive and called the seed the "secret key" when it isn't, it's the seed. This adds a new PrivateKey class (alongside the existing SecretKey and PubKey) that holds just a private key value but no seed -- which we need to do because there is no way we can get a seed after calculating a derived keypair. With these changes, we now generate exactly the same keys and subkeys as Tor (and a new test case uses values generated in Tor to verify this). This is incomplete -- the subkey signing code is still not implemented; it has to be adapted to create a signature from a PrivateKey rather than a SecretKey which will probably requiring working around/reimplementing some of what libsodium does for creating a signature since it expects "secret keys" i.e. the seed.	5 years ago
Jeff Becker	99eb7726ff	initial dht key blinding	5 years ago
Stephen Shelton	2c6226f54a	Backup SNApp keys when migrating to new ed25519 crypto	5 years ago
Michael	491fee206b	Port code to use CryptoManager over passing Crypto pointers	5 years ago
Michael	3f53965b71	Remove all use of IBEncodeMessage	5 years ago
Michael	a83be769e2	More explicit error when keyfile is not a valid file	5 years ago
michael-loki	e36ddfb093	Fixup casing (#543) ... * Rename Identity.hpp to identity.hpp * Rename Identity.cpp to identity.cpp * Rename Info.hpp to info.hpp * Rename Intro.cpp to intro.cpp * Rename Intro.hpp to intro.hpp	6 years ago