neulab/tldr huggingface dataset:
/verbosity:<level> Display this amount of information in the event log. The available verbosity levels are: q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]. (Short form: /v)
Example: /verbosity:quiet
/consoleloggerparameters:<parameters Parameters to console logger. (Short form: /clp)
The available parameters are: PerformanceSummary      Show time spent in tasks, targets and projects. Summary                 Show error and warning summary at the end. NoSummary               Don't show error and warning summary at the end. ErrorsOnly              Show only errors. WarningsOnly            Show only warnings. NoItemAndPropertyList   Don't show list of items and properties at the start of each project build. ShowCommandLine         Show TaskCommandLineEvent messages ShowTimestamp           Display the Timestamp as a prefix to any message. ShowEventId             Show eventId for started events, finished events, and messages ForceNoAlign            Does not align the text to the size of the console buffer DisableConsoleColor     Use the default console colors for all logging messages. DisableMPLogging        Disable the multiprocessor logging style of output when running in non-multiprocessor mode. EnableMPLogging         Enable the multiprocessor logging style even when running in non-multiprocessor mode. This logging style is on by default. ForceConsoleColor       Use ANSI console colors even if console does not support it Verbosity               overrides the /verbosity setting for this logger.
Example: /consoleloggerparameters:PerformanceSummary;NoSummary;Verbosity=minimal
/noconsolelogger Disable the default console logger and do not log events to the console. (Short form: /noconlog)
/fileLogger[n] Logs the build output to a file. By default the file is in the current directory and named "msbuild[n].log". Events from all nodes are combined into a single log. The location of the file and other parameters for the fileLogger can be specified through the addition of the "/fileLoggerParameters[n]" switch.  "n" if present can be a digit from 1-9, allowing up to 10 file loggers to be attached. (Short form: /fl[n])
/fileloggerparameters[n]:<parameters> Provides any extra parameters for file loggers. The presence of this switch implies the corresponding /filelogger[n] switch.  "n" if present can be a digit from 1-9.
/fileloggerparameters is also used by any distributed file logger, see description of /distributedFileLogger.  (Short form: /flp[n]) The same parameters listed for the console logger are available. Some additional available parameters are:
LogFile     path to the log file into which the build log will be written. Append      determines if the build log will be appended to or overwrite the log file. Setting the switch appends the build log to the log file; Not setting the switch overwrites the contents of an existing log file.  The default is not to append to the log file. Encoding    specifies the encoding for the file, for example, UTF-8, Unicode, or ASCII Default verbosity is Detailed.
/fileLoggerParameters:LogFile=MyLog.log;Append;Verbosity=diagnostic;Encoding=UTF-8
/flp:Summary;Verbosity=minimal;LogFile=msbuild.sum /flp1:warningsonly;logfile=msbuild.wrn /flp2:errorsonly;logfile=msbuild.err
/distributedlogger:<central logger>*<forwarding logger> Use this logger to log events from MSBuild, attaching a different logger instance to each node. To specify multiple loggers, specify each logger separately.  (Short form /dl)
The <logger> syntax is: [<logger class>,]<logger assembly>[;<logger parameters>] The <logger class> syntax is: [<partial or full namespace>.]<logger class name> The <logger assembly> syntax is: {<assembly name>[,<strong name>] | <assembly file>} The <logger parameters> are optional, and are passed to the logger exactly as you typed them. (Short form: /l)
Examples: /dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral /dl:MyLogger,/mylibs/My.dll*ForwardingLogger,/mylibs/Loggger.dll
/distributedFileLogger Logs the build output to multiple log files, one log file per MSBuild node. The initial location for these files is the current directory. By default the files are called "MSBuild<nodeid>.log". The location of the files and other parameters for the fileLogger can be specified with the addition of the "/fileLoggerParameters" switch.
If a log file name is set through the fileLoggerParameters switch the distributed logger will use the fileName as a template and append the node id to this fileName to create a log file for each node.
/logger:<logger> Use this logger to log events from MSBuild. To specify multiple loggers, specify each logger separately. The <logger> syntax is: [<logger class>,]<logger assembly>[;<logger parameters>] The <logger class> syntax is: [<partial or full namespace>.]<logger class name> The <logger assembly> syntax is: {<assembly name>[,<strong name>] | <assembly file>} The <logger parameters> are optional, and are passed to the logger exactly as you typed them. (Short form: /l)
Examples: /logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral /logger:XMLLogger,/MyLoggers/MyLogger.dll;OutputAsHTML
/binaryLogger[:output.binlog] Serializes all build events to a compressed binary file.  By default the file is in the current directory and named "msbuild.binlog". The binary log is a detailed description of the build process that can later be used to reconstruct text logs and used by other analysis tools. A binary log is usually 10-20x smaller than the most detailed text diagnostic-level log, but it contains more information.  (Short form: /bl)
Examples: /bl /bl:output.binlog /bl:../../custom.binlog /binaryLogger
/warnaserror[:code[;code2]] List of warning codes to treats as errors.  Use a semicolon or a comma to separate multiple warning codes. To treat all warnings as errors use the switch with no values.  (Short form: /err[:c;[c2]])
Example: /warnaserror:MSB4130
When a warning is treated as an error the target will continue to execute as if it was a warning but the overall build will fail.
/warnasmessage[:code[;code2]] List of warning codes to treats as low importance messages.  Use a semicolon or a comma to separate multiple warning codes.  (Short form: /nowarn[:c;[c2]])
Example: /warnasmessage:MSB3026
/ignoreprojectextensions:<extensions> List of extensions to ignore when determining which project file to build. Use a semicolon or a comma to separate multiple extensions.  (Short form: /ignore)
Example: /ignoreprojectextensions:.sln
/nodeReuse:<parameters> Enables or Disables the reuse of MSBuild nodes. The parameters are: True    Nodes will remain after the build completes and will be reused by subsequent builds (default) False Nodes will not remain after the build completes (Short form: /nr)
Example: /nr:true
/preprocess[:file] Creates a single, aggregated project file by inlining all the files that would be imported during a build, with their boundaries marked. This can be useful for figuring out what files are being imported and from where, and what they will contribute to the build. By default the output is written to the console window. If the path to an output file is provided that will be used instead. (Short form: /pp)
Example: /pp:out.txt
/detailedsummary Shows detailed information at the end of the build about the configurations built and how they were scheduled to nodes.  (Short form: /ds)
@<file> Insert command-line settings from a text file. To specify multiple response files, specify each response file separately.
Any response files named "msbuild.rsp" are automatically consumed from the following locations: (1) the directory of msbuild.dll (2) the directory of the first project or solution built
/noautoresponse Do not auto-include any MSBuild.rsp files. (Short form: /noautorsp)
/nologo Do not display the startup banner and copyright message.
/version Display version information only. (Short form: /ver)
/help  Display this usage message. (Short form: /? or /h)
mono(1),csc(1)
OPENSSL-REQ(1)                       OpenSSL                      OPENSSL-REQ(1)
openssl-req - PKCS#10 certificate request and certificate generating command
openssl req [-help] [-inform DER|PEM] [-outform DER|PEM] [-in filename] [-passin arg] [-out filename] [-passout arg] [-text] [-pubkey] [-noout] [-verify] [-modulus] [-new] [-newkey arg] [-pkeyopt opt:value] [-noenc] [-nodes] [-key filename|uri] [-keyform DER|PEM|P12|ENGINE] [-keyout filename] [-keygen_engine id] [-digest] [-config filename] [-section name] [-x509] [-CA filename|uri] [-CAkey filename|uri] [-days n] [-set_serial n] [-newhdr] [-copy_extensions arg] [-addext ext] [-extensions section] [-reqexts section] [-precert] [-utf8] [-reqopt] [-subject] [-subj arg] [-multivalue-rdn] [-sigopt nm:v] [-vfyopt nm:v] [-batch] [-verbose] [-nameopt option] [-rand files] [-writerand file] [-engine id] [-provider name] [-provider-path path] [-propquery propq]
This command primarily creates and processes certificate requests (CSRs) in PKCS#10 format. It can additionally create self-signed certificates for use as root CAs for example.
-help Print out a usage message.
-inform DER|PEM, -outform DER|PEM The input and output formats; the default is PEM.  See openssl-format-options(1) for details.
The data is a PKCS#10 object.
-in filename This specifies the input filename to read a request from or standard input if this option is not specified. A request is only read if the creation options (-new or -newkey) are not specified.
-sigopt nm:v Pass options to the signature algorithm during sign operations. Names and values of these options are algorithm-specific.
-vfyopt nm:v Pass options to the signature algorithm during verify operations. Names and values of these options are algorithm-specific.
-passin arg The password source for the request input file and the certificate input.  For more information about the format of arg see openssl-passphrase-options(1).
-passout arg The password source for the output file.  For more information about the format of arg see openssl-passphrase-options(1).
-out filename This specifies the output filename to write to or standard output by default.
-text Prints out the certificate request in text form.
-subject Prints out the certificate request subject (or certificate subject if -x509 is specified).
-pubkey Prints out the public key.
-noout This option prevents output of the encoded version of the certificate request.
-modulus Prints out the value of the modulus of the public key contained in the request.
-verify Verifies the self-signature on the request.
-new This option generates a new certificate request. It will prompt the user for the relevant field values. The actual fields prompted for and their maximum and minimum sizes are specified in the configuration file and any requested extensions.
If the -key option is not given it will generate a new RSA private key using information specified in the configuration file or given with the -newkey and -pkeyopt options, else by default with 2048 bits length.
-newkey arg This option creates a new certificate request and a new private key. The argument takes one of several forms.
rsa:nbits, where nbits is the number of bits, generates an RSA key nbits in size. If nbits is omitted, i.e. -newkey rsa specified, the default key size, specified in the configuration file is used.
All other algorithms support the -newkey alg:file form, where file may be an algorithm parameter file, created with "openssl genpkey -genparam" or an X.509 certificate for a key with appropriate algorithm.
param:file generates a key using the parameter file or certificate file, the algorithm is determined by the parameters. algname:file use algorithm algname and parameter file file: the two algorithms must match or an error occurs. algname just uses algorithm algname, and parameters, if necessary should be specified via -pkeyopt parameter.
dsa:filename generates a DSA key using the parameters in the file filename. ec:filename generates EC key (usable both with ECDSA or ECDH algorithms), gost2001:filename generates GOST R 34.10-2001 key (requires gost engine configured in the configuration file). If just gost2001 is specified a parameter set should be specified by -pkeyopt paramset:X
-pkeyopt opt:value Set the public key algorithm option opt to value. The precise set of options supported depends on the public key algorithm used and its implementation.  See "KEY GENERATION OPTIONS" in openssl-genpkey(1) for more details.
-key filename|uri This specifies the private key to use for request self-signature and signing certificates produced using the -x509 option.  It also accepts PKCS#8 format private keys for PEM format files.
-keyform DER|PEM|P12|ENGINE The format of the private key; the default is PEM.  The only value with effect is ENGINE; all others have become obsolete.  See openssl-format-options(1) for details.
-keyout filename This gives the filename to write the newly created private key to. If this option is not specified then the filename present in the configuration file is used.
-noenc If this option is specified then if a private key is created it will not be encrypted.
-nodes This option is deprecated since OpenSSL 3.0; use -noenc instead.
-digest This specifies the message digest to sign the request.  Any digest supported by the OpenSSL dgst command can be used.  This overrides the digest algorithm specified in the configuration file.
Some public key algorithms may override this choice. For instance, DSA signatures always use SHA1, GOST R 34.10 signatures always use GOST R 34.11-94 (-md_gost94), Ed25519 and Ed448 never use any digest.
-config filename This allows an alternative configuration file to be specified. Optional; for a description of the default value, see "COMMAND SUMMARY" in openssl(1).
-section name Specifies the name of the section to use; the default is req.
-subj arg Sets subject name for new request or supersedes the subject name when processing a certificate request.
The arg must be formatted as "/type0=value0/type1=value1/type2=...". Special characters may be escaped by "\" (backslash), whitespace is retained.  Empty values are permitted, but the corresponding type will not be included in the request.  Giving a single "/" will lead to an empty sequence of RDNs (a NULL-DN).  Multi-valued RDNs can be formed by placing a "+" character instead of a "/" between the AttributeValueAssertions (AVAs) that specify the members of the set. Example:
"/DC=org/DC=OpenSSL/DC=users/UID=123456+CN=John Doe"
-multivalue-rdn This option has been deprecated and has no effect.
-x509 This option outputs a certificate instead of a certificate request. This is typically used to generate test certificates.
If an existing request is specified with the -in option, it is converted to the a certificate; otherwise a request is created from scratch.
Unless specified using the -set_serial option, a large random number will be used for the serial number.
Unless the -copy_extensions option is used, X.509 extensions are not copied from any provided request input file.
X.509 extensions to be added can be specified in the configuration file or using the -addext option.
-CA filename|uri Specifies the "CA" certificate to be used for signing with the -x509 option.  When present, this behaves like a "micro CA" as follows: The subject name of the "CA" certificate is placed as issuer name in the new certificate, which is then signed using the "CA" key given as specified below.
-CAkey filename|uri Sets the "CA" private key to sign a certificate with.  The private key must match the public key of the certificate given with -CA.  If this option is not provided then the key must be present in the -CA input.
-days n When the -x509 option is being used this specifies the number of days to certify the certificate for, otherwise it is ignored. n should be a positive integer. The default is 30 days.
-set_serial n Serial number to use when outputting a self-signed certificate.  This may be specified as a decimal value or a hex value if preceded by "0x".  If not given, a large random number will be used.
-copy_extensions arg Determines how X.509 extensions in certificate requests should be handled when -x509 is given.  If arg is none or this option is not present then extensions are ignored.  If arg is copy or copyall then all extensions in the request are copied to the certificate.
The main use of this option is to allow a certificate request to supply values for certain extensions such as subjectAltName.
-addext ext Add a specific extension to the certificate (if the -x509 option is present) or certificate request.  The argument must have the form of a key=value pair as it would appear in a config file.
This option can be given multiple times.
-extensions section -reqexts section These options specify alternative sections to include certificate extensions (if the -x509 option is present) or certificate request extensions. This allows several different sections to be used in the same configuration file to specify requests for a variety of purposes.
-precert A poison extension will be added to the certificate, making it a "pre-certificate" (see RFC6962). This can be submitted to Certificate Transparency logs in order to obtain signed certificate timestamps (SCTs).  These SCTs can then be embedded into the pre-certificate as an extension, before removing the poison and signing the certificate.
This implies the -new flag.
-utf8 This option causes field values to be interpreted as UTF8 strings, by default they are interpreted as ASCII. This means that the field values, whether prompted from a terminal or obtained from a configuration file, must be valid UTF8 strings.
-reqopt option Customise the printing format used with -text. The option argument can be a single option or multiple options separated by commas.
See discussion of the  -certopt parameter in the openssl-x509(1) command.
-newhdr Adds the word NEW to the PEM file header and footer lines on the outputted request. Some software (Netscape certificate server) and some CAs need this.
-batch Non-interactive mode.
-verbose Print extra details about the operations being performed.
-keygen_engine id Specifies an engine (by its unique id string) which would be used for key generation operations.
-nameopt option This specifies how the subject or issuer names are displayed.  See openssl-namedisplay-options(1) for details.
-rand files, -writerand file See "Random State Options" in openssl(1) for details.
-engine id See "Engine Options" in openssl(1).  This option is deprecated.
-provider name -provider-path path -propquery propq See "Provider Options" in openssl(1).
The configuration options are specified in the req section of the configuration file. An alternate name be specified by using the -section option.  As with all configuration files, if no value is specified in the specific section then the initial unnamed or default section is searched too.
The options available are described in detail below.
input_password output_password The passwords for the input private key file (if present) and the output private key file (if one will be created). The command line options passin and passout override the configuration file values.
default_bits Specifies the default key size in bits.
This option is used in conjunction with the -new option to generate a new key. It can be overridden by specifying an explicit key size in the -newkey option. The smallest accepted key size is 512 bits. If no key size is specified then 2048 bits is used.
default_keyfile This is the default filename to write a private key to. If not specified the key is written to standard output. This can be overridden by the -keyout option.
oid_file This specifies a file containing additional OBJECT IDENTIFIERS.  Each line of the file should consist of the numerical form of the object identifier followed by whitespace then the short name followed by whitespace and finally the long name.
oid_section This specifies a section in the configuration file containing extra object identifiers. Each line should consist of the short name of the object identifier followed by = and the numerical form. The short and long names are the same when this option is used.
RANDFILE At startup the specified file is loaded into the random number generator, and at exit 256 bytes will be written to it.  It is used for private key generation.
encrypt_key If this is set to no then if a private key is generated it is not encrypted. This is equivalent to the -noenc command line option. For compatibility encrypt_rsa_key is an equivalent option.
default_md This option specifies the digest algorithm to use. Any digest supported by the OpenSSL dgst command can be used. This option can be overridden on the command line. Certain signing algorithms (i.e. Ed25519 and Ed448) will ignore any digest that has been set.
string_mask This option masks out the use of certain string types in certain fields. Most users will not need to change this option.
It can be set to several values default which is also the default option uses PrintableStrings, T61Strings and BMPStrings if the pkix value is used then only PrintableStrings and BMPStrings will be used. This follows the PKIX recommendation in RFC2459. If the utf8only option is used then only UTF8Strings will be used: this is the PKIX recommendation in RFC2459 after 2003. Finally the nombstr option just uses PrintableStrings and T61Strings: certain software has problems with BMPStrings and UTF8Strings: in particular Netscape.
req_extensions This specifies the configuration file section containing a list of extensions to add to the certificate request. It can be overridden by the -reqexts command line switch. See the x509v3_config(5) manual page for details of the extension section format.
x509_extensions This specifies the configuration file section containing a list of extensions to add to certificate generated when the -x509 switch is used. It can be overridden by the -extensions command line switch.
prompt If set to the value no this disables prompting of certificate fields and just takes values from the config file directly. It also changes the expected format of the distinguished_name and attributes sections.
utf8 If set to the value yes then field values to be interpreted as UTF8 strings, by default they are interpreted as ASCII. This means that the field values, whether prompted from a terminal or obtained from a configuration file, must be valid UTF8 strings.
attributes This specifies the section containing any request attributes: its format is the same as distinguished_name. Typically these may contain the challengePassword or unstructuredName types. They are currently ignored by OpenSSL's request signing utilities but some CAs might want them.
distinguished_name This specifies the section containing the distinguished name fields to prompt for when generating a certificate or certificate request. The format is described in the next section.
There are two separate formats for the distinguished name and attribute sections. If the prompt option is set to no then these sections just consist of field names and values: for example,
CN=My Name OU=My Organization emailAddress=someone@somewhere.org
This allows external programs (e.g. GUI based) to generate a template file with all the field names and values and just pass it to this command. An example of this kind of configuration file is contained in the EXAMPLES section.
Alternatively if the prompt option is absent or not set to no then the file contains field prompting information. It consists of lines of the form:
fieldName="prompt" fieldName_default="default field value" fieldName_min= 2 fieldName_max= 4
"fieldName" is the field name being used, for example commonName (or CN). The "prompt" string is used to ask the user to enter the relevant details. If the user enters nothing then the default value is used if no default value is present then the field is omitted. A field can still be omitted if a default value is present if the user just enters the '.' character.
The number of characters entered must be between the fieldName_min and fieldName_max limits: there may be additional restrictions based on the field being used (for example countryName can only ever be two characters long and must fit in a PrintableString).
Some fields (such as organizationName) can be used more than once in a DN. This presents a problem because configuration files will not recognize the same name occurring twice. To avoid this problem if the fieldName contains some characters followed by a full stop they will be ignored. So for example a second organizationName can be input by calling it "1.organizationName".
The actual permitted field names are any object identifier short or long names. These are compiled into OpenSSL and include the usual values such as commonName, countryName, localityName, organizationName, organizationalUnitName, stateOrProvinceName. Additionally emailAddress is included as well as name, surname, givenName, initials, and dnQualifier.
Additional object identifiers can be defined with the oid_file or oid_section options in the configuration file. Any additional fields will be treated as though they were a DirectoryString.
Examine and verify certificate request:
openssl req -in req.pem -text -verify -noout
Create a private key and then generate a certificate request from it:
openssl genrsa -out key.pem 2048 openssl req -new -key key.pem -out req.pem
The same but just using req:
openssl req -newkey rsa:2048 -keyout key.pem -out req.pem
Generate a self-signed root certificate:
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out req.pem
Create an SM2 private key and then generate a certificate request from it:
openssl ecparam -genkey -name SM2 -out sm2.key openssl req -new -key sm2.key -out sm2.csr -sm3 -sigopt "distid:1234567812345678"
Examine and verify an SM2 certificate request:
openssl req -verify -in sm2.csr -sm3 -vfyopt "distid:1234567812345678"
Example of a file pointed to by the oid_file option:
1.2.3.4        shortName       A longer Name 1.2.3.6        otherName       Other longer Name
Example of a section pointed to by oid_section making use of variable expansion:
testoid1=1.2.3.5 testoid2=${testoid1}.6
Sample configuration file prompting for field values:
[ req ] default_bits           = 2048 default_keyfile        = privkey.pem distinguished_name     = req_distinguished_name attributes             = req_attributes req_extensions         = v3_ca
dirstring_type = nobmp
[ req_distinguished_name ] countryName                    = Country Name (2 letter code) countryName_default            = AU countryName_min                = 2 countryName_max                = 2
localityName                   = Locality Name (eg, city)
organizationalUnitName         = Organizational Unit Name (eg, section)
commonName                     = Common Name (eg, YOUR name) commonName_max                 = 64
emailAddress                   = Email Address emailAddress_max               = 40
[ req_attributes ] challengePassword              = A challenge password challengePassword_min          = 4 challengePassword_max          = 20
[ v3_ca ]
subjectKeyIdentifier=hash authorityKeyIdentifier=keyid:always,issuer:always basicConstraints = critical, CA:true
Sample configuration containing all field values:
[ req ] default_bits           = 2048 default_keyfile        = keyfile.pem distinguished_name     = req_distinguished_name attributes             = req_attributes prompt                 = no output_password        = mypass
[ req_distinguished_name ] C                      = GB ST                     = Test State or Province L                      = Test Locality O                      = Organization Name OU                     = Organizational Unit Name CN                     = Common Name emailAddress           = test@email.address
[ req_attributes ] challengePassword              = A challenge password
Example of giving the most common attributes (subject and extensions) on the command line:
openssl req -new -subj "/C=GB/CN=foo" \ -addext "subjectAltName = DNS:foo.co.uk" \ -addext "certificatePolicies = 1.2.3.4" \ -newkey rsa:2048 -keyout key.pem -out req.pem
The certificate requests generated by Xenroll with MSIE have extensions added. It includes the keyUsage extension which determines the type of key (signature only or general purpose) and any additional OIDs entered by the script in an extendedKeyUsage extension.
The following messages are frequently asked about:
Using configuration from /some/path/openssl.cnf Unable to load config info
This is followed some time later by:
unable to find 'distinguished_name' in config problems making Certificate Request
The first error message is the clue: it can't find the configuration file! Certain operations (like examining a certificate request) don't need a configuration file so its use isn't enforced. Generation of certificates or requests however does need a configuration file. This could be regarded as a bug.
Another puzzling message is this:
Attributes: a0:00
this is displayed when no attributes are present and the request includes the correct empty SET OF structure (the DER encoding of which is 0xa0 0x00). If you just see:
Attributes:
then the SET OF is missing and the encoding is technically invalid (but it is tolerated). See the description of the command line option -asn1-kludge for more information.
OpenSSL's handling of T61Strings (aka TeletexStrings) is broken: it effectively treats them as ISO-8859-1 (Latin 1), Netscape and MSIE have similar behaviour.  This can cause problems if you need characters that aren't available in PrintableStrings and you don't want to or can't use BMPStrings.
As a consequence of the T61String handling the only correct way to represent accented characters in OpenSSL is to use a BMPString: unfortunately Netscape currently chokes on these. If you have to use accented characters with Netscape and MSIE then you currently need to use the invalid T61String form.
The current prompting is not very friendly. It doesn't allow you to confirm what you've just entered. Other things like extensions in certificate requests are statically defined in the configuration file. Some of these: like an email address in subjectAltName should be input by the user.
openssl(1), openssl-x509(1), openssl-ca(1), openssl-genrsa(1), openssl-gendsa(1), config(5), x509v3_config(5)
The -section option was added in OpenSSL 3.0.0.
All -keyform values except ENGINE and the -multivalue-rdn option have become obsolete in OpenSSL 3.0.0 and have no effect.
The -engine option was deprecated in OpenSSL 3.0.  The <-nodes> option was deprecated in OpenSSL 3.0, too; use -noenc instead.
Copyright 2000-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>.
LWP-REQUEST(1)         User Contributed Perl Documentation        LWP-REQUEST(1)
lwp-request - Simple command line user agent
lwp-request [-afPuUsSedvhx] [-m method] [-b base URL] [-t timeout] [-i if-modified-since] [-c content-type] [-C credentials] [-p proxy-url] [-o format] url...
This program can be used to send requests to WWW servers and your local file system. The request content for POST and PUT methods is read from stdin.  The content of the response is printed on stdout.  Error messages are printed on stderr.  The program returns a status value indicating the number of URLs that failed.
The options are:
-m <method> Set which method to use for the request.  If this option is not used, then the method is derived from the name of the program.
-f  Force request through, even if the program believes that the method is illegal.  The server might reject the request eventually.
-b <uri> This URI will be used as the base URI for resolving all relative URIs given as argument.
-t <timeout> Set the timeout value for the requests.  The timeout is the amount of time that the program will wait for a response from the remote server before it fails.  The default unit for the timeout value is seconds. You might append "m" or "h" to the timeout value to make it minutes or hours, respectively.  The default timeout is '3m', i.e. 3 minutes.
-i <time> Set the If-Modified-Since header in the request. If time is the name of a file, use the modification timestamp for this file. If time is not a file, it is parsed as a literal date. Take a look at HTTP::Date for recognized formats.
-c <content-type> Set the Content-Type for the request.  This option is only allowed for requests that take a content, i.e. POST and PUT.  You can force methods to take content by using the "-f" option together with "-c". The default Content-Type for POST is "application/x-www-form-urlencoded".  The default Content-type for the others is "text/plain".
-p <proxy-url> Set the proxy to be used for the requests.  The program also loads proxy settings from the environment.  You can disable this with the "-P" option.
-P  Don't load proxy settings from environment.
-H <header> Send this HTTP header with each request. You can specify several, e.g.:
lwp-request \ -H 'Referer: http://other.url/' \ -H 'Host: somehost' \ http://this.url/
-C <username>:<password> Provide credentials for documents that are protected by Basic Authentication.  If the document is protected and you did not specify the username and password with this option, then you will be prompted to provide these values.
The following options controls what is displayed by the program:
-u  Print request method and absolute URL as requests are made.
-U  Print request headers in addition to request method and absolute URL.
-s  Print response status code.  This option is always on for HEAD requests.
-S  Print response status chain. This shows redirect and authorization requests that are handled by the library.
-e  Print response headers.  This option is always on for HEAD requests.
-E  Print response status chain with full response headers.
-d  Do not print the content of the response.
-o <format> Process HTML content in various ways before printing it.  If the content type of the response is not HTML, then this option has no effect.  The legal format values are; "text", "ps", "links", "html" and "dump".
If you specify the "text" format then the HTML will be formatted as plain "latin1" text.  If you specify the "ps" format then it will be formatted as Postscript.
The "links" format will output all links found in the HTML document. Relative links will be expanded to absolute ones.
The "html" format will reformat the HTML code and the "dump" format will just dump the HTML syntax tree.
Note that the "HTML-Tree" distribution needs to be installed for this option to work.  In addition the "HTML-Format" distribution needs to be installed for "-o text" or "-o ps" to work.
-v  Print the version number of the program and quit.
-h  Print usage message and quit.
-a  Set text(ascii) mode for content input and output.  If this option is not used, content input and output is done in binary mode.
Because this program is implemented using the LWP library, it will only support the protocols that LWP supports.
lwp-mirror, LWP
Copyright 1995-1999 Gisle Aas.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Gisle Aas <gisle@aas.no>
http_load(1)                 General Commands Manual                http_load(1)
http_load - multiprocessing http test client
http_load [-checksum] [-throttle] [-proxy host:port] [-verbose] [-timeout secs] [-sip sip_file] [-cipher str] ( -parallel N | -rate N [-jitter] ) ( -fetches N | -seconds N ) url_file
http_load runs multiple http fetches in parallel, to test the throughput of a web server.  However unlike most such test clients, it runs in a single process, so it doesn't bog down the client machine.  It can be configured to do https fetches as well.
The -checksum flag tells http_load to do checksums on the files fetched, to make sure they came across ok.  The checksums are computed the first time each URL gets fetched, and then recomputed and compared on each subsequent fetch.  Without the -checksum flag only the byte count is checked.
The -throttle flag tells http_load to throttle its consumption of data to 33.6Kbps, to simulate access by modem users.
The -proxy flag lets you run http_load through a web proxy.
The -verbose flag tells http_load to put out progress reports every minute on stderr.
The -timeout flag specifies how long to wait on idle connections before giving up.  The default is 60 seconds.
The -sip flag lets you specify a file containing numeric IP addresses (not hostnames), one per line.  These get used randomly as the *source* address of connections.  They must be real routable addresses on your machine, created with ifconfig, in order for this to work.  The advantage of using this option is you can make one client machine look like a whole bank of machines, as far as the server knows.
The -cipher flag is only available if you have SSL support compiled in. It specifies a cipher set to use.  By default, http_load will negotiate the highest security that the server has available, which is often higher (and slower) than typical browsers will negotiate.  An example of a cipher set might be "RC4-MD5" - this will run considerably faster than the default.  In addition to specifying a raw cipher string, there are three built-in cipher sets accessible by keywords: * fastsec - fast security - RC4-MD5 * highsec - high security - DES-CBC3-SHA * paranoid - ultra high security - AES256-SHA Of course, not all servers are guaranteed to implement these combinations.
One start specifier, either -parallel or -rate, is required.  -parallel tells http_load to keep that many parallel fetches going simultaneously. -rate tells http_load to start that many new connections each second.  If you use the -rate start specifier, you can also give the -jitter flag, telling http_load to vary the rate randomly by about 10%.
One end specifier, either -fetches or -seconds, is required.  -fetches tells http_load to quit when that many fetches have been completed. -seconds tells http_load to quit after that many seconds have elapsed.
The url_file is just a list of URLs, one per line.  The URLs that get fetched are chosen randomly from this file.
All flags may be abbreviated to a single letter.
Note that while the end specifier is obeyed precisely, the start specifier is only approximate.  If you use the -rate flag, http_load will make its best effort to start connections at that rate, but may not succeed.  And if you use the -parallel flag, http_load will attempt to keep that many simultaneous connections going, but may fail to keep up if the server is very fast.
Sample run: % http_load -rate 2 -seconds 300 urls 591 fetches, 8 max parallel, 5.33606e+06 bytes, in 300 seconds 9028.87 mean bytes/connection 1.97 fetches/sec, 17786.9 bytes/sec msecs/connect: 28.8932 mean, 44.243 max, 24.488 min msecs/first-response: 63.5362 mean, 81.624 max, 57.803 min HTTP response codes: code 200 -- 591
http_ping(1)
Copyright Â© 1998,1999,2001 by Jef Poskanzer <jef@mail.acme.com>.  All rights reserved.
DOCKER(1)                      Docker User Manuals                     DOCKER(1)
docker-stats - Display a live stream of container(s) resource usage statistics
docker stats [OPTIONS] [CONTAINER...]
Alias for docker container stats.
-a, --all[=false]      Show all containers (default shows just running)
--format=""      Pretty-print images using a Go template
-h, --help[=false]      help for stats
--no-stream[=false]      Disable streaming stats and only pull the first result
--no-trunc[=false]      Do not truncate output
docker(1)
FALSE(1)                          User Commands                         FALSE(1)
false - do nothing, unsuccessfully
false [ignored command line arguments] false OPTION
Exit with a status code indicating failure.
NOTE: your shell may have its own version of false, which usually supersedes the version described here.  Please refer to your shell's documentation for details about the options it supports.
Written by Jim Meyering.
Full documentation <https://www.gnu.org/software/coreutils/false> or available locally via: info '(coreutils) false invocation'
SoX(1)                           Sound eXchange                           SoX(1)
SoX - Sound eXchange, the Swiss Army knife of audio manipulation
sox [global-options] [format-options] infile1 [[format-options] infile2] ... [format-options] outfile [effect [effect-options]] ...
play [global-options] [format-options] infile1 [[format-options] infile2] ... [format-options] [effect [effect-options]] ...
rec [global-options] [format-options] outfile [effect [effect-options]] ...
Introduction SoX reads and writes audio files in most popular formats and can optionally apply effects to them. It can combine multiple input sources, synthesise audio, and, on many systems, act as a general purpose audio player or a multi-track audio recorder. It also has limited ability to split the input into multiple output files.
All SoX functionality is available using just the sox command.  To simplify playing and recording audio, if SoX is invoked as play, the output file is automatically set to be the default sound device, and if invoked as rec, the default sound device is used as an input source. Additionally, the soxi(1) command provides a convenient way to just query audio file header information.
The heart of SoX is a library called libSoX.  Those interested in extending SoX or using it in other programs should refer to the libSoX manual page: libsox(3).
SoX is a command-line audio processing tool, particularly suited to making quick, simple edits and to batch processing.  If you need an interactive, graphical audio editor, use audacity(1).
*        *        *
The overall SoX processing chain can be summarised as follows:
Input(s) → Combiner → Effects → Output(s)
Note however, that on the SoX command line, the positions of the Output(s) and the Effects are swapped w.r.t. the logical flow just shown. Note also that whilst options pertaining to files are placed before their respective file name, the opposite is true for effects.  To show how this works in practice, here is a selection of examples of how SoX might be used.  The simple sox recital.au recital.wav translates an audio file in Sun AU format to a Microsoft WAV file, whilst sox recital.au -b 16 recital.wav channels 1 rate 16k fade 3 norm performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16. sox -r 16k -e signed -b 8 -c 1 voice-memo.raw voice-memo.wav converts `raw' (a.k.a. `headerless') audio to a self-describing file format, sox slow.aiff fixed.aiff speed 1.027 adjusts audio speed, sox short.wav long.wav longer.wav concatenates two audio files, and sox -m music.mp3 voice.wav mixed.flac mixes together two audio files. play "The Moonbeams/Greatest/*.ogg" bass +3 plays a collection of audio files whilst applying a bass boosting effect, play -n -c1 synth sin %-12 sin %-9 sin %-5 sin %-2 fade h 0.1 1 0.1 plays a synthesised `A minor seventh' chord with a pipe-organ sound, rec -c 2 radio.aiff trim 0 30:00 records half an hour of stereo audio, and play -q take1.aiff & rec -M take1.aiff take1-dub.aiff (with POSIX shell and where supported by hardware) records a new track in a multi-track recording.  Finally, rec -r 44100 -b 16 -e signed-integer -p \ silence 1 0.50 0.1% 1 10:00 0.1% | \ sox -p song.ogg silence 1 0.50 0.1% 1 2.0 0.1% : \ newfile : restart records a stream of audio such as LP/cassette and splits in to multiple audio files at points with 2 seconds of silence.  Also, it does not start recording until it detects audio is playing and stops after it sees 10 minutes of silence.
N.B.  The above is just an overview of SoX's capabilities; detailed explanations of how to use all SoX parameters, file formats, and effects can be found below in this manual, in soxformat(7), and in soxi(1).
File Format Types SoX can work with `self-describing' and `raw' audio files.  `self- describing' formats (e.g. WAV, FLAC, MP3) have a header that completely describes the signal and encoding attributes of the audio data that follows. `raw' or `headerless' formats do not contain this information, so the audio characteristics of these must be described on the SoX command line or inferred from those of the input file.
The following four characteristics are used to describe the format of audio data such that it can be processed with SoX:
sample rate The sample rate in samples per second (`Hertz' or `Hz').  Digital telephony traditionally uses a sample rate of 8000 Hz (8 kHz), though these days, 16 and even 32 kHz are becoming more common. Audio Compact Discs use 44100 Hz (44.1 kHz). Digital Audio Tape and many computer systems use 48 kHz. Professional audio systems often use 96 kHz.
sample size The number of bits used to store each sample.  Today, 16-bit is commonly used. 8-bit was popular in the early days of computer audio. 24-bit is used in the professional audio arena. Other sizes are also used.
data encoding The way in which each audio sample is represented (or `encoded'). Some encodings have variants with different byte-orderings or bit- orderings.  Some compress the audio data so that the stored audio data takes up less space (i.e. disk space or transmission bandwidth) than the other format parameters and the number of samples would imply.  Commonly-used encoding types include floating-point, μ-law, ADPCM, signed-integer PCM, MP3, and FLAC.
channels The number of audio channels contained in the file.  One (`mono') and two (`stereo') are widely used.  `Surround sound' audio typically contains six or more channels.
The term `bit-rate' is a measure of the amount of storage occupied by an encoded audio signal over a unit of time.  It can depend on all of the above and is typically denoted as a number of kilo-bits per second (kbps).  An A-law telephony signal has a bit-rate of 64 kbps. MP3-encoded stereo music typically has a bit-rate of 128-196 kbps. FLAC-encoded stereo music typically has a bit-rate of 550-760 kbps.
Most self-describing formats also allow textual `comments' to be embedded in the file that can be used to describe the audio in some way, e.g. for music, the title, the author, etc.
One important use of audio file comments is to convey `Replay Gain' information.  SoX supports applying Replay Gain information (for certain input file formats only; currently, at least FLAC and Ogg Vorbis), but not generating it.  Note that by default, SoX copies input file comments to output files that support comments, so output files may contain Replay Gain information if some was present in the input file.  In this case, if anything other than a simple format conversion was performed then the output file Replay Gain information is likely to be incorrect and so should be recalculated using a tool that supports this (not SoX).
The soxi(1) command can be used to display information from audio file headers.
Determining & Setting The File Format There are several mechanisms available for SoX to use to determine or set the format characteristics of an audio file.  Depending on the circumstances, individual characteristics may be determined or set using different mechanisms.
To determine the format of an input file, SoX will use, in order of precedence and as given or available:
1.  Command-line format options.
2.  The contents of the file header.
3.  The filename extension.
To set the output file format, SoX will use, in order of precedence and as given or available:
2.  The filename extension.
3.  The input file format characteristics, or the closest that is supported by the output file type.
For all files, SoX will exit with an error if the file type cannot be determined. Command-line format options may need to be added or changed to resolve the problem.
Playing & Recording Audio The play and rec commands are provided so that basic playing and recording is as simple as play existing-file.wav and rec new-file.wav These two commands are functionally equivalent to sox existing-file.wav -d and sox -d new-file.wav Of course, further options and effects (as described below) can be added to the commands in either form.