Establish trust of an SSL connection to a Perforce service.

Use the command p4 trust -h to get help for the server (if you have not yet trusted your server). You must do this because the command is implemented on the client rather than the server. When a command begins with p4 help, the client forwards it to the server to construct the text of what is displayed on the client machine. In the case of the trust command, the client might not trust the server to send any commands to it, so the help must begin with p4 trust to get it serviced locally by the client rather than have it forwarded to the server.

p4 [g-opts] 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 Perforce service, you are prompted with its fingerprint; if the fingerprint is correct, you can use p4 trust to add the service’s fingerprint to your trust file. If the fingerprint changes (or expires), subsequent attempts to connect to that service will result in warning or error messages.

Your system administrator can help you confirm the accuracy of any fingerprint (or change to a fingerprint) provided to you by a Perforce service.

Only after you have added an SSL-enabled Perforce service to your P4TRUST file can you connect to it by setting P4PORT to ssl:hostname:port.