Re: Request: Specifications / Requirements that only svn canmeet

[Ted Stern <do...@gmail.com>]

On 08 May 2009 14:46:40 -0700, webpost@tigris.org wrote:
>
> Steve,
>
> You are correct, we primarily want to avoid the Expensive Bloated
> Version Control System (tm).
>
> Requirements that CVS and svn (and perhaps other open source
> software) can meet but commercial products can not would be fine.
>
> In the meantime I'll start bringing together some information on the
> long term costs of using the other system. As a former site
> administrator of the commercial system in question I am in an
> especially good place to make that argument.
>
> -Andrew

Here are a couple of requirements I don't think "EBVCS" can handle,
but it's possible to do it in OSS tools such as Subversion, Git,
Mercurial, Bazaar, etc.:

High security access from anywhere on the internet.

You can set up a single account that is the only one that can view the
project.

Then you multiplex the account via its ~/.ssh/authorized_keys file.

Documented for Subversion in

     http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks
     (Trick #4)

and
     http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth    

There are similar ssh server modes for other systems.

This lets you access the code from anywhere with an ssh route to the
host.

I need svn+ssh access this way because

1) Third party source code license requirements require secure access.
2) Users/developers are nationwide and don't have local accounts.
3) It works from any OS that OpenSSH runs on :-).

plus this bit of sugar:

4) With svnserve's --tunnel-user option, you can change the log into a
   human-readable name format.  This is a welcome change from CVS
   because our login names are basically line noise.  The name I
   convert to is the standard name email format, first.last
   (@company.com is assumed).


Ted
-- 
 Frango ut patefaciam -- I break so that I may reveal

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2125290

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Request: Specifications / Requirements that only svn canmeet

[Les Mikesell <le...@gmail.com>]

Ted Stern wrote:
> On 08 May 2009 14:46:40 -0700, webpost@tigris.org wrote:
>> Steve,
>>
>> You are correct, we primarily want to avoid the Expensive Bloated
>> Version Control System (tm).
>>
>> Requirements that CVS and svn (and perhaps other open source
>> software) can meet but commercial products can not would be fine.
>>
>> In the meantime I'll start bringing together some information on the
>> long term costs of using the other system. As a former site
>> administrator of the commercial system in question I am in an
>> especially good place to make that argument.
>>
>> -Andrew
> 
> Here are a couple of requirements I don't think "EBVCS" can handle,
> but it's possible to do it in OSS tools such as Subversion, Git,
> Mercurial, Bazaar, etc.:
> 
> High security access from anywhere on the internet.
> 
> You can set up a single account that is the only one that can view the
> project.
> 
> Then you multiplex the account via its ~/.ssh/authorized_keys file.
> 
> Documented for Subversion in
> 
>      http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks
>      (Trick #4)
> 
> and
>      http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth    
> 
> There are similar ssh server modes for other systems.
> 
> This lets you access the code from anywhere with an ssh route to the
> host.
> 
> I need svn+ssh access this way because
> 
> 1) Third party source code license requirements require secure access.
> 2) Users/developers are nationwide and don't have local accounts.
> 3) It works from any OS that OpenSSH runs on :-).
> 
> plus this bit of sugar:
> 
> 4) With svnserve's --tunnel-user option, you can change the log into a
>    human-readable name format.  This is a welcome change from CVS
>    because our login names are basically line noise.  The name I
>    convert to is the standard name email format, first.last
>    (@company.com is assumed).

Or, use https with an apache configuration that requires a client 
certificate.

-- 
   Les Mikesell
    lesmikesell@gmail.com

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2154567

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].