Rev 2628: Last review feedback, spec approved in file:///v/home/vila/src/experimental/auth.ring/
Vincent Ladeuil
v.ladeuil+lp at free.fr
Wed Sep 19 10:38:36 BST 2007
At file:///v/home/vila/src/experimental/auth.ring/
------------------------------------------------------------
revno: 2628
revision-id: v.ladeuil+lp at free.fr-20070919093834-0r03bryclv0p8oit
parent: v.ladeuil+lp at free.fr-20070912170642-ictbc9bfvdj5w842
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: auth.ring
timestamp: Wed 2007-09-19 11:38:34 +0200
message:
Last review feedback, spec approved
modified:
doc/developers/authentication-ring.txt authring.txt-20070718200437-q5tdik0ne6lor86d-1
-------------- next part --------------
=== modified file 'doc/developers/authentication-ring.txt'
--- a/doc/developers/authentication-ring.txt 2007-09-12 17:06:42 +0000
+++ b/doc/developers/authentication-ring.txt 2007-09-19 09:38:34 +0000
@@ -40,7 +40,7 @@
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 need to update them on a regular
+for users handling a lot of passwords who need to update them on a regular
basis.
Rationale
@@ -118,9 +118,9 @@
* ``password_encoding``: can be empty (default is ``plaintext``).
-Also note that an optional ``self_certified`` field will be allowed to force
-the connection to ``HTTPS`` hosts that provides a self certified certificate
-(the default should be to refuse the connection and inform the user).
+Also note that an optional ``verify_certificates=no`` field will allow the
+connection to ``HTTPS`` hosts that provides a self certified certificate (the
+default should be to refuse the connection and inform the user).
Multiple definitions can be provided and, for a given URL, bzr will select a
(``user`` [, ``password``]) based on the following rules :
@@ -334,6 +334,11 @@
default to ``getpass.get_user()`` and may attempt a second matching to obtain
a password.
+* As this specification proposes a matching between some credentials
+ definitions and real urls, the implementation should provide an optional UI
+ feedback about which credential definition is used. That will allow the user
+ to validate his definitions.
+
Questions and Answers
---------------------
More information about the bazaar-commits
mailing list