问题
I was wondering if there was (and I hope there is) a standard for public key size for ECDH (Elliptic Curve Diffie-Hellman) and ECDSA (Elliptic Curve Digital Signature Algorithm) for every curve type over prime fields (192, 224, 256, 384 and 521).
回答1:
If you use one of the "named curves" then the public key size is fixed and dependent on the "field size" of your underlying curve.
Compressed vs. uncompressed representation
Public key sizes further depend on whether the "uncompressed" representation or the "compressed" representation is used. In the uncompressed form, the public key size is equal to two times the field size (in bytes) + 1, in the compressed form it is field size + 1. So if your curve is defined on secp256r1 (also called NIST P-256 or X9.62 prime256v1), then the field size is 256 bits or 32 bytes. And therefore the public key would be exactly 65 bytes (32*2 +1) long in the uncompressed form and 33 bytes (32 +1) long in the compressed form.
The uncompressed form consists of a 0x04 (in analogy to the DER OCTET STRING tag) plus the concatenation of the binary representation of the X coordinate plus the binary representation of the y coordinate of the public point.
GF(2^p) case
If the underlying field is GF(2^p) then x and y can be thought of as elements from [0, n-1]. They are encoded the usual way integers are encoded and the remaining space to fill exactly log2(p)/8 bytes is padded with zeroes.
GF(2^m) case
For GF(2^m) x and y can be thought of as polynomials a_0x_0 + ... + a_m-1 with coefficients a_i 0 or 1. Their binary representation is simply the concatenation of the coefficients.
Further reading
The exact details can be found in SEC1v2. (Especially section 2.3.3 Elliptic-Curve-Point-to-Octet-String Conversion on pages 10 and 11.)
回答2:
I was looking for answer quite long and wanted to share mine in Java. My task was to get key size from X509Certificate (website to be correct)
Method #1 - actually calculating:
ECPublicKeyImpl ecPublicKey = (ECPublicKeyImpl) certificate.getPublicKey();
int publicKeyLength = (ecPublicKey.getEncodedPublicValue().length - 1) / 2 * 8;
(Verification if first byte is 0x04 might be added)
Method #2 - extracting from some "internals":
ECParameterSpec spec = ecPublicKey.getParams();
AlgorithmParameters algorithmParameters = AlgorithmParameters.getInstance("EC");
algorithmParameters.init(spec);
Provider provider = algorithmParameters.getProvider();
provider.get("KeyPairGenerator.EC KeySize");
来源：https://stackoverflow.com/questions/6665353/is-there-a-standardized-fixed-length-encoding-for-ec-public-keys