8 Commits (364b7832811c19106456b3b30a34c7097a0b526e)

Author	SHA1	Message	Date
zelig	364b783281	changes that fix it all: ... - set proper public key serialisation length in pubLen = 64 - reset all sizes and offsets - rename from DER to S (we are not using DER encoding) - add remoteInitRandomPubKey as return value to respondToHandshake - add ImportPublicKey with error return to read both EC golang.elliptic style 65 byte encoding and 64 byte one - add ExportPublicKey falling back to go-ethereum/crypto.FromECDSAPub() chopping off the first byte - add Import - Export tests - all tests pass	10 years ago
zelig	e252c634cb	first stab at integrating crypto in our p2p ... - abstract the entire handshake logic in cryptoId.Run() taking session-relevant parameters - changes in peer to accomodate how the encryption layer would be switched on - modify arguments of handshake components - fixed test getting the wrong pubkey but it till crashes on DH in newSession()	10 years ago
zelig	1803c65e40	integrate cryptoId into peer and connection lifecycle	10 years ago
zelig	489d956283	completed the test. FAIL now. it crashes at diffie-hellman. ECIES -> secp256k1-go panics	10 years ago
zelig	3b6385b146	handshake test to crypto	10 years ago
zelig	714b955d6e	fix crash ... - add session token check and fallback to shared secret in responder call too - use explicit length for the types of new messages - fix typo resp[resLen-1] = tokenFlag	10 years ago
zelig	b855f671a5	rewrite to comply with latest spec ... - correct sizes for the blocks : sec signature 65, ecies sklen 16, keylength 32 - added allocation to Xor (should be optimized later) - no pubkey reader needed, just do with copy - restructuring now into INITIATE, RESPOND, COMPLETE -> newSession initialises the encryption/authentication layer - crypto identity can be part of client identity, some initialisation when server created	10 years ago
zelig	4e52adb84a	add crypto auth logic to p2p	10 years ago