Put command unix example

A certificate is a digitally signed statement from one entity person, company, and so forthsaying that the public key and some other information of some other entity has a particular value.

When data is digitally signed, the signature can be verified to check the data integrity and authenticity. Integrity means that the data has not been modified or tampered with, and authenticity means the data indeed comes from whoever claims to have created and signed it. The keytool default keystore implementation implements the keystore as a file. It protects private keys with a password.

The jarsigner 1 tool uses information from a keystore to generate or verify digital signatures for Java ARchive JAR files. These new tools provide more features than javakey, including the ability to protect the keystore and private keys with passwords, and the ability to verify signatures in addition to generating them.

The new keystore architecture replaces the identity database that javakey created and managed. It is possible to import the information from an identity database into a keystore, via the -identitydb subcommand.

Keystore Entries There are two different types of entries in a keystore: Typically, a key stored in this type of entry is a secret key, or a private key accompanied by the certificate "chain" for the corresponding public key.

The keytool and jarsigner 1 tools only handle the latter type of entry, that is, private keys and their associated certificate chains. It is called a "trusted certificate" because the keystore owner trusts that the public key in the certificate indeed belongs to the identity identified by the "subject" owner of the certificate.

The issuer of the certificate vouches for this, by signing the certificate. Keystore Aliases All keystore entries key and trusted certificate entries are accessed via unique aliases.

Aliases are case-insensitive; the aliases Hugo and hugo would refer to the same keystore entry. An alias is specified when you add an entity to the keystore using the -genkey subcommand to generate a key pair public and private key or the -import subcommand to add a certificate or certificate chain to the list of trusted certificates.

Subsequent keytool commands must use this same alias to refer to the entity. A password should not actually be specified on a command line or in a script unless it is for testing purposes, or you are on a secure system. When typing in a password at the password prompt, the password is currently echoed displayed exactly as typedso be careful not to type it in front of anyone.

10 example of using Vim or VI editor in UNIX and Linux

Keystore Location Each keytool command has a -keystore option for specifying the name and location of the persistent keystore file for the keystore managed by keytool. The keystore is by default stored in a file named. Note that the input stream from the -keystore option is passed to the KeyStore. If NONE is specified as the URL, then a null stream is passed to the KeyStore. NONE should be specified if the KeyStore is not file-based, for example, if it resides on a hardware token device.

If that file does not yet exist, it will be created. Keystore Implementation The KeyStore class provided in the java. It is possible for there to be multiple different concrete implementations, where each implementation is that for a particular type of keystore.

Currently, there are two command-line tools keytool and jarsigner 1 and also a GUI-based tool named policytool. Since KeyStore is publicly available, JDK users can write additional security applications that use it.

A collection of Unix/Linux ‘find’ command examples | utabumo.web.fc2.com

There is a built-in default implementation, provided by Sun Microsystems. It implements the keystore as a file, utilizing a proprietary keystore type format named "JKS". It protects each private key with its individual password, and also protects the integrity of the entire keystore with a possibly different password.

Basic UNIX commands

Keystore implementations are provider-based. More specifically, the application interfaces supplied by KeyStore are implemented in terms of a "Service Provider Interface" SPI.

That is, there is a corresponding abstract KeystoreSpi class, also in the java. The term "provider" refers to a package or a set of packages that supply a concrete implementation of a subset of services that can be accessed by the Java Security API. Thus, to provide a keystore implementation, clients must implement a "provider" and supply a KeystoreSpi subclass implementation, as described in How to Implement a Provider for the Java Cryptography Architecture.

Applications can choose different types of keystore implementations from different providers, using the "getInstance" factory method supplied in the KeyStore class. A keystore type defines the storage and data format of the keystore information, and the algorithms used to protect private keys in the keystore and the integrity of the keystore itself.

Keystore implementations of different types are not compatible. It treats the keytore location that is passed to it at the command line as a filename and converts it to a FileInputStream, from which it loads the keystore information. The jarsigner 1 and policytool tools, on the other hand, can read a keystore from any location that can be specified using a URL.

For keytool and jarsigner 1you can specify a keystore type at the command line, via the -storetype option. For Policy Toolyou can specify a keystore type via the "Change Keystore" command in the Edit menu.

The security properties file is called java. Each tool gets the keystore. It then uses the keystore implementation from that provider.

The KeyStore class defines a static method named getDefaultType that lets applications and applets retrieve the value of the keystore.

The following line of code creates an instance of the default keystore type as specified in the keystore.

This is specified by the following line in the security properties file: For example, if you have a provider package that supplies a keystore implementation for a keystore type called "pkcs12", change the line to keystore. For example, "JKS" would be considered the same as "jks". Supported Algorithms and Key Sizes keytool allows users to specify any key pair generation and signature algorithm supplied by any of the registered cryptographic service providers.

That is, the -keyalg and -sigalg options for various subcommands must be supported by a provider implementation. The default key pair generation algorithm is "DSA".

The signature algorithm is derived from the algorithm of the underlying private key: If the underlying private key is of type "DSA", the default signature algorithm is "SHA1withDSA", and if the underlying private key is of type "RSA", the default signature algorithm is "MD5withRSA".

When generating a DSA key pair, the key size must be in the range from to bits, and must be a multiple of The default key size for any algorithm is bits. Certificates A certificate also known as a public-key certificate is a digitally signed statement from one entity the issuersaying that the public key and some other information of another entity the subject has some Let us expand on some of the key terms used in this sentence: Tag Description Public Keys These are numbers associated with a particular entity, and are intended to be known to everyone who needs to have trusted interactions with that entity.

Public keys are used to verify signatures. Digitally Signed If some data is digitally signed it has been stored with the "identity" of an entity, and a signature that proves that entity knows about the data. Identity A known way of addressing an entity. In some systems the identity is the public key, in others it can be anything from a Unix UID to an Email address to an X. Signature A signature is computed over some data using the private key of an entity the signer, which in the case of a certificate is also known as the issuer.

Private and public keys exist in pairs in all public key cryptography systems also referred to as "public key crypto systems". In a typical public key crypto system, such as DSA, a private key corresponds to exactly one public key. Private keys are used to compute signatures.

Entity An entity is a person, organization, program, computer, business, bank, or something else you are trusting to some degree.

In a large-scale networked environment it is impossible to guarantee that prior relationships between communicating entities have been established or that a trusted repository exists with all used public keys. Certificates were invented as a solution to this public key distribution problem.

Now a Certification Authority CA can act as a trusted third party. CAs are entities for example, businesses that are trusted to sign issue certificates for other entities. It is assumed that CAs will only create valid and reliable certificates, as they are bound by legal agreements. There are many public Certification Authorities, such as VeriSign, Thawte, Entrust, and so on.

Using keytoolit is possible to display, import, and export certificates. It is also possible to generate self-signed certificates. Tag Description Version This identifies which version of the X.

Thus far, three versions are defined. It generates v1 certificates. Serial Number The entity that created the certificate is responsible for assigning it a serial number to distinguish it from other certificates it issues.

This information is used in numerous ways, for example when a certificate is revoked its serial number is placed in a Certificate Revocation List CRL. Signature Algorithm Identifier This identifies the algorithm used by the CA to sign the certificate.

Issuer Name The X. This is normally a CA. Using this certificate implies trusting the entity that signed this certificate. Note that in some cases, such as root or top-level CA certificates, the issuer signs its own certificate. Validity Period Each certificate is valid only for a limited amount of time.

This period is described by a start date and time and an end date and time, and can be as short as a few seconds or almost as long as a century. The validity period chosen depends on a number of factors, such as the strength of the private key used to sign the certificate or the amount one is willing to pay for a certificate. This is the expected period that entities can rely on the public value, if the associated private key has not been compromised.

Subject Name The name of the entity whose public key the certificate identifies. This name uses the X. This is the X. Tag Description Subject Public Key Information This is the public key of the entity being named, together with an algorithm identifier which specifies which public key crypto system this key belongs to and any associated key parameters.

Most certificate profile documents strongly recommend that names not be reused, and that certificates should not make use of unique identifiers. Version 2 certificates are not widely used. Some common extensions in use today are: KeyUsage limits the use of the keys to particular purposes such as "signing-only" and AlternativeNames allows other identities to also be associated with this public key, for example, DNS names, Email addresses, IP addresses.

For example, if a certificate has the KeyUsage extension marked critical and set to "keyCertSign" then if this certificate is presented during SSL communication, it should be rejected, as the certificate extension indicates that the associated private key should only be used for signing certificates and not for SSL use. All the data in a certificate is encoded using two related standards called ASN.

Abstract Syntax Notation 1 describes data. The Definite Encoding Rules describe a single way to store and transfer that data. For example, CNcnand Cn are all treated the same. Order matters; each subcomponent must appear in the designated order. However, it is not necessary to have all the subcomponents. You may use a subset, for example: If it is needed for a command, but not supplied on the command line, the user is prompted for each of the subcomponents. This certificate format, also known as "Base 64 encoding", facilitates exporting certificates to other applications by email or through some other mechanism.

Certificates read by the -import and -printcert subcommands can be in either this format or binary encoded. The -export subcommand by default outputs a certificate in binary encoding, but will instead output a certificate in the printable encoding format, iko forex review the -rfc option is specified. The -list subcommand by default prints the MD5 fingerprint of a certificate.

If the -v option is specified, the certificate is printed in human-readable format, while if the -rfc option is specified, the certificate is output in the printable encoding format. The first certificate in the chain contains the public key corresponding to the private key.

When keys are first generated see the -genkey subcommandthe chain starts off containing a single element, a self-signed certificate. A self-signed certificate is one for which the issuer signer is the same as the subject the entity whose public key is being authenticated by the certificate. Later, after a Certificate Signing Request CSR has been generated see the -certreq subcommand and sent to a Certification Authority CAthe response from the CA is imported see -importand the self-signed certificate is replaced by a chain of certificates.

In many cases, this is a self-signed certificate that is, a certificate from the CA authenticating shorting call options own public key and the last certificate in the chain. In other cases, the CA may return a chain of certificates.

In this case, the bottom certificate in the chain is the same a certificate signed by the CA, authenticating the public key of the key entrybut the second certificate in the chain is a certificate signed by a different CA, authenticating the public key of the CA you sent the CSR to.

Each certificate in the chain after the first thus authenticates the public key of the signer of the previous certificate in the chain. Many CAs only return the issued certificate, with no supporting chain, trading ranking forex course when there is a flat hierarchy no intermediates CAs.

In this case, the certificate chain must be established from trusted certificate information already stored in the keystore. A different reply bible code market crash 2016 stockholm defined by the PKCS 7 standard also includes the supporting certificate chain, in addition to the issued certificate. Both reply formats can be vecm stock market exchange rate oil price by keytool.

tr command examples in Unix

The top-level root CA certificate is self-signed. The root CA public key is widely known. Importing Certificates To import a certificate from a file, use the -import subcommand, as in keytool -import -alias put command unix example -file jcertfile. You import a certificate for two reasons: Which type of import is intended is indicated by the value of the -alias option. In this case, the alias should not already exist in the keystore. If the alias does already exist, then keytool outputs an error, since there is already a trusted certificate for that alias, and does not import the certificate.

If the alias does not exist in the keystore, keytool creates a trusted certificate entry with the specified alias and associates it with the imported certificate. WARNING Regarding Importing Trusted Certificates IMPORTANT: Be sure to check a certificate very carefully before importing it as a trusted certificate! View it first using the -printcert subcommand, or the -import subcommand without the -noprompt optionand make sure that the displayed certificate fingerprint s match the expected ones.

Thu Sep 25 Wed Dec 24 FE Then call or otherwise contact the person who sent the certificate, and compare the fingerprint s that you see with the ones that they walt disney world ticker symbol. If such an attack took place, and you did not check the certificate before you imported it, you would end up trusting anything the attacker has signed for example, a JAR file with malicious class files inside.

You then have the option of aborting the import operation. Note, however, this is only the case if you invoke the -import subcommand without the -noprompt option. If the -noprompt option is given, there is no interaction with the user. Exporting Certificates To export a certificate to a file, use best forex uk broker -export subcommand, as in keytool -export -alias jane -file janecertfile.

That is, if jane is the alias for a key entry, the command exports the certificate at the bottom of the certificate chain in that keystore entry. If, instead, jane is the alias for a trusted certificate entry, tdu2 easy way to make money that trusted certificate is exported. To display the contents of a certificate stored in a file, use the -printcert subcommand, as get index selected item dropdown jquery keytool -printcert -file certfile.

Generating a Self-signed Certificate A self-signed certificate is one for which the issuer signer is the same as the subject the entity whose public key is being authenticated by the certificate.

You may occasionally wish to generate a new self-signed certificate. For example, you may want to use the same key pair under a different identity distinguished name.

For example, suppose you change departments. See the -certreq and -import subcommand. COMMAND AND OPTION NOTES The various subcommands and their options are listed and described below.

Tag Description o All subcommand and option names are preceded by a minus sign. For a -keypass option, if you do not specify the option on the command line, keytool will first attempt to use the keystore password to recover the private key, and if this fails, will then prompt you for the private key password.

For example, here is the format of the -printcert subcommand: Thus, the command forex m2 preis keytool is equivalent to keytool -help Option Defaults Below are the defaults for various option values.

If the underlying private key is of type "DSA", the -sigalg private key is of type "RSA", -sigalg defaults to "MD5withRSA". Options that Appear for Most Subcommands The -v option can appear for all subcommands except -help. If it appears, it signifies "verbose" mode; detailed certificate information will be output.

There is also a -J javaoption option that may appear for any subcommand. If it appears, the specified -javaoption string is passed through directly to the Java interpreter. This option should not contain any spaces.

It is useful for adjusting the execution environment or memory usage. For a list of possible interpreter options, type java -h or java -X at the command line. These options may appear for all commands operating on a keystore: The default keystore type is the one that is specified as the value of the "keystore.

Defaults to the file. It must be provided to all subcommands that access the keystore contents. For such subcommands, if a -storepass option is not provided at the command line, the user is prompted for it.

When retrieving information from the keystore, the password is optional; if no password is given, the integrity of the retrieved information cannot be checked and a warning is displayed.

Be careful with passwords - see Warning Regarding Passwords.

Warning Regarding Passwords Most commands operating on a keystore require the store password. Some commands require a private key password. Passwords can be specified on the command line in the -storepass and -keypass options, respectively. However, a password should not be specified on a command line or in a script unless it is for testing purposes, or you are on a secure system. COMMANDS See also COMMAND AND OPTION NOTES. Wraps profitable stock market patterns public key into an X.

This certificate chain and the private key futures and options trading video tutorial stored in a new keystore entry identified by alias.

See Supported Algorithms and Key Sizes. If no distinguished name is provided at the command line, the user will be prompted for one. If no password is provided, the user is prompted for it. If you press RETURN at the prompt, the key password is set to the same password as that used for the keystore. Be careful with passwords: See Warning Regarding Passwords. If no file is given, the certificate or PKCS 7 reply is read from stdin.

The data to tri county livestock auction osborn mo imported must be provided either in binary encoding format, or in printable encoding format also known as Base64 encoding as defined by the Internet RFC standard.

In 60 second binary options review in excel latter case, the encoding must be bounded at the beginning by a string that starts with "BEGIN", and bounded at the end by a string that starts with "END". You import a certification for two reasons: Importing a New Trusted Certificate When importing a new trusted certificate, alias must not yet exist in the keystore. Before adding the certificate to the keystore, keytool tries to verify it by attempting to construct a chain of trust from that certificate to a self-signed certificate belonging to a root CAusing trusted certificates that are already available in the keystore.

If the -trustcacerts option has been specified, additional certificates are considered for the chain of trust, namely the certificates in a file named cacerts. If keytool forex cft-626b mp3 fm transmitter to establish a trust path from the certificate to be imported up to a self-signed certificate either from the keystore or the "cacerts" filethe certificate information is printed out, and the user is prompted to verify it, e.

Be very careful to ensure the certificate is valid prior to importing it as a "trusted" certificate! The user then has the option of aborting the import operation. If the -noprompt option is given, however, there will be no interaction with the user.

Importing a Certificate Reply When importing a certificate reply, the certificate reply is validated using trusted certificates from the keystore, and optionally using the certificates configured in the cacerts keystore file if the -trustcacerts option was specified.

The methods of determining whether the certificate reply is trusted are described in the following: If the reply is a single X. The certificate reply and the hierarchy of certificates used to authenticate the certificate reply form the new certificate chain of alias.

If the reply is a Discount stock brokerages 7 formatted certificate chain, the chain is first ordered with the user certificate first and the self-signed root CA certificate lastbefore keytool attempts to match the root CA certificate provided in the reply with any of the trusted certificates in the keystore or the cacerts keystore file if the -trustcacerts option was specified.

If no match can be found, the information of the root CA certificate how to get quick money in aqw printed out, and the user is prompted to verify it, for example, by comparing the displayed certificate fingerprints with the fingerprints obtained from some other trusted source of information, which might be the root CA itself.

The new certificate chain of alias replaces the old certificate chain associated with this entry. The old chain can only be replaced if a valid keypass, the password used to protect the private key of the entry, is supplied.

If no password is provided, and the private key password is different from the keystore password, the user is prompted for it. The cacerts Certificates File A certificates file named "cacerts" resides in the security properties directory, java. The "cacerts" file represents a system-wide keystore with CA certificates.

System administrators can configure and manage that file using keytool, specifying "jks" as the keystore type. The "cacerts" keystore file ships with several root CA certificates with the following aliases and X.

System administrators should change that password and the default access permission of that file upon installing the SDK. Verify Your cacerts File Since you trust the CAs in the cacerts file as entities for signing and issuing certificates to other entities, you must manage the cacerts file carefully.

The cacerts file should contain only certificates of the Cp cheats money maker new downloads you trust. It is your responsibility to verify the trusted root CA certificates bundled in the cacerts file and make your own trust decisions. To remove an untrusted CA certificate from the cacerts file, use the delete option of the keytool command. You can find the You can find the cacerts file in the JRE installation directory.

Contact your system administrator if you do not have permission to edit this file. If dname is supplied at the command line, it is used as the X. The generated certificate is stored as a single-element certificate chain in the keystore entry identified by aliaswhere it replaces the existing certificate chain.

In order to access the private key, the appropriate password must be provided, since private keys are protected in the keystore with a password. If keypass is not provided at the command line, and is different from the password used to protect the integrity of the keystore, the user is prompted for it. If no file is given, the identity database is read from stdin. If a keystore does not exist, it is created. Only identity database entries "identities" that were marked as trusted will be imported in the keystore.

All other identities will be ignored. For each trusted identity, a keystore entry will be created. The private keys from trusted identities will all be encrypted under the same password, storepass.

Users can later assign individual passwords to those private keys by using the -keypasswd keytool command option. An identity in an identity database may hold more than one certificate, each certifying the same public key. But a keystore key entry for a private key has that private key and a single "certificate chain" initially just a single certificatewhere the first certificate in the chain contains the public key corresponding to the private key.

When importing the information from an identity, only the first certificate of the identity is stored in the keystore. A CSR is intended to be sent to a certificate authority CA. The CA will authenticate the certificate requestor usually off-line and will return a certificate or certificate chain, used to replace the existing certificate chain which initially consists of a self-signed certificate in the keystore. The private key and X. If no file is given, the CSR is output to stdout.

Use the import command to import the response from the CA. If no file is given, the certificate is output to stdout. The certificate is by default output in binary encoding, but will instead be output in the printable encoding format, as defined by the Internet RFC standard, if the -rfc option is specified. If alias refers to a trusted certificate, that certificate is output.

Otherwise, alias refers to a key entry with an associated certificate chain. In that case, the first certificate in the chain is returned. This certificate authenticates the public key of the entity addressed by alias. If no alias is specified, the contents of the entire keystore are printed. This command by default prints the MD5 fingerprint of a certificate. If the -v option is specified, the certificate is printed in human-readable format, with additional information such as the owner, issuer, and serial number.

If the -rfc option is specified, certificate contents are printed using the printable encoding format, as defined by the Internet RFC standard You cannot specify both -v and -rfc. If no file is given, the certificate is read from stdin. The certificate may be either binary encoded or in printable encoding format, as defined by the Internet RFC standard. This option can be used independently of a keystore. The original entry is identified by alias which defaults to "mykey" if not provided.

If no destination alias is supplied at the command line, the user is prompted for it. If the private key password is different from the keystore password, then the entry will only be cloned if a valid keypass is supplied. This is the password used to protect the private key associated with alias. If no key password is supplied at the command line, and the private key password is different from the keystore password, the user is prompted for it. The private key in the cloned entry may be protected with a different password, if desired.

This command can be used to establish multiple certificate chains corresponding to a given key pair, or for backup purposes. If the -keypass option is not provided at the command line, and the private key password is different from the keystore password, the user is prompted for it.

If the -new option is not provided at the command line, the user is prompted for it. The user is prompted for the aliasif no alias is provided at the command line. Getting Help Tag Description -help Lists all the command and their options. Generating Your Key Pair The first thing you need to do is create a keystore and generate the key pair.

You could use a command such as the following: This must be typed as a single line. Multiple lines are used in the examples just for legibility purposes. This command creates the keystore named mykeystore in the working directory assuming it does not already existand assigns it the password abc.

It uses the default "DSA" key generation algorithm to create the keys, both bits long. It creates a self-signed certificate using the default "SHA1withDSA" signature algorithm that includes the public key and the distinguished name information.

This certificate will be valid for days, and is associated with the private key in a keystore entry referred to by the alias business. The private key is assigned the password kpi The command could be significantly shorter if option defaults were accepted.

As a matter of fact, no options are required; defaults are used for unspecified options that have default values, and you are prompted for any required values. Thus, you could simply have the following: This entry is placed in the keystore named.

You will be prompted for the distinguished name information, the keystore password, and the private key password. The rest of the examples assume you executed the -genkey command without options specified, and that you responded to the prompts with values equal to those given in the first -genkey command, above a private key password of kpiand so forth. A certificate is more likely to be trusted by others if it is signed by a Certification Authority CA.

To get such a signature, you first generate a Certificate Signing Request CSRvia the following: Submit this file to a CA, such as VeriSign, Inc. The CA will authenticate you, the requestor usually off-lineand then will return a certificate, signed by them, authenticating your public key. In some cases, they will actually return a chain of certificates, each one authenticating the public key of the signer of the previous certificate in the chain.

Importing a Certificate for the CA You need to replace your self-signed certificate with a certificate chain, where each certificate in the chain authenticates the public key of the signer of the previous certificate in the chain, up to a "root" CA.

Before you import the certificate reply from a CA, you need one or more "trusted certificates" in your keystore or in the cacerts keystore file which is described in import command: Suppose company ABC, Inc. You can call the person who sent the certificate, and compare the fingerprint s that you see with the ones that they show or that a secure public key repository shows. If such an attack took place, and you did not check the certificate before you imported it, you would end up trusting anything the attacker has signed.

If you trust that the certificate is valid, then you can add it to your keystore via the following: This chain is the one returned by the CA in response to your request if the CA reply is a chainor one constructed if the CA reply is a single certificate using the certificate reply and trusted certificates that are already available in the keystore where you import the reply or in the cacerts keystore file.

For example, suppose you sent your certificate signing request to VeriSign. You can then import the reply via the following, which assumes the returned certificate is named VSMarkJ. Clients that want to use the file will want to authenticate your signature. One way they can do this is by first importing your public key certificate into their keystore as a "trusted" entry.

You can export the certificate and supply it to your clients. As an example, you can copy your certificate to a file named MJ. Changing Your Distinguished Name but Keeping your Key Pair Suppose your distinguished name changes, for example because you have changed departments or moved to a different city.

First, copy clone your key entry: Now you need to change the certificate chain associated with the copy, so that the first certificate in the chain uses your different distinguished name. Start by generating a self-signed certificate with the appropriate name: Unix - What is Shell? Unix - Using Variables Unix - Special Variables Unix - Using Arrays Unix - Basic Operators Unix - Decision Making Unix - Shell Loops Unix - Loop Control Unix - Shell Substitutions Unix - Quoting Mechanisms Unix - IO Redirections Unix - Shell Functions Unix - Manpage Help.

Unix - Regular Expressions Unix - File System Basics Unix - User Administration Unix - System Performance Unix - System Logging Unix - Signals and Traps. Unix - Useful Commands Unix - Quick Guide Unix - Builtin Functions Unix - System Calls Unix - Commands List. Computer Glossary Who is Who. It also allows users to cache the public keys in the form of certificates of their communicating peers.

These are numbers associated with a particular entity, and are intended to be known to everyone who needs to have trusted interactions with that entity. If some data is digitally signed it has been stored with the "identity" of an entity, and a signature that proves that entity knows about the data. A known way of addressing an entity.

A signature is computed over some data using the private key of an entity the signer, which in the case of a certificate is also known as the issuer.

An entity is a person, organization, program, computer, business, bank, or something else you are trusting to some degree. This identifies which version of the X. The entity that created the certificate is responsible for assigning it a serial number to distinguish it from other certificates it issues.

Each certificate is valid only for a limited amount of time. The name of the entity whose public key the certificate identifies.

This is the public key of the entity being named, together with an algorithm identifier which specifies which public key crypto system this key belongs to and any associated key parameters. The options for each subcommand may be provided in any order. All items not italicized or in braces or square brackets are required to appear as is. Braces surrounding an option generally signify that a default value will be used if the option is not specified on the command line.

Brackets surrounding an option signify that the user is prompted for the value s if the option is not specified on the command line. Items in italics option values represent the actual values that must be supplied. For example, here is the format of the -printcert subcommand:. Option values must be quoted if they contain a blank space. This qualifier specifies the type of keystore to be instantiated. The keystore database file location. If the certificate reply is a single certificate, you need a certificate for the issuing CA the one that signed itand if that certificate is not self-signed, you need a certificate for its signer, and so on, up to a self-signed "root" CA certificate.