[p4] client on secured network

[Lee Marzke]

You might surely need it if you don't want your passwords and data sent 
in the clear.
( e.g. for any Perforce connection over the Internet )

Plus it means on the server side, only port 22 is exposed to probes, so 
no one
knows theres a P4 server running ( in case of any known exploits )

Lee Marzke

Paul Goffin wrote:
> You don't need any of this, surely?
>
> If port 22 is open for SSH, just run the p4 server on port 22.
>
> Paul.
>
>
> -----Original Message-----
> From:	Jeff With The Big Yellow Suit [mailto:jeff at drinktomi.com]
> Sent:	Mon 26/06/2006 17:07
> To:	Samuel M T Ehrlichman
> Cc:	perforce-user at perforce.com
> Subject:	Re: [p4] client on secured network
>
>  >Does any of you p4 experts know a way I can continue to use p4 from  
> the
>  > office under the circumstances?  Can I get the client to use http
>  > tunneling or something like that?  (The documentation regarding ssh
>  > tunneling seems to focus on the situation where the *server* is on a
>  > secure network, which is not the issue here.)
>
> The syntax is a little clunky, but ssh will do what you want.
>
> PORT=1666
> SERVER=200.220.18.7
> USER=joe
> ssh -L ${PORT}:localhost:${PORT} ${USER}@${SERVER}
>
> Then point your p4 client to localhost:${PORT}.  The local
> port ${PORT} will be forwarded to the port localhost:${PORT}
> on the machine ${SERVER}.
>
> As long as the SSH connection stays active the tunnel will be up.
>
> -jeff
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>