NAME
gjarsigner - Java ARchive (JAR) file signing and verification tool
SYNOPSIS
jarsigner [OPTION]... FILE ALIAS jarsigner -verify [OPTION]... FILE
DESCRIPTION
When the first form is used, the tool signs the designated JAR file. The second form, on the other hand, is used to verify a previously signed JAR file. FILE is the .JAR file to process; i.e., to sign if the first syntax form is used, or to verify if the second syntax form is used instead. ALIAS must be a known Alias of a Key Entry in the designated Key Store. The private key material associated with this Alias is then used for signing the designated .JAR file.
OPTIONS
Common options The following options may be used when the tool is used for either signing, or verifying, a .JAR file. -verbose Use this option to force the tool to generate more verbose messages, during its processing. -internalsf When present, the tool will include --which otherwise it does not-- the ".SF" file in the ".DSA" generated file. -sectionsonly When present, the tool will include in the ".SF" generated file --which otherwise it does not-- a header containing a hash of the whole manifest file. When that header is included, the tool can quickly check, during verification, if the hash (in the header) matches or not the manifest file. -provider PROVIDER_CLASS_NAME A fully qualified class name of a Security Provider to add to the current list of Security Providers already installed in the JVM in- use. If a provider class is specified with this option, and was successfully added to the runtime --i.e. it was not already installed-- then the tool will attempt to remove this Security Provider before exiting. -help Prints a help text similar to this one. Signing options The following options may be specified when using the tool for signing purposes. -keystore URL Use this option to specify the location of the key store to use. The default value is a file URL referencing the file named .keystore located in the path returned by the call to "java.lang.System#getProperty(String)" using "user.home" as argument. If a URL was specified, but was found to be malformed --e.g. missing protocol element-- the tool will attempt to use the URL value as a file-name (with absolute or relative path-name) of a key store --as if the protocol was "file:". -storetype STORE_TYPE Use this option to specify the type of the key store to use. The default value, if this option is omitted, is that of the property "keystore.type" in the security properties file, which is obtained by invoking the static method call "getDefaultType()" in "java.security.KeyStore". -storepass PASSWORD Use this option to specify the password which will be used to unlock the key store. If this option is missing, the User will be prompted to provide a password. -keypass PASSWORD Use this option to specify the password which the tool will use to unlock the Key Entry associated with the designated Alias. If this option is omitted, the tool will first attempt to unlock the Key Entry using the same password protecting the key store. If this fails, you will then be prompted to provide a password. -sigfile NAME Use this option to designate a literal that will be used to construct file names for both the ".SF" and ".DSA" signature files. These files will be generated, by the tool, and placed in the META-INF directory of the signed JAR. Permissible characters for NAME must be in the range "a-zA-Z0-9_-". All characters will be converted to upper-case ones. If this option is missing, the first eight characters of the ALIAS argument will be used. When this is the case, any character in ALIAS that is outside the permissible range of characters will be replaced by an underscore. -signedjar FILE Use this option to specify the file name of the signed JAR. If this option is omitted, then the signed JAR will be named the same as FILE; i.e., the input JAR file will be replaced with the signed copy. Verification options The following options may be specified when using the tool for verification purposes. -verify Use this option to indicate that the tool is to be used for verification purposes. -certs This option is used in conjunction with the -verbose option. When present, along with the -verbose option, the tool will print more detailed information about the certificates of the signer(s) being processed.
BUGS
SEE ALSO
AUTHOR
More Linux Commands
manpages/systemd-user.conf.5.html
systemd-user.conf(5) System and session service manager conf
When run as system instance systemd reads the configuration file system.conf, otherwise user.conf. These configuration files contain a few settings controlling
manpages/pam_close_session.3.html
pam_close_session(3) - terminate PAM session management.....
The pam_close_session function is used to indicate that an authenticated session has ended. The session should have been created with a call to pam_open_session
manpages/gnutls_openpgp_privkey_get_subkey_idx.3.html
gnutls_openpgp_privkey_get_subkey_idx(3) - API function.....
Get index of subkey. RETURNS the index of the subkey or a negative error value. SINCE 2.4.0 REPORTING BUGS Report bugs to <bug-gnutls@gnu.org>. GnuTLS home page
manpages/tcsendbreak.3.html
tcsendbreak(3) - get and set terminal attributes, line contr
The termios functions describe a general terminal interface that is provided to control asynchronous communications ports. The termios structure Many of the fun
manpages/glEvalMesh2.3gl.html
glEvalMesh2(3gl) - compute a one- or two-dimensional grid of
glMapGrid and glEvalMesh are used in tandem to efficiently generate and evaluate a series of evenly-spaced map domain values. glEvalMesh steps through the integ
manpages/prunehistory.8.html
prunehistory(8) - Remove tokens from Usenet history file....
prunehistory modifies a history(5)-format text file to remove a set of tokens from it. The tokens are removed by overwriting them with spaces, so that the size
manpages/tclvars.n.html
tclvars(n) - Variables used by Tcl - Linux manual page......
tclvars.n - The following global variables are created and managed automatically by the Tcl library. Except where noted below, these variables should normally b
manpages/ping.8.html
ping(8) - send ICMP ECHO_REQUEST to network hosts (ManPage)
ping uses the ICMP protocols mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (pings) have an IP a
manpages/gdbm.3.html
gdbm(3) - The GNU database manager. Includes dbm and ndbm co
GNU dbm is a library of routines that manages data files that contain key/data pairs. The access provided is that of storing, retrieval, and deletion by key and
manpages/TAP::Parser::Iterator::Stream.3pm.html
TAP::Parser::Iterator::Stream(3pm) - Iterator for filehandle
This is a simple iterator wrapper for reading from filehandles, used by TAP::Parser. Unless youre writing a plugin or subclassing, you probably wont need to use
manpages/netlink.3.html
netlink(3) - Netlink macros (Library - Linux man page)......
<linux/netlink.h> defines several standard macros to access or create a netlink datagram. They are similar in spirit to the macros defined in cmsg(3) for auxili
manpages/XeviGetVisualInfo.3.html
XeviGetVisualInfo(3) - X Extended Visual Information functio
The X11 Extended Visual Information extension (EVI) allows a client to determine information about core X visuals beyond what the core protocol provides. The EV
