Previous Table of Contents Index Next
Perforce 2012.1: Command Reference

p4 trust
Establish trust of an SSL connection to a Perforce server.
p4 [-p port] trust [ -l -y -n -d -f -r -i fingerprint ]
Use p4 trust to manage the P4TRUST file (by default, .p4trust in your home directory) to establish (or manage) the trust of an SSL connection.
The trust file contains the fingerprints of the keys received for SSL connections; when you first connect to a server, you are prompted with its fingerprint; if the fingerprint is correct, you can use p4 trust to add the server's fingerprint to your trust file. If the fingerprint changes (or expires), subsequent attempts to connect to the server will result in warning or error messages.
Only after you have added an SSL-enabled server to your P4TRUST file can you connect to it by setting P4PORT to ssl:hostname:port.
-i fingerprint
List, install, or delete a replacement fingerprint. If a replacement fingerprint exists for the connection, and the primary fingerprint does not match (but the replacement fingerprint does), the replacement fingerprint replaces the primary. This flag may be combined with the -l, -i, or -d flags.
The P4PORT setting of the server from which to check or retrieve the fingerprint.
Usage Notes
Can File Arguments Use
Revision Specifier?
Your system administrator can help you confirm the accuracy of any fingerprint (or change to a fingerprint) provided to you by a Perforce Server.

Previous Table of Contents Index Next

Perforce 2012.1: Command Reference
Copyright 1999-2012 Perforce Software.