<!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 ring — Bazaar 2.6.0 documentation</title>
<link rel="stylesheet" href="_static/default.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: './',
VERSION: '2.6.0',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="shortcut icon" href="_static/bzr.ico"/>
<link rel="top" title="Bazaar 2.6.0 documentation" href="index.html" />
<link rel="up" title="Specifications" href="specifications.html" />
<link rel="next" title="Bundles" href="bundles.html" />
<link rel="prev" title="Bazaar Apport Integration" href="apport.html" />
<link rel="stylesheet" href="_static/bzr-doc.css" type="text/css" />
</head>
<body>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="bundles.html" title="Bundles"
accesskey="N">next</a></li>
<li class="right" >
<a href="apport.html" title="Bazaar Apport Integration"
accesskey="P">previous</a> |</li>
<li><a href="http://bazaar.canonical.com/">
<img src="_static/bzr icon 16.png" /> Home</a> | </li>
<a href="http://doc.bazaar.canonical.com/en/">Documentation</a> | </li>
<li><a href="index.html">Developer Document Catalog (2.6.0)</a> »</li>
<li><a href="specifications.html" accesskey="U">Specifications</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="authentication-ring">
<h1>Authentication ring<a class="headerlink" href="#authentication-ring" title="Permalink to this headline">¶</a></h1>
<p>When accessing a remote branch (specified as an URL), it may occur that the
server requests an authentication.</p>
<p>This authentication can be provided in different ways:</p>
<p>1. Embedding the user and password
in the URL:</p>
<div class="highlight-python"><div class="highlight"><pre>bzr branch <scheme>://<user>:<password>@host:port/path
</pre></div>
</div>
<ul class="simple">
<li><tt class="docutils literal"><span class="pre">scheme</span></tt>: Any transport protocol requiring authentication.</li>
<li><tt class="docutils literal"><span class="pre">user</span></tt>: The login used to authenticate.</li>
<li><tt class="docutils literal"><span class="pre">password</span></tt>: The associated password.</li>
<li><tt class="docutils literal"><span class="pre">host</span></tt>: The address of the server.</li>
<li><tt class="docutils literal"><span class="pre">port</span></tt>: The port the server is listening to.</li>
<li><tt class="docutils literal"><span class="pre">path</span></tt>: The path on the server.</li>
</ul>
<p>2. Embedding the user in the URL and let bzr find the right password or prompt
for one:</p>
<div class="highlight-python"><div class="highlight"><pre>bzr branch <scheme>://<user>@host/path
</pre></div>
</div>
<p>3. Embedding nothing in the URL and let bzr find user and password or prompt
for user and/or password:</p>
<div class="highlight-python"><div class="highlight"><pre>bzr branch <scheme>://host/path
</pre></div>
</div>
<p>This specification proposes a mechanism that will allow users to
just use <tt class="docutils literal"><span class="pre">bzr</span> <span class="pre">branch</span> <span class="pre"><scheme>://host/path</span></tt> or <tt class="docutils literal"><span class="pre">bzr</span> <span class="pre">branch</span>
<span class="pre"><scheme>://<user>@host/path</span></tt> and leaves bzr find the <tt class="docutils literal"><span class="pre">user</span></tt>
and <tt class="docutils literal"><span class="pre">password</span></tt> in its configuration files.</p>
<p>When no user is specified for <tt class="docutils literal"><span class="pre">FTP</span></tt>, <tt class="docutils literal"><span class="pre">SFTP</span></tt> or <tt class="docutils literal"><span class="pre">SSH</span></tt>, the actual behavior
of <tt class="docutils literal"><span class="pre">bzr</span></tt> is to default to <tt class="docutils literal"><span class="pre">getpass.get_user()</span></tt>.</p>
<p>Any implementation of this specification should respect that behaviour.</p>
<p>This specification also proposes a way to describe credentials so that several
remote branches can use the same definition. This is particularily important
for users handling a lot of passwords and who need to update them on a regular
basis.</p>
<div class="section" id="rationale">
<h2>Rationale<a class="headerlink" href="#rationale" title="Permalink to this headline">¶</a></h2>
<p>Embedding user and passwords in the command line is a security
hazard (see <a class="reference external" href="https://launchpad.net/products/bzr/+bug/34685">bug #34685</a>).</p>
<p>Storing passwords in <tt class="docutils literal"><span class="pre">~/.bazaar/bazaar.conf</span></tt> or <tt class="docutils literal"><span class="pre">~/.bazaar/locations.conf</span></tt>
is also a security risk.</p>
<p>Typing user and passwords is error-prone and boring.</p>
<p>Yet, a safe way to store passwords, while allowing bzr to retrieve them, when
needed, could improve the bzr user experience.</p>
<p>This specification describes a way to provide user and passwords to bzr while
storing them in a relatively safe way.</p>
<p>Note that SSH servers can be configured to use keys instead of (<tt class="docutils literal"><span class="pre">user</span></tt>,
<tt class="docutils literal"><span class="pre">password</span></tt>) and, when used with appropriate agents, provide the same kind of
comfort this specification aims to provide for all other schemes. Since SSH
agents provide a safer way to secure the passwords, this specification is
restricted to providing <tt class="docutils literal"><span class="pre">user</span></tt> but does not provide <tt class="docutils literal"><span class="pre">password</span></tt> when used
for SSH.</p>
</div>
<div class="section" id="authentication-definitions">
<h2>Authentication definitions<a class="headerlink" href="#authentication-definitions" title="Permalink to this headline">¶</a></h2>
<p>There are two kinds of authentication used by the various schemes supported by
bzr:</p>
<ol class="arabic simple">
<li>user and password</li>
</ol>
<p><tt class="docutils literal"><span class="pre">FTP</span></tt> and <tt class="docutils literal"><span class="pre">SFTP</span></tt> needs a (<tt class="docutils literal"><span class="pre">user</span></tt>, <tt class="docutils literal"><span class="pre">password</span></tt>) to authenticate against a
<tt class="docutils literal"><span class="pre">host</span></tt> (SFTP can use SSH keys too, but we don’t talk about that in this
specification as SSH agents provide a better solution).</p>
<ol class="arabic simple" start="2">
<li>user, realm and password</li>
</ol>
<p><tt class="docutils literal"><span class="pre">HTTP</span></tt> and <tt class="docutils literal"><span class="pre">HTTPS</span></tt> needs a (<tt class="docutils literal"><span class="pre">user,</span> <span class="pre">realm,</span> <span class="pre">password</span></tt>) to authenticate
against a host. But, by using <tt class="docutils literal"><span class="pre">.htaccess</span></tt> files, for example, it is possible
to define several (<tt class="docutils literal"><span class="pre">user,</span> <span class="pre">realm,</span> <span class="pre">password</span></tt>) for a given <tt class="docutils literal"><span class="pre">host</span></tt>. So what is
really needed is (<tt class="docutils literal"><span class="pre">user</span></tt>, <tt class="docutils literal"><span class="pre">password</span></tt>, <tt class="docutils literal"><span class="pre">host</span></tt>, <tt class="docutils literal"><span class="pre">path</span></tt>). The <tt class="docutils literal"><span class="pre">realm</span></tt>
can be ignored <a class="footnote-reference" href="#ignored-realm" id="id1">[1]</a> as long as it is still presented to the user
when prompting for the password (unless someone found a way to declare two
different realms for the same path).</p>
<p><tt class="docutils literal"><span class="pre">HTTP</span> <span class="pre">proxy</span></tt> can be handled as <tt class="docutils literal"><span class="pre">HTTP</span></tt> (or <tt class="docutils literal"><span class="pre">HTTPS</span></tt>) by explicitly
specifying the appropriate port.</p>
<table class="docutils footnote" frame="void" id="ignored-realm" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id1">[1]</a></td><td>The true purpose of realms is to allow the same credentials
to be reused for disjoint hierarchies. Ignoring them in this specification
aims to simplify the user experience while still allowing to share the same
credentials for a whole hierarchy.</td></tr>
</tbody>
</table>
<p>To take all schemes into account, the password will be deduced from a set of
authentication definitions (<tt class="docutils literal"><span class="pre">scheme</span></tt>, <tt class="docutils literal"><span class="pre">host</span></tt>, <tt class="docutils literal"><span class="pre">port</span></tt>, <tt class="docutils literal"><span class="pre">path</span></tt>, <tt class="docutils literal"><span class="pre">user</span></tt>,
<tt class="docutils literal"><span class="pre">password</span></tt>).</p>
<blockquote>
<div><ul class="simple">
<li><tt class="docutils literal"><span class="pre">scheme</span></tt>: can be empty (meaning the rest of the definition can be used
for any scheme), <tt class="docutils literal"><span class="pre">SFTP</span></tt> and <tt class="docutils literal"><span class="pre">bzr+ssh</span></tt> should not be used here, <tt class="docutils literal"><span class="pre">ssh</span></tt>
should be used instead since this is the real scheme regarding
authentication,</li>
<li><tt class="docutils literal"><span class="pre">host</span></tt>: can be empty (to act as a default for any host),</li>
<li><tt class="docutils literal"><span class="pre">port</span></tt> can be empty (useful when an host provides several servers for the
same scheme), only numerical values are allowed, this should be used only
when the server uses a port different than the scheme standard port,</li>
<li><tt class="docutils literal"><span class="pre">path</span></tt>: can be empty (FTP or SFTP will never use it),</li>
<li><tt class="docutils literal"><span class="pre">user</span></tt>: can be empty (<tt class="docutils literal"><span class="pre">bzr</span></tt> will defaults to Python’s
<tt class="docutils literal"><span class="pre">getpass.get_user()</span></tt> for FTP, SFTP and SSH),</li>
<li><tt class="docutils literal"><span class="pre">password</span></tt>: can be empty (for security reasons, a user may use the
definitions without storing the passwords but want to be prompted ; or the
password will be provided by an external plugin via the
<tt class="docutils literal"><span class="pre">password_encoding</span></tt> mechanism decribed below). Must be left empty for
<tt class="docutils literal"><span class="pre">ssh</span></tt>.</li>
<li><tt class="docutils literal"><span class="pre">password_encoding</span></tt>: can be empty (default is <tt class="docutils literal"><span class="pre">plaintext</span></tt>).</li>
</ul>
</div></blockquote>
<p>Also note that an optional <tt class="docutils literal"><span class="pre">verify_certificates=no</span></tt> field will allow the
connection to <tt class="docutils literal"><span class="pre">HTTPS</span></tt> hosts that provides a self certified certificate (the
default should be to refuse the connection and inform the user). (Not
implemented yet)</p>
<p>Multiple definitions can be provided and, for a given URL, bzr will select a
(<tt class="docutils literal"><span class="pre">user</span></tt> [, <tt class="docutils literal"><span class="pre">password</span></tt>]) based on the following rules :</p>
<blockquote>
<div><ol class="arabic simple">
<li>the first match wins,</li>
<li>empty fields match everything,</li>
<li><tt class="docutils literal"><span class="pre">scheme</span></tt> matches even if decorators are used in the requested URL,</li>
<li><tt class="docutils literal"><span class="pre">host</span></tt> matches exactly or act as a domain if it starts with ‘.’
(<tt class="docutils literal"><span class="pre">project.bzr.sf.net</span></tt> will match <tt class="docutils literal"><span class="pre">.bzr.sf.net</span></tt> but <tt class="docutils literal"><span class="pre">projectbzr.sf.net</span></tt>
will not match <tt class="docutils literal"><span class="pre">bzr.sf.net</span></tt>).</li>
<li><tt class="docutils literal"><span class="pre">port</span></tt> matches if included in the requested URL (exact matches only)</li>
<li><tt class="docutils literal"><span class="pre">path</span></tt> matches if included in the requested URL (and by rule #2 above,
empty paths will match any provided path).</li>
</ol>
</div></blockquote>
<p>An optional <tt class="docutils literal"><span class="pre">password_encoding</span></tt> field may specify how the password is encoded
but has no impact on the definition selection.</p>
<p>Possible values are <tt class="docutils literal"><span class="pre">plaintext</span></tt> (no encoding at all) and <tt class="docutils literal"><span class="pre">base64</span></tt>. When the
field is absent, <tt class="docutils literal"><span class="pre">plaintext</span></tt> is assumed. Additional encodings may be added in
future versions.</p>
<p>Encoding passwords in <tt class="docutils literal"><span class="pre">base64</span></tt>, while weak, provides protection against
accidental reading (if an administrator have to look into the file, he will not
see the passwords in clear).</p>
<p>This specification intends to ease the authentication providing, not to secure
it in the best possible way.</p>
<p>Plugins can provide additional password encodings. The provided
<tt class="docutils literal"><span class="pre">netrc_credential_store</span></tt> plugin can be used as an example implementation.</p>
<p>Future versions of this specification may provide additional
encodings <a class="footnote-reference" href="#password-encoding" id="id2">[2]</a>.</p>
<table class="docutils footnote" frame="void" id="password-encoding" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id2">[2]</a></td><td>Additional password encoding methods may be defined
that will rely on external means to store the password which, in these
cases, will not appear anymore in the definition. It is assumed that
additional password encodings will provide a storage outside of the file
described here. The <tt class="docutils literal"><span class="pre">netrc</span></tt> encoding, for example, provides passwords by
retrieving them from the <tt class="docutils literal"><span class="pre">.netrc</span></tt> file.</td></tr>
</tbody>
</table>
</div>
<div class="section" id="file-format">
<h2>File format<a class="headerlink" href="#file-format" title="Permalink to this headline">¶</a></h2>
<p>Even if <tt class="docutils literal"><span class="pre">~/.bazaar/bazaar.conf</span></tt> and <tt class="docutils literal"><span class="pre">~/.bazaar/locations.conf</span></tt> seems to
provide most of the needed infrastructure, we choose to use a dedicated file
for the authentication info <tt class="docutils literal"><span class="pre">~/.bazaar/authentication.conf</span></tt> for the following
reasons:</p>
<blockquote>
<div><ul class="simple">
<li>allow the user to protect the content of one file only, relaxing security
constraints on the others,</li>
<li>while <tt class="docutils literal"><span class="pre">locations.conf</span></tt> is organized around <em>local</em> branches,
<tt class="docutils literal"><span class="pre">authentication.conf</span></tt> is organized around <em>remote</em> branches or more
generally servers. The same authentification definition can even be used
for several schemes for servers providing those schemes.</li>
</ul>
</div></blockquote>
<p><tt class="docutils literal"><span class="pre">~/.bazaar/authentication.conf</span></tt> will use the same file format as
<tt class="docutils literal"><span class="pre">~/.bazaar/bazaar.conf</span></tt>.</p>
<p>Each section describes an authentication definition.</p>
<p>The section name is an arbitrary string, only the <tt class="docutils literal"><span class="pre">DEFAULT</span></tt> value is reserved
and should appear as the <em>last</em> section.</p>
<p>Each section should define:</p>
<blockquote>
<div><ul class="simple">
<li><tt class="docutils literal"><span class="pre">user</span></tt>: the login to be used,</li>
</ul>
</div></blockquote>
<p>Each section could define:</p>
<blockquote>
<div><ul class="simple">
<li><tt class="docutils literal"><span class="pre">host</span></tt>: the remote server,</li>
<li><tt class="docutils literal"><span class="pre">port</span></tt>: the port the server is listening,</li>
<li><tt class="docutils literal"><span class="pre">verify_certificates</span></tt>: to control certificate verification (useful
for self certified hosts). This applies to HTTPS only. Accepted values
are yes and no, default to yes.</li>
<li><tt class="docutils literal"><span class="pre">path</span></tt>: the branch location,</li>
<li><tt class="docutils literal"><span class="pre">password</span></tt>: the password,</li>
<li><tt class="docutils literal"><span class="pre">password_encoding</span></tt>: the method used to encode the password if any,</li>
</ul>
</div></blockquote>
<p>The default content of the file will be:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="p">[</span><span class="n">DEFAULT</span><span class="p">]</span>
</pre></div>
</div>
<p>This section could define:</p>
<blockquote>
<div><ul class="simple">
<li><tt class="docutils literal"><span class="pre">user</span></tt>: default user to be used (if not defined the usual
bzr way applies, see below).</li>
<li><tt class="docutils literal"><span class="pre">password_encoding</span></tt>: default password encoding.</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="use-cases">
<h2>Use Cases<a class="headerlink" href="#use-cases" title="Permalink to this headline">¶</a></h2>
<p>The use cases described below use the file format defined above.</p>
<blockquote>
<div><ul>
<li><p class="first">all FTP connections to the foo.net domain are done with the same (<tt class="docutils literal"><span class="pre">user</span></tt>,
<tt class="docutils literal"><span class="pre">password</span></tt>):</p>
<div class="highlight-python"><div class="highlight"><pre># Identity on foo.net
[foo.net]
scheme=ftp
host=foo.net
user=joe
password=secret-pass
</pre></div>
</div>
<p>will provide (‘joe’, ‘secret-pass’) for:</p>
<div class="highlight-python"><div class="highlight"><pre>bzr branch ftp://foo.net/bzr/branch
bzr pull ftp://bzr.foo.net/bzr/product/branch/trunk
</pre></div>
</div>
</li>
<li><p class="first">all connections are done with the same <tt class="docutils literal"><span class="pre">user</span></tt> (the remote one for which
the default bzr one is not appropriate) and the password is always prompted
with some exceptions:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="c"># Pet projects on hobby.net</span>
<span class="p">[</span><span class="n">hobby</span><span class="p">]</span>
<span class="n">host</span><span class="o">=</span><span class="n">r</span><span class="o">.</span><span class="n">hobby</span><span class="o">.</span><span class="n">net</span>
<span class="n">user</span><span class="o">=</span><span class="n">jim</span>
<span class="n">password</span><span class="o">=</span><span class="n">obvious1234</span>
<span class="c"># Home server</span>
<span class="p">[</span><span class="n">home</span><span class="p">]</span>
<span class="n">scheme</span><span class="o">=</span><span class="n">https</span>
<span class="n">host</span><span class="o">=</span><span class="n">home</span><span class="o">.</span><span class="n">net</span>
<span class="n">user</span><span class="o">=</span><span class="n">joe</span>
<span class="c"># Obtain the base64 encoded password by running 'echo -n "secret-pass" | base64'</span>
<span class="n">password</span><span class="o">=</span><span class="s">'c2VjcmV0LXBhc3M='</span>
<span class="n">password_encoding</span><span class="o">=</span><span class="n">base64</span>
<span class="n">verify_certificates</span><span class="o">=</span><span class="n">no</span> <span class="c"># Still searching a free certificate provider</span>
<span class="p">[</span><span class="n">DEFAULT</span><span class="p">]</span>
<span class="c"># Our local user is barbaz, on all remote sites we're known as foobar</span>
<span class="n">user</span><span class="o">=</span><span class="n">foobar</span>
</pre></div>
</div>
</li>
<li><p class="first">an HTTP server and a proxy:</p>
<div class="highlight-python"><div class="highlight"><pre># development branches on dev server
[dev]
scheme=https
host=dev.company.com
path=/dev
user=user1
password=pass1
# toy branches
[localhost]
scheme=http
host=dev.company.com
path=/
user=user2
password=pass2
# proxy
[proxy]
scheme=http
host=proxy.company.com
port=3128
user=proxyuser1
password=proxypass1
</pre></div>
</div>
</li>
<li><p class="first">source hosting provider declaring sub-domains for each project:</p>
<div class="highlight-python"><div class="highlight"><pre>[sfnet domain]
# we use SFTP, but SSH is the scheme used for authentication
scheme=ssh
# The leading '.' ensures that 'sf.net' alone doesn't match
host=.sf.net
user=georges
password=ben...son
</pre></div>
</div>
</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="ui-changes">
<h2>UI Changes<a class="headerlink" href="#ui-changes" title="Permalink to this headline">¶</a></h2>
<p>Depending on the info provided in the URL, bzr will interact with the user in
different ways:</p>
<ol class="arabic simple">
<li><tt class="docutils literal"><span class="pre">user</span></tt> and <tt class="docutils literal"><span class="pre">password</span></tt> given in the URL.</li>
</ol>
<blockquote>
<div>Nothing to do.</div></blockquote>
<ol class="arabic simple" start="2">
<li><tt class="docutils literal"><span class="pre">user</span></tt> given in the URL.</li>
</ol>
<blockquote>
<div>Get a password from <tt class="docutils literal"><span class="pre">~/.bazaar/authentication.conf</span></tt> or prompt
for one if none is found.</div></blockquote>
<ol class="arabic simple" start="3">
<li>No <tt class="docutils literal"><span class="pre">user</span></tt> given in the URL (and no <tt class="docutils literal"><span class="pre">password</span></tt>).</li>
</ol>
<blockquote>
<div>Get a user from <tt class="docutils literal"><span class="pre">~/.bazaar/authentication.conf</span></tt> or prompt for one if none is
found. Continue as 2. (Not implemented yet)</div></blockquote>
<p>Note: A user will be queried only if the server requires it for <tt class="docutils literal"><span class="pre">HTTP</span></tt> or
<tt class="docutils literal"><span class="pre">HTTPS</span></tt>, other protocols always require a user.</p>
<p>In any case, if the server refuses the authentication, bzr reports to the user
and terminates.</p>
</div>
<div class="section" id="implementation-constraints">
<h2>Implementation constraints<a class="headerlink" href="#implementation-constraints" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>bzr should be able to prompt for a <tt class="docutils literal"><span class="pre">user</span></tt> for a given (<tt class="docutils literal"><span class="pre">scheme</span></tt>, <tt class="docutils literal"><span class="pre">host</span></tt>
[, <tt class="docutils literal"><span class="pre">realm</span></tt>]). Note that <tt class="docutils literal"><span class="pre">realm</span></tt> is available only after a first
connection attempt to the server.</li>
<li>No assumptions should be made about the clients of this service
(i.e. Transport is the primary target but plugins must be able to use it as
well, the definitions used: (<tt class="docutils literal"><span class="pre">scheme,</span> <span class="pre">host,</span> <span class="pre">[port,]</span> <span class="pre">path</span></tt>) are general
enough to described credentials for <tt class="docutils literal"><span class="pre">svn</span></tt> servers or LaunchPad XML-RPC
calls).</li>
<li>Policies regarding default users may be taken into account by the
implementations, there is no good way to represent that in this specification
and stays flexible enough to accommodate various needs (default user policies
may differ for different schemes and that may be easier to handle in the code
than in the authentication file itself).</li>
<li>If no user can be found by the mechanism described above, bzr should still
default to <tt class="docutils literal"><span class="pre">getpass.get_user()</span></tt> and may attempt a second matching to obtain
a password.</li>
<li>As this specification proposes a matching between some credentials
definitions and real URLs, the implementation provides an optional UI
feedback about which credential definition is used. Using <tt class="docutils literal"><span class="pre">-Dauth</span></tt> will
output some traces in the <tt class="docutils literal"><span class="pre">.bzr.log</span></tt> file metionning the sections
used. This allows the user to validate his definitions.</li>
</ul>
</div>
<div class="section" id="questions-and-answers">
<h2>Questions and Answers<a class="headerlink" href="#questions-and-answers" title="Permalink to this headline">¶</a></h2>
<blockquote>
<div><ul>
<li><p class="first">What if a <tt class="docutils literal"><span class="pre">.authinfo</span></tt> file exists ?</p>
<ul class="simple">
<li>It will be ignored,</li>
<li>Automatic (one-time) conversions may be proposed if sufficient demand
exists,</li>
</ul>
</li>
<li><p class="first">What if a <tt class="docutils literal"><span class="pre">.netrc</span></tt> file exists ?</p>
<ul class="simple">
<li>It is honored if the definition specifies
<tt class="docutils literal"><span class="pre">password_encoding=netrc</span></tt>.</li>
</ul>
</li>
<li><p class="first">What mode should the authentication file use ?</p>
<ul class="simple">
<li>600 read/write for owner only by default, if another mode (more
permissive) is used, a warning will be issued to inform the users of the
potential risks.(Not implemented yet)</li>
</ul>
</li>
<li><p class="first">What about using <tt class="docutils literal"><span class="pre">seahorse</span></tt> on Ubuntu or <tt class="docutils literal"><span class="pre">KeyChain</span> <span class="pre">Access</span></tt> on Mac OS X ?</p>
<ul class="simple">
<li>plugins can be written and registered to handle the associated
<tt class="docutils literal"><span class="pre">password_encoding</span></tt>.</li>
</ul>
</li>
<li><p class="first">Could it be possible to encode the whole authentication file with an SSH key
?</p>
<ul class="simple">
<li>yes and if the user configure a ssh-agent it will not be queried for
pass-phrase every time we want to query the file for a password. But
that seems a bit extreme for a first version.(Not implemented yet and
may be never)</li>
</ul>
</li>
<li><p class="first">Why can’t bzr update the authentication file when it queried the user for a
password ?</p>
<ul>
<li><p class="first">a future version may address that but:</p>
<p>1. The user may want to decide which passwords are stored in the file and
which aren’t.</p>
<p>2. The user should decide if the passwords are encoded (and how) or not
(but we may default to base64).</p>
<p>3. The right definition may be hard to get right, but reducing it to
(<tt class="docutils literal"><span class="pre">scheme,</span> <span class="pre">host,</span> <span class="pre">[port,]</span> <span class="pre">user,</span> <span class="pre">password</span></tt>) may be a good start. I.e. no
path so that all paths on the host will match. The user will have to
modify it for more complex configurations anyway.</p>
</li>
</ul>
</li>
</ul>
</div></blockquote>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Authentication ring</a><ul>
<li><a class="reference internal" href="#rationale">Rationale</a></li>
<li><a class="reference internal" href="#authentication-definitions">Authentication definitions</a></li>
<li><a class="reference internal" href="#file-format">File format</a></li>
<li><a class="reference internal" href="#use-cases">Use Cases</a></li>
<li><a class="reference internal" href="#ui-changes">UI Changes</a></li>
<li><a class="reference internal" href="#implementation-constraints">Implementation constraints</a></li>
<li><a class="reference internal" href="#questions-and-answers">Questions and Answers</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="apport.html"
title="previous chapter">Bazaar Apport Integration</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="bundles.html"
title="next chapter">Bundles</a></p>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/authentication-ring.txt"
rel="nofollow">Show Source</a></li>
</ul>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="bundles.html" title="Bundles"
>next</a></li>
<li class="right" >
<a href="apport.html" title="Bazaar Apport Integration"
>previous</a> |</li>
<li><a href="http://bazaar.canonical.com/">
<img src="_static/bzr icon 16.png" /> Home</a> | </li>
<a href="http://doc.bazaar.canonical.com/en/">Documentation</a> | </li>
<li><a href="index.html">Developer Document Catalog (2.6.0)</a> »</li>
<li><a href="specifications.html" >Specifications</a> »</li>
</ul>
</div>
<div class="footer">
© Copyright 2009-2011 Canonical Ltd.
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.2.3.
</div>
</body>
</html>
