<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Authentication</title>
<link rel="stylesheet" type="text/css" href="styles.css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1" />
<link rel="home" href="index.html" title="Version Control with Subversion" />
<link rel="up" href="svn.forcvs.html" title="Appendix B. Subversion for CVS Users" />
<link rel="prev" href="svn.forcvs.modules.html" title="Versioned Modules" />
<link rel="next" href="svn.forcvs.convert.html" title="Converting a Repository from CVS to Subversion" />
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Authentication</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="svn.forcvs.modules.html">Prev</a> </td>
<th width="60%" align="center">Appendix B. Subversion for CVS Users</th>
<td width="20%" align="right"> <a accesskey="n" href="svn.forcvs.convert.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" title="Authentication">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="svn.forcvs.auth"></a>Authentication</h2>
</div>
</div>
</div>
<p>With CVS's pserver, you are required to log in to the server
(using the <span class="command"><strong>cvs login</strong></span> command) before
performing any read or write operation—you sometimes even
have to log in for anonymous operations. With a Subversion
repository using Apache <span class="command"><strong>httpd</strong></span> or
<span class="command"><strong>svnserve</strong></span> as the server, you don't provide any
authentication credentials at the outset—if an operation
that you perform requires authentication, the server will
challenge you for your credentials (whether those credentials
are username and password, a client certificate, or even both).
So if your repository is world-readable, you will not be
required to authenticate at all for read operations.</p>
<p>As with CVS, Subversion still caches your credentials on
disk (in your <code class="filename">~/.subversion/auth/</code>
directory) unless you tell it not to by using the
<code class="option">--no-auth-cache</code> option.</p>
<p>The exception to this behavior, however, is in the case of
accessing an <span class="command"><strong>svnserve</strong></span> server over an SSH
tunnel, using the <code class="literal">svn+ssh://</code> URL scheme. In
that case, the <span class="command"><strong>ssh</strong></span> program unconditionally
demands authentication just to start the tunnel.</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="svn.forcvs.modules.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="svn.forcvs.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="svn.forcvs.convert.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Versioned Modules </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Converting a Repository from CVS to Subversion</td>
</tr>
</table>
</div>
<div xmlns="" id="svn-footer">
<hr />
<p>You are reading <em>Version Control with Subversion</em> (for Subversion 1.7), by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato.<br />
This work is licensed under the <a href="http://creativecommons.org/licenses/by/2.0/">Creative Commons Attribution License v2.0</a>.<br />
To submit comments, corrections, or other contributions to the text, please visit <a href="http://www.svnbook.com/">http://www.svnbook.com/</a>.</p>
</div>
</body>
</html>
distrib
>
Mageia
>
3
>
i586
>
media
>
core-updates
>
by-pkgid
>
1d6e0a3784534d5165fa22faeeca008d
>
files
>
65
