开发者

Commit via SVN and Client certificate

开发者 https://www.devze.com 2022-12-21 12:25 出处:网络
Is there a way to commit code via SVN without SVN asking for a \'Client certific开发者_如何学Pythonate filename\' all the time?In your client you should be able to configure the path to the client cer

Is there a way to commit code via SVN without SVN asking for a 'Client certific开发者_如何学Pythonate filename' all the time?


In your client you should be able to configure the path to the client certificate, see the subversion docs

[examplehost]
ssl-client-cert-file = /path/to/my/cert.p12
ssl-client-cert-password = somepassword


At Ubuntu I had to add the following lines at the ~/.subversion/servers file:

[groups]
cacert = hostname
[cacert]
ssl-client-cert-file = /path/to/my/cert.p12
ssl-client-cert-password = somepassword

Without using [groups] and directly having the hostname (eg *.example.com), it did not work for me.

At svn advanced confarea, it states:

The servers file contains Subversion configuration options related to the network layers. There are two special sections in this file—[groups] and [global]. The [groups] section is essentially a cross-reference table. The keys in this section are the names of other sections in the file; their values are globs—textual tokens that possibly contain wildcard characters—that are compared against the hostnames of the machine to which Subversion requests are sent.

When Subversion is used over a network, it attempts to match the name of the server it is trying to reach with a group name under the [groups] section. If a match is made, Subversion then looks for a section in the servers file whose name is the matched group's name. From that section, it reads the actual network configuration settings.

0

精彩评论

暂无评论...
验证码 换一张
取 消