Hi Todd, Thanks for pointing people in the right direction...
> connect using ssh, in this way the users can specify their Windows servers of course do not support ssh (unless you want to "break" windows security by hacking an SSH server into windows, which I have seen done but usually results in more backdoors than windows usually has...). The "problem" descirbed is most easily solved with SSPI so that the users authenticated token is used as their credentials instead (just like a printer or file share). Cvsnt also allows "generic" pserver logins, so a CVSROOT :pserver:host:/aaa for me assumes [EMAIL PROTECTED] wheras for you would assume [EMAIL PROTECTED] etc etc. I'm not sure if that is unique to CVSNT still, but I'm pretty sure it was at one stage... Regards, Arthur
