> I have created my X25519 pub/priv keypair with:
> openssl genpkey -algorithm X25519
> -out $dir/private/$clientemail-X.key.$format
Are you sure you didn't want ed25519 instead? X25519 is a key agreement
menthod, not a signature method.
> openssl req -config $dir/openssl-intermediate.cnf
> -key $dir/private/$clientemail-X.key.$format
> -subj '$DN' -new -out $dir/csr/$clientemail-X.csr.$format
> which is what I used for ED25519 client certs. But I get an error:
> 140487683954496:error:0608D096:digital envelope
> routines:EVP_PKEY_sign_init:operation not supported for this
Not surprising, why do you expect this to work?
> Can someone point me to what I am missing?
> Oh, and I am ASSuMEing that a CA cert of ED25519 signs an X25519 client
> cert. Haven't found instructions on this, but it seems reasonable...
Openssl genpkey -algorithm x25519 -out priv.pem openssl pkey -in priv.pem -pubout -out pub.pem Target: my code on the stm32 is based on this example: https. Tested with OpenSSL v1.1.0g, Python does not support selection of curve Curve25519 with ssl.ctx.setecdhcurve('X25519'). Additionally the DH key exchange parameters (which curve has been chosen, what DH bit size was used) are not available through any SSL or Context method. Msg312238 - Author: Christian Heimes (christian.heimes).
OpenSSL provides two command line tools for working with keys suitable for Elliptic Curve (EC) algorithms:
The only Elliptic Curve algorithms that OpenSSL currently supports are Elliptic Curve Diffie Hellman (ECDH) for key agreement and Elliptic Curve Digital Signature Algorithm (ECDSA) for signing/verifying.
x25519, ed25519 and ed448 aren't standard EC curves so you can't use ecparams or ec subcommands to work with them. If you need to generate x25519 or ed25519 keys then see the genpkey subcommand.
EC Private Key File Formats
By default OpenSSL will work with PEM files for storing EC private keys. These are text files containing base-64 encoded data. A typical traditional format private key file in PEM format will look something like the following, in a file with a '.pem' extension:
Or, in an encrypted form like this:
You may also encounter PKCS8 format private keys in PEM files. These look like this:
Or, in an encrypted form like this:
PKCS8 private key files, like the above, are capable of holding many different types of private key - not just EC keys.
You can convert between these formats if you like. All of the conversion commands can read either the encrypted or unencrypted forms of the files however you must specify whether you want the output to be encrypted or not. To convert a PKCS8 file to a traditional encrypted EC format use:
You can replace the first argument 'aes-128-cbc' with any other valid openssl cipher name (see Manual:enc(1) for a list of valid cipher names). To convert a PKCS8 file to a traditional unencrypted EC format, just drop the first argument:
Or to convert from a traditional EC format to an encrypted PKCS8 format use:
Or to a non-encrypted PKCS8 format use:
Note that by default in the above traditional format EC Private Key files are not encrypted (you have to explicitly state that the file should be encrypted, and what cipher to use), whilst for PKCS8 files the opposite is true. The default is to encrypt - you have to explicitly state that you do not want encryption applied if appropriate using the '-nocrypt' option.
As well as PEM format all of the above types of key file can also be stored in DER format. This is a binary format and so is not directly human readable - unlike a PEM file. A PEM file is essentially just DER data encoded using base 64 encoding rules with a header and footer added. Often it is more convenient to work with PEM files for this reason.
The openssl commands typically have options '-inform DER' or '-outform DER' to specify that the input or output file is DER respectively. So for example the command to convert a PKCS8 file to a traditional encrypted EC format in DER is the same as above, but with the addition of '-outform DER':
Note that you cannot encrypt a traditional format EC Private Key in DER format (and in fact if you attempt to do so the argument is silently ignored!). The same is not true for PKCS8 files - these can still be encrypted even in DER format. So for example the following will convert a traditional format key file to an ecrypted PKCS8 format DER encoded key:
EC Public Key File Formats
EC Public Keys are also stored in PEM files. A typical EC public key looks as follows:
This format is used to store all types of public keys in OpenSSL not just EC keys.
How To Use Openssl
It is possible to create a public key file from a private key file (although obviously not the other way around!):
As above a DER encoded version can be created using '-outform DER':
Generating EC Keys and Parameters
An EC Parameters file contains all of the information necessary to define an Elliptic Curve that can then be used for cryptographic operations (for OpenSSL this means ECDH and ECDSA). OpenSSL contains a large set of pre-defined curves that can be used. The full list of built-in curves can be obtained through the following command:
An EC parameters file can then be generated for any of the built-in named curves as follows:
Replace secp256k1 in the above with whichever curve you are interested in.
Keys can be generated from the ecparam command, either through a pre-existing parameters file or directly by selecting the name of the curve. To generate a private/public key pair from a pre-eixsting parameters file use the following:
Or to do the equivalent operation without a parameters file use the following:
Information on the parameters that have been used to generate the key are embedded in the key file itself.
By default, when creating a parameters file, or generating a key, openssl will only store the name of the curve in the generated parameters or key file, not the full set of explicit parameters associated with that name. For example:
This will simply confirm the name of the curve in the parameters file by printing out the following:
Openssl X25519 Support
If you wish to examine the specific details of the parameters associated with a particular named curve then this can be achieved as follows:
The above command shows the details for a built-in named curve from a file, but this can also be done directly using the '-name' argument instead of '-in'. The output will look similar to the following:
The meaning of each of these parameters is discussed further on this page.
Parameters and key files can be generated to include the full explicit parameters instead of just the name of the curve if desired. This might be important if, for example, not all the target systems know the details of the named curve. In OpenSSL version 1.0.2 new named curves have been added such as brainpool512t1. Attempting to use a parameters file or key file in versions of OpenSSL less than 1.0.2 with this curve will result in an error:
This problem can be avoided if explicit parameters are used instead. So under OpenSSL 1.0.2 you could create a parameters file like this:
Looking at the parameters file you will notice that it is now much longer:
The full parameters are included rather than just the name. This can now be processed by versions of OpenSSL less than 1.0.2. So under 1.0.1:
This will correctly display the parameters, even though this version of OpenSSL does not know about this curve.
The same is true of key files. So to generate a key with explicit parameters:
This key file can now be processed by versions of openssl that do not know about the brainpool curve.
It should be noted however that once the parameters have been converted from the curve name format into explicit parameters it is not possible to change them back again, i.e. there is no utility to take a set of explicit parameters and work out which named curve they are associated with.