Secure logon

[Kieran Benton]

Just a thought I've had lately. Ive been implementing a source control
system (as I pretty much despise CVS and Visual SourceSafe seems a bit
flakey) and now Im coming to secure it. The client and server of my app
communicate over sockets and I was wondering what everyone thought would be
the best way to implement strong security starting with the logon procedure?
Please bear in mind that Im very new to SSH and the crypto APIs and dont
really know how they relate to each other... Can anyone help?

Thanks alot
Kieran

 

[Harry Wohlfels]

Do you plan write a plugin for Dev. Studio .NET?
I am very interested. Using VSS now, but the technique
of VSS (file sharing) is not state of the art! CVS is better
but does not integrate smoothly in the dev. environment...

 

[Justin Rogers]

CVS can integrate smoothly with VS .NET, you just have to write the
appropriate source control interfaces. If you look at
www.gotdotnet.com/Workspaces they have a VS .NET plugin that allows you to
use Workspaces as your source control server. If you really like CVS then
I'd say go with that. SharpDevelop already has some CVS interfaces, and
they might not mind if you use some of that code to write a VS .NET plug-in.

 

[Kieran Benton]

Yup eventually. Still in the preliminary design stage at the moment.
Thinking of basing it on web services and additionally giving a ASP.NET
(obviously secured) front end so that you can get access to the repository
from anywhere. Ill probably add it to gotdotnet once i get properly started.

Kieran