OPENSSL-ECPARAM(1SSL)
π NAME π
bestie, this is openssl-ecparam β the OpenSSL command that does EC parameter manipulation and generation. elliptic curve vibes only β¨
β¨ SYNOPSIS β¨
openssl ecparam [-help] [-inform DER|PEM] [-outform DER|PEM] [-in
filename] [-out filename] [-noout] [-text] [-check] [-check_named]
[-name arg] [-list_curves] [-conv_form arg] [-param_enc arg] [-no_seed]
[-genkey] [-rand files] [-writerand file] [-provider name]
[-provider-path path] [-provparam [name:]key=value] [-propquery propq]
π DESCRIPTION π
okay so. this command manipulates or generates EC parameter files. that's the whole job. it's giving utility icon π
and here's the tea bestie: OpenSSL currently cannot generate new groups. so this command can only make EC parameters from curves it already knows about β the named curves. no custom curve-building from scratch, unfortunately π
π OPTIONS π
-helpβ prints a usage message. little help menu moment π«Ά-inform DER|PEMβ tells it what input format the EC parameters are in. unspecified by default. seeopenssl-format-options(1)for the details, bestie.-outform DER|PEMβ what output format to use. default isPEM. again,openssl-format-options(1)has the deets. oh and fun fact: the parameters are encoded asEcpkParametersexactly as specified in IETF RFC 3279. very official of them β-in filenameβ the input file to read parameters from. if you don't pass this, it reads from standard input. no file? no problem, stdin's got you π¦-out filenameβ the output file to write parameters to. if you don't include this option, standard output is used. and yes, you can set the output filename to be the same as the input filename, which means it replaces the file contents. heads up though: > file I/O is not atomic. the output file gets truncated and then written. so like, don't yank the cable mid-write, iykyk π-nooutβ this one inhibits the output of the encoded version of the parameters. so it just... doesn't print the encoded blob. slay.-textβ prints the EC parameters in human readable form. for when you wanna actually read the thing with your eyeballs π-checkβ validates the elliptic curve parameters. vibe check, but for curves π-check_namedβ validates the elliptic name curve parameters by checking whether the curve parameters match any of the built-in curves. detective mode π-name argβ use the EC parameters with the specified 'short' name. wanna know your options? run-list_curvesand it'll hand you every currently implemented EC parameters name. periodt.-list_curvesβ prints out a list of all currently implemented EC parameters names, and then exits. that's it, that's the whole job β¨-conv_form argβ how the points on the elliptic curve get converted into octet strings. possible values are:compressed,uncompressed(the default value), andhybrid. if you want the full lore on point conversion forms, go read the X9.62 standard. also, note: due to patent issues, thecompressedoption is disabled by default for binary curves, and you can only enable it by defining the preprocessor macroOPENSSL_EC_BIN_PT_COMPat compile time. no cap, that's the rule π-param_enc argβ how the elliptic curve parameters themselves are encoded. possible values:named_curve(the ec parameters are specified by an OID) orexplicit(the ec parameters are explicitly given β see RFC 3279 for the definition of the EC parameters structures). default value isnamed_curve. and btw, theimplicitlyCAalternative as specified in RFC 3279? currently not implemented in OpenSSL, bestie. it's just not there π-no_seedβ this option inhibits the 'seed' for the parameter generation from being included in theECParametersstructure (see RFC 3279). keep your seed to yourself, queen πΈ-genkeyβ this will generate an EC private key using the specified parameters. main character energy, generating keys and all π-rand files,-writerand fileβ check out "Random State Options" inopenssl(1)for all the details.-provider name-provider-path path-provparam [name:]key=value-propquery propqβ these four are the provider crew. see "Provider Options" inopenssl(1),provider(7), andproperty(7). they're all in the group chat together π
also quick shoutout: openssl-genpkey(1) and openssl-pkeyparam(1) can do everything this command can do, AND they support other public key types too. so they're like, the upgraded versions. still, this one ate π
π₯ EXAMPLES π₯
the docs for openssl-genpkey(1) and openssl-pkeyparam(1) contain examples that are equivalent to the ones listed right here, bestie.
to create EC parameters with the group 'prime192v1':
openssl ecparam -out ec_param.pem -name prime192v1
to create EC parameters with explicit parameters:
openssl ecparam -out ec_param.pem -name prime192v1 -param_enc explicit
to validate given EC parameters:
openssl ecparam -in ec_param.pem -check
to create EC parameters and a private key:
openssl ecparam -out ec_key.pem -name prime192v1 -genkey
to change the point encoding to 'compressed':
openssl ecparam -in ec_in.pem -out ec_out.pem -conv_form compressed
to print out the EC parameters to standard output:
openssl ecparam -in ec_param.pem -noout -text
π SEE ALSO π
openssl(1), openssl-pkeyparam(1), openssl-genpkey(1), openssl-ec(1), openssl-dsaparam(1)
π HISTORY π
- the
-Coption was removed in OpenSSL 3.0. gone, bye, won't be missed π - the
-engineoption was removed in OpenSSL 4.0. also gone π«Ά
π COPYRIGHT π
Copyright 2003-2021 The OpenSSL Project Authors. All Rights Reserved.
Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.
aaaand that's the whole page, bestie π this was OpenSSL β openssl-ecparam, section 1SSL β version 4.0.3, dated 2026-09-29. go read your curves, mwah πβ¨π¦
π¦ where this page comes from
- ubuntu stonking: openssl 4.0.3-1ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms