omz13

I have now released build #2 of cvssproxy (a cvs secure proxy, i.e. client pserver protocol accepted by the proxy then forwarded as sserver protocol).

The main changes from cvssproxy build #1 are:

• It is now a fully-fledged Windows application and lives in the system tray (no more running as a console application).
• It no longer needs the SSL DLLs as OpenSSL is now statically linked into it; whilst this means it has increased in size, it also means that it has no dependencies whatsoever.
• Memory leaks have been fixed.
• Speed and memory optimization has occurred.
• It can now be considered BETA instead of ALPHA quality.

Enjoy!

On the cvsnt list there has been a lot of activity recently regarding sserver. For some people, setting up and using sserver is a real pain, especially if they use a client/ide that only supports the pserver protocol.

Tony Hoyle made this observation:

I actually wonder if a local proxy would be useful – eg. you connect to localhost:2401 via pserver and it does the relevant handshake and connects in a secure manner.  It’s basically what extnt does I guess, but people do seem to have problems configuring that.

I’ve been thinking about doing something similar for ages, so this was the very excuse I neeed to go and hack some code together. Yes, that right, I build a proof-of-concept sserver proxy for cvs, or cvssproxy for short.

More details are on the cvssproxy page. Enjoy!