[p4] long ticket expiration
Russell C. Jackson
rusty at rcjacksonconsulting.com
Tue Jan 9 18:44:24 PST 2007
No, I asked Perforce that question specifically, and they said it is
encrypted.
Thanks,
Rusty
--------------------------------------------------
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
--------------------------------------------------
rusty at rcjacksonconsulting.com
http://www.rcjacksonconsulting.com
tel: 479-696-9710
fax: 479-967-0963
mobile: 479-747-3845
--------------------------------------------------
Paul Goffin wrote:
> The trouble is the communication between the perforce server and the client
> isn't (generally) secure.
>
> So if you use LDAP passwords, there's probably a stage where your LDAP
> password is passed, in clear, between your perforce client and the server.
>
> Which doesn't sound like a good idea to me.
>
> Paul.
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Chuck Karish
> Sent: 09 January 2007 15:00
> To: Mark Allender
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] long ticket expiration
>
>
> On 1/8/07, Mark Allender <marka at volition-inc.com> wrote:
>
>> IMHO, it would be nice to have a "fall-through" the auth-check to go
>> to normal Perforce passwords if the auth-check fails in some way.
>>
>
> The reason for choosing the LDAP integration is that normal Perforce
> passwords are insecure. If you want to favor convenience over security
> don't use auth-check in the first place.
>
>
More information about the perforce-user
mailing list