Ben Kruger - 23 Feb 05 19:38 This is a show stopper for me since my new company runs CVS on Windows and only allows the sspi protocal. From searching on google this seems to be hindering a lot of other engineers.

Manfred Moser - 30 Jun 05 21:00 While you are at it it might be worth looking at the sserver protocol as well. This is the simple yet secure protocol. sspi is more related to windows specifics where as sserver is more platform independent. Btw. the CVSNT mailinglist is very helpful. manfred

Thomas Singer - 30 Jun 05 22:25 sserver is simple, but I gave up with sspi.

Kerwin Bonsol - 20 Sep 06 22:19 Has the sserver protocol been worked on? Is there a workaround available now to use the sserver protocol?

Yegor Yarko - 03 Jul 07 16:20 Seems, the following can work as a workaround for SSPI protocol (checked with IDEA build #7041): Assuming CVSNT is installed on the client machine. 1. modify CVSNT's extnt.ini file to include the section: [<CVS server name>] protocol=sspi hostname=<CVS server name> directory=/<CVS repository name> 2. Add new CVS root in IDEA with the following parameters: CVS root: :ext:<CVS user name>@<CVS server name>:/<CVS repository name> Path to external rsh: <path to CVSNT directory>\extnt.exe Additional parameters: -P <CVS password>

Dmitry Jemerov - 16 Jul 07 17:21 See http://wiki.netbeans.org/wiki/view/FaqCVSHowToProtocolsCVSNT for additional documentation.