Sponsored Content
Operating Systems Solaris Solaris BigAdmin RSS Solaris tip of the week: Managing self-signed certificates Post 302266513 by Linux Bot on Wednesday 10th of December 2008 11:40:03 AM
Old 12-10-2008
Solaris tip of the week: Managing self-signed certificates

Another Solaris tip from Jay Danielsen's "greetings from network.com" blog. Here is a utility to automate the process of importing a self-signed certificate from a remote host into a client's local truststore or certificate database, so the client can communicate with a secured service.

More...
 
PUPPET-CERT(8)							   Puppet manual						    PUPPET-CERT(8)

NAME
puppet-cert - Manage certificates and requests SYNOPSIS
Standalone certificate authority. Capable of generating certificates, but mostly used for signing certificate requests from puppet clients. USAGE
puppet cert action [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [--digest digest] [host] DESCRIPTION
Because the puppet master service defaults to not signing client certificate requests, this script is available for signing outstanding requests. It can be used to list outstanding requests and then either sign them individually or sign all of them. ACTIONS
Every action except 'list' and 'generate' requires a hostname to act on, unless the '--all' option is set. clean Revoke a host's certificate (if applicable) and remove all files related to that host from puppet cert's storage. This is useful when rebuilding hosts, since new certificate signing requests will only be honored if puppet cert does not have a copy of a signed certificate for that host. If '--all' is specified then all host certificates, both signed and unsigned, will be removed. fingerprint Print the DIGEST (defaults to md5) fingerprint of a host's certificate. generate Generate a certificate for a named client. A certificate/keypair will be generated for each client named on the command line. list List outstanding certificate requests. If '--all' is specified, signed certificates are also listed, prefixed by '+', and revoked or invalid certificates are prefixed by '-' (the verification outcome is printed in parenthesis). print Print the full-text version of a host's certificate. revoke Revoke the certificate of a client. The certificate can be specified either by its serial number (given as a decimal number or a hexadecimal number prefixed by '0x') or by its hostname. The certificate is revoked by adding it to the Certificate Revocation List given by the 'cacrl' configuration option. Note that the puppet master needs to be restarted after revoking certificates. sign Sign an outstanding certificate request. verify Verify the named certificate against the local CA certificate. OPTIONS
Note that any configuration parameter that's valid in the configuration file is also a valid long argument. For example, 'ssldir' is a valid configuration parameter, so you can specify '--ssldir directory' as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet cert with '--genconfig'. --all Operate on all items. Currently only makes sense with the 'sign', 'clean', 'list', and 'fingerprint' actions. --digest Set the digest for fingerprinting (defaults to md5). Valid values depends on your openssl and openssl ruby extension version, but should contain at least md5, sha1, md2, sha256. --debug Enable full debugging. --help Print this help message --verbose Enable verbosity. --version Print the puppet version number and exit. EXAMPLE
$ puppet cert list culain.madstop.com $ puppet cert sign culain.madstop.com AUTHOR
Luke Kanies COPYRIGHT
Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License Puppet Labs, LLC June 2012 PUPPET-CERT(8)
All times are GMT -4. The time now is 11:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy