11.07.2015 Views

Version Control with Subversion - Login

Version Control with Subversion - Login

Version Control with Subversion - Login

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Customizing Your <strong>Subversion</strong> Experiencehttp-auth-typesThis option is a semicolon-delimited list of authentication types supported by the NeonbasedWebDAV repository access modules. Valid members of this list are basic, digest,and negotiate.neon-debug-maskThis is an integer mask that the underlying HTTP library, Neon, uses for choosing whattype of debugging output to yield. The default value is 0, which will silence all debuggingoutput. For more information about how <strong>Subversion</strong> makes use of Neon, seeChapter 8, Embedding <strong>Subversion</strong>.ssl-authority-filesThis is a semicolon-delimited list of paths to files containing certificates of the certificateauthorities (or CAs) that are accepted by the <strong>Subversion</strong> client when accessing therepository over HTTPS.ssl-trust-default-caSet this variable to yes if you want <strong>Subversion</strong> to automatically trust the set of defaultCAs that ship <strong>with</strong> OpenSSL.ssl-client-cert-fileIf a host (or set of hosts) requires an SSL client certificate, you'll normally be promptedfor a path to your certificate. By setting this variable to that same path, <strong>Subversion</strong> willbe able to find your client certificate automatically <strong>with</strong>out prompting you. There's nostandard place to store your certificate on disk; <strong>Subversion</strong> will grab it from any pathyou specify.ssl-client-cert-passwordIf your SSL client certificate file is encrypted by a passphrase, <strong>Subversion</strong> will promptyou for the passphrase whenever the certificate is used. If you find this annoying (anddon't mind storing the password in the servers file), you can set this variable to thecertificate's passphrase. You won't be prompted anymore.store-plaintext-passwordsThis variable is only important on UNIX-like systems. It controls what the <strong>Subversion</strong>client does in case the password for the current authentication realm can only becached on disk in unencrypted form, in the ~/.subversion/auth/ caching area.You can set it to yes or no to enable or disable caching of passwords in unencryptedform, respectively. The default setting is ask, which causes the <strong>Subversion</strong> client toask you each time a new password is about to be added to the~/.subversion/auth/ caching area.ConfigThe config file contains the rest of the currently available <strong>Subversion</strong> runtime options—thosenot related to networking. There are only a few options in use as of this writing,but they are again grouped into sections in expectation of future additions.The auth section contains settings related to <strong>Subversion</strong>'s authentication and authorizationagainst the repository. It contains the following:store-passwordsThis instructs <strong>Subversion</strong> to cache, or not to cache, passwords that are supplied by theuser in response to server authentication challenges. The default value is yes. Set thisto no to disable this on-disk password caching. You can override this option for asingle instance of the svn command using the --no-auth-cache command-lineparameter (for those subcommands that support it). For more information, see the sectioncalled “Client Credentials Caching”.store-auth-creds196

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!