[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] proposal : ~/.authinfo

From: Tom Lord
Subject: Re: [Gnu-arch-users] proposal : ~/.authinfo
Date: Thu, 11 Mar 2004 12:33:17 -0800 (PST)

    > From: Matthieu Moy <address@hidden>

    > Tom Lord <address@hidden> writes:

    > >     > Should I implement  it on tla 1.2  or do you suggest I  upgrade 
to the
    > >     > latest development version for that ? 

    > > Branch off of the recently created 1.3 line, please.

    > Ah, too late  ;-) I've already posted the modified  file, based on tla
    > 1.2 :-(

No big deal.

    > As the ML has problems, here it is again :


I want to gently poke you in the direction of setting up a public
archive from which I can merge.

    > > I'm not so sure that "machine/login/password" is the right idea.
    > > Shouldn't that be, instead, something more flexible and generic like:

    > >     url "http://%s:address@hidden/"; YOURUSERNAMEHERE YOURPASSWORDHERE

    > Hmm, ~/.authinfo is shared  between many applications (many mailers or
    > newsreaders for  example use this  convention. This includes  at least
    > slrn, Gnus), so, introducing a new syntax may break the existing.

Hehe.  I thought it was something you were inventing.   Looks like a
problematic convention from the little bit of data I've inferred from
you but I'll add it to my list of things to explore and understand
before passing judgement.

Lemme catch up before commenting further.

    >> It'd be swell to write up a little formal spec of this functionality
    >> and  to publish it  as an  arch-independent library  with absolutely
    >> minimal dependencies. 

    > I was surprised  not to find this already, but in  the sources of slrn
    > I've looked at,  for example, they just have ad  hoc code, with global
    > variables and all, so I thought  it was simpler to re-write it instead
    > of reusing it.

    > But my code has almost no dependancies, so it's really reusable.

It'd be schwell to have it also play with a key manager.

I wonder (semi-idly) if qagent might not be a better approach here.
It seems to me to have a good start of a quite general interface.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]