[MERGE] authentication ring specification

[Vincent Ladeuil]

>>>>> "bialix" == Alexander Belchenko <bialix at ukr.net> writes:


    bialix> I carefully read your document and I think I understand it well.
    bialix> +1 conditional. See some comments below.

    bialix> Vincent Ladeuil пишет:
    >> +  * all connections are done with the same ``user`` (the local one) and the
    >> +    password is always prompted with some exceptions::
    >> +
    >> +        # Pet projects on hobby.net
    >> +        [hobby]
    >> +        scheme=https
    >> +        host=r.hobby.net
    >> +        self_certified==yes
    >> +        user=jim
    >> +        password=obvious1234

    bialix> ^-- probably self_certified=yes with one equal sign?

Obviously :)


<snip/>

    bialix> Just one idea, not the real nitpicking.
    bialix> Can we add global flag --remember-auth or --remember-password,
    bialix> or --store-password-plain/--store-password-plain-base64 or something similar
    bialix> to address the question below:

That's a good idea, I'll look into it when I'll come back (circa August 20th).

    bialix> +Questions and Answers
    >> +---------------------
    >> +
    >> +  * Why can't bzr update the authentication file when it queried the user for a
    >> +    password ?
    >> +
    >> +    * a future version may address that but:
    >> +
    >> +      1. The user may want to decide which passwords are stored in the file and
    >> +         which aren't.
    >> +
    >> +      2. The user should decide if the passwords are encoded or not.

    bialix> Because encoding of password with base64 is not
    bialix> simple task, if you're not programmer, IMO.

Sure.

Thanks for the review,

        Vincent