Bug 184114 - [Connections] Add CVS SServer (SSL) native protocol support
Summary: [Connections] Add CVS SServer (SSL) native protocol support
Status: RESOLVED DUPLICATE of bug 41097
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2.2   Edit
Hardware: PC All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-04-25 16:27 EDT by David Carver CLA
Modified: 2007-04-26 09:34 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Carver CLA 2007-04-25 16:27:30 EDT
Build ID: 3.2.x

Steps To Reproduce:
Currently there is an old CVS plugin that adds sserver support.  It would be nice to have this native in eclipse.


More information:
Comment 1 Michael Valenta CLA 2007-04-26 09:10:26 EDT
I wasn't aware there was an SSL based connection method for CVS. What be benefit does it offer over SSH (or is it just more firewall friendly)? Could you include a link to the "old plug-in" you are referring to. 

Unfortunately, we really don't have the manpower to address this but we would be happy to accept a contribution.
Comment 2 David Carver CLA 2007-04-26 09:20:48 EDT
Here is the link to the SSL plugin:

http://home.arcor.de/rolf_wilms/cvsssl/cvsssl_help.html

Big benefit is that it is much more Windows friendly instead of having to have an SSH server, which isn't native to Windows.   Other clients already support this like: SmartCVS, CVSNT command line utilies, and TortoiseCVS
Comment 3 Michael Valenta CLA 2007-04-26 09:34:43 EDT
OK. I did some digging and we have already provided a link to that plug-in in the wiki (http://wiki.eclipse.org/index.php/CVS_Plugins). I agree that it would be nice if this support was included in Eclipse. However, at this stage, I think it is up to the author to decide if they want to contribute the plug-in or not. 

*** This bug has been marked as a duplicate of bug 41097 ***