Kieredin Garbaa (privat) wrote:
> Hi there,
>
> we are a small group of hobby-developpers from Germany and enjoy using
> SVN to bring together our projects from people all over Germany (acting
> as configmanagers).
>
> In this context we found an issue we would love to see implemented and
> doesn't seem to be too difficult to do so.
>
>
> Problem description:
>
> - In our configuration (see attached Drawing.pdf) we have *one domain*
> where several repositories are attached to
>
> - Each repository is accessible by one individual ssl-certificate
>
> - Here is the problem: When we initially click "save certificate" a
> reference to *only the domain* is saved to the registry
>
> - Effect: It is not possible to distinguish and save one certificate
> *per* repository. Our current Solution is to export a Key for every
> single configuration (Repository+CertificatePath) we have and switch
> between these before using the disiered Repository.
>
>
> Idea for a solution:
>
> - Save the Domain+the folder someone has rightclicked on, to the
> registry instead of only the domain.
> - or at least have an otion to do so ( first check the complete Path ;
> if no certificate is found look for a Regkeyvalue with
> Domain+Repositoryfolder [or port]; if all that doesn't exist ask for a
> certificate)
>
> Example:
>
> Suppose following structure:
>
> https://bla.com/Repos1 = certificate1
> https://bla.com/Repos2 = certificate2
>
> could be realized by simply saving the domain (https://bla.com) plus the
> Folder wanted by the user (In this case Repos1 or Repos2) to the
> /Servers/Groups entry in the regestry. Maybe also plus the port If a
> User has two different Repositories on the same domain but on different
> virtual hosts.
>
> Not very difficult to do and we think it could be a great enhancement in
> working with ssl-certificates in Totoise.
If it's not that difficult to do, why don't you send a patch for this? :)
Seriously: please avoid such comments if you don't have even looked at
the sourcecode.
That said: saving the certificate is implemented in TSVN (Subversion
doesn't do it, you have to do it manually). TSVN does this by parsing
the realm string passed down to it by Subversion when the certificate is
needed the first time. I'm not even sure if it's possible to save those
per-repository and not per-domain.
You can try it yourself: open the settings dialog, go to the network
tab. Then click on the "Edit" button to open the servers config file in
a text editor. There, you'll find a lot of comments on how to configure
Subversion with certificates. Just add your per-repository certs there
with the url including the repository path - if it works, ok. But if it
doesn't, then you have to go to the Subversion mailing list and ask for
this feature.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 23 09:17:14 2006