We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auth = auth-size || enc-auth-body auth-size = size of enc-auth-body, encoded as a big-endian 16-bit integer auth-vsn = 4 auth-body = [sig, initiator-pubk, initiator-nonce, auth-vsn, ...] enc-auth-body = ecies.encrypt(recipient-pubk, auth-body || auth-padding, auth-size) auth-padding = arbitrary data
Looking at various implementations, it seems like sig is:
sig = secp256k1.sign(ephemeral-privkey , shared-secret ^ initiator-nonce)
and shared-secret is:
shared-secret = ecdh.agree(privkey, remote-pubk)
The text was updated successfully, but these errors were encountered:
Also, there might need to be a definition for auth-padding and clarification on auth-size.
auth-padding
auth-size
Is auth-size = len(auth-body || auth-padding) instead of size of enc-auth-bod
auth-size = len(auth-body || auth-padding)
size of enc-auth-bod
Sorry, something went wrong.
Ah, I suppose that auth-size can be known prior to ecies encryption using: len(auth-body || auth-padding) + 113. Does that sound correct?
len(auth-body || auth-padding) + 113
Yes, 113 is the fixed ecies overhead which can be used to pre-calculate the total size.
No branches or pull requests
Looking at various implementations, it seems like sig is:
and shared-secret is:
The text was updated successfully, but these errors were encountered: