[cvsnt] Secure alternatives to SSPI
Michael.Wojcik at microfocus.com
Thu Sep 14 23:07:40 BST 2006
> From: cvsnt-bounces at cvsnt.org
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Jim Hyslop
> Sent: Thursday, 14 September, 2006 17:20
> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Currently, our CVSNT server (running Windows Server) is set up to use
> SSPI authentication. There are two minor problems with this, however.
> First, I'd like to be able to work from home, and my login credentials
> at home are not recognized at work (obviously).
I use CVSNT at home with our servers at work, using SSPI, and my
home-network credentials are not the same as my work credentials.
There's no problem there; I just do a "cvs login" with an appropriate -d
option (or CVSROOT environment setting) when I create a new sandbox.
My connection to the corporate network is secure (it's a VPN), of
> Second, and more
> importantly, I'd like to set up an automated daily build
> system that can
> check out the code. If I use the Windows 'at' command, then
> the command
> will run with SYSTEM privileges, i.e. no login credentials.
Just have your automated system run cvs with an appropriate -d option
setting, in a sandbox where you've done a "cvs login". That's how our
automated build system works.
Principal Software Systems Developer
michael.wojcik at microfocus.com
9420 Key West Avenue
Rockville, MD 20850
Direct: 517 676 0892
What would you like Micro Focus to do for you? Contribute your view by
More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter CVSNT on Facebook