Re: Howto specify password and AUTH field in POP url ?

[Sam Roberts]

You might want to look at the wicket_t, an example of it being used is
sieve. It gets usernames and passwords from a ticket file, but if your
application had another type of ticket store, you could make a version
that retrieved passwords from wherever you store your passwords.

It didn't occur to me to allow both, I'm not sure what it would look
like,

     pop://user:password;address@hidden  ?
     pop://user;AUTH=+APOP:address@hidden  ?

                 either?

Only the  address@hidden and user;address@hidden forms are standardized, by
the way, the user:address@hidden is an extension based on how other protocols
allow passwords to be specified. The pop3 url format doesn't allow
passwords for "security" reasons, that don't apply under many
conditions.

As you are finding out, the whole authentication framework is very
biased towards interactive command line utilities, and username and
password using authentication algorithms. It needs to be
reworked.

One thing I wanted to do was be able to register multiple authentication
sources, so you put the wicket_t object first, then some object that
queries the user, for example. As soon as one of the auth objects
returns the auth info, then the search would stop. As it is, you have
only one source, and only user names and passwords, what if you needed a
private key and a certificate to complete an ssl exchange?

Btw, I did document this in url.texi, did you find this, or is it too
dusty a corner?

Cheers,
Sam


-- 
Sam Roberts <address@hidden>