.TH P4FILTER 1 "15 June 2000" "Akamai Technologies" "Perforce Accessories"
.SH NAME
p4filter \- Monitor Perforce data streams
.SH SYNOPSIS
.B p4filter
[
.B \-\-help
]
[
.B \-\-verbose
]
.I p4port user
.SH DESCRIPTION
.B p4filter
sits between a Perforce client, such as
.BR p4 (1),
and a Perforce server.  It monitors the data stream, and cuts off
connections where the declared Perforce user is different from the
.I user
specified on the command line.
.PP
.B p4filter
establishes a connection a remote Perforce server.  The location of
the server is specified by the
.I p4port
command-line argument.  All valid Perforce port specifications should
be accepted.
.PP
.B p4filter
is intended to be run in connection with some other authentication
mechanism, such as
.BR ssh (1).
.BR sshd (8)
can be configured to allow a user with a particular RSA key to only
run a particular command; if that command is set to run
.BR p4filter ,
then the user can set the P4PORT environment variable to
.I rsh:ssh -l p4user p4host
to cause all Perforce traffic to be fed through an authenticating and
encrypting ssh tunnel.
.SH OPTIONS
.TP
.B \-\-verbose
Display detailed information on the Perforce protocol exchange.
.TP
.B \-\-help
Print a summary of usage.
.SH EXIT STATUS
Returns 0 on success or 1 on some failure.  Note that no diagnostic
messages will be printed unless the
.I \-\-verbose
option is specified.
.SH SEE ALSO
.BR p4 (1),
.BR p4d (1),
.BR ssh (1),
.BR sshd (8)
.SH BUGS
.B p4filter
cannot directly communicated with a
.BR p4d (1)
using a specified
.I p4port
such as
.I rsh:p4d
.IR -i .
This is due to a bug in
.BR p4d ,
which writes to its standard input rather than its standard output
when in "interactive" mode.
.SH AUTHORS
David Maze <dmaze@akamai.com>