Solaris tip of the week: Managing self-signed certificates


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Solaris tip of the week: Managing self-signed certificates
# 1  
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...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
phones(4)							   File Formats 							 phones(4)

NAME
phones - remote host phone number database SYNOPSIS
/etc/phones DESCRIPTION
The file /etc/phones contains the system-wide private phone numbers for the tip(1) program. /etc/phones is normally unreadable, and so may contain privileged information. The format of /etc/phones is a series of lines of the form: <system-name>[ ]*<phone-number>. The system name is one of those defined in the remote(4) file and the phone number is constructed from [0123456789-=*%]. The `=' and `*' characters are indicators to the auto call units to pause and wait for a second dial tone (when going through an exchange). The `=' is required by the DF02-AC and the `*' is required by the BIZCOMP 1030. Comment lines are lines containing a `#' sign in the first column of the line. Only one phone number per line is permitted. However, if more than one line in the file contains the same system name tip(1) will attempt to dial each one in turn, until it establishes a connection. FILES
/etc/phones SEE ALSO
tip(1), remote(4) SunOS 5.10 14 Jan 1992 phones(4)