[AccessD] Source Code Control

> Basically it equates to tunneling through SSH and then using SSH to
> perform your checkout.
Thank you, Josh!

I will check the ref - but this could be not what I wanted.
What I wanted is to keep SubVersion running on a public Web server and to
store source files in it encrypted.
And to encrypt/decrypt them on client side transparently to the development
tools during check-in/check-out.

Please dont' spend time to look for this feature - just post info about it
here if you ever see it occasionally somewhere ....

Shamil

----- Original Message ----- 
From: "Josh McFarlane" <darsant at gmail.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, January 19, 2006 3:28 AM
Subject: Re: [AccessD] Source Code Control


> On 1/18/06, Shamil Salakhetdinov <shamil at users.mns.ru> wrote:
> > > As far as actual encryption of the data passed, I haven't looked into
> > > it much. I'll see what I can find out and let you know.
> > Thank you and thank in advance, Josh!
>
> OK, I can't find anywhere that says it has any built in encryption
> support for data transport, however, you can use their server service
> and SSH.
>
> Basically it equates to tunneling through SSH and then using SSH to
> perform your checkout.
>
> See http://subversion.tigris.org/faq.html#paranoid
>
> --
> Josh McFarlane
>
> "Peace cannot be kept by force. It can only be achieved by understanding."
> -Albert Einstein
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com