Gnus development mailing list
 help / color / mirror / Atom feed
From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: no forced authinfo in 5.6.2?
Date: Mon, 16 Mar 1998 14:22:42 -0500	[thread overview]
Message-ID: <199803161922.OAA28792@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <HBF.980314tbql@bombur2.uio.no> (message from Hallvard B Furuseth on Sat, 14 Mar 1998 01:06:40 +0100)

Excerpts from mail: (14-Mar-98) Re: no forced authinfo in 5.6.2? by Hallvard B Furuseth
> If nntp-authinfo-file is .netrc-compatible just because you wanted to
> reuse existing code to parse .netrc:
>
> I don't see any reason *not* to send authinfo to a machine mentioned
> in .authinforc.  If I have an authinfo password there, why would I
> want not to use it?

I thought the same thing, but Lars convinced me otherwise:

------- Start of exceprted message -------
To: ding@gnus.org
Subject: Re: feedback on AUTHINFO in qgnus-0.27
References: <199802191555.KAA18753@alderaan.gsfc.nasa.gov>
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date: 20 Feb 1998 03:31:45 +0100

"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:
> It sounds more complicated than it really is. Basically, if there's an entry
> for the server in ~/.authinforc, then send authinfo for that server whether
> challenged or not.

Hm.  Some servers only challenge when entering certain groups.  The
user may wish to stick the machine name and the user name into the
file, but not the password, and it would be annoying if that would
lead Gnus to send the authinfo (and promt the user for that
unnecessary password) even if the user doesn't want to read the
password-protected groups.
------- End of excerpted message -------

> If nntp-authinfo-file is .netrc-compatible so we can point it to .netrc:
>
> Bummer.
>
> * I can't have different FTP user/password and NNTP user/password
> on the same machine.
>
> * If I insert `machine some.server login hbf password newspassword',
> then the `ftp some.server' command will try to log in with my NNTP
> username and password.

I think you miss the point. You *can* point gnus-authinfo-file to your
~/.netrc, but you don't *have* to. The default has them being different
files. If your NNTP password is different from your FTP password, then use
separate files for NNTP and FTP.

> Maybe this format will fix it:
>
> machine some.server      login hbf password ftppassword
> machine nntp/some.server login hbf password newspassword

Yuck.

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Well, I didn't feel it was resolved.  Should I add a "force" tag?

Lars, as long as the "force" tag is an optional part of the syntax (i.e.,
Gnus defaults to "force no" if there is no "force" tag present) in order to
keep some semblance of compatibility with ~/.netrc, I see no problem with it.

Besides, I also see many advantages to this syntax. When people post to the
mailing list asking how to make Gnus automatically send authinfo for certain
servers, I will get a great thrill out of replying to them and writing "Use
the FORCE tag, Luke!" :-)

Please go ahead and implement it, Lars.

Later,
Ed


  reply	other threads:[~1998-03-16 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-08 20:46 Steinar Bang
     [not found] ` <m3iupil26f.fsf@sparky.gnus.org>
1998-03-14  0:06   ` Hallvard B Furuseth
1998-03-16 19:22     ` Edward J. Sabol [this message]
1998-03-17  8:01       ` Steinar Bang
1998-03-19 12:09       ` Lars Magne Ingebrigtsen
1998-03-20 10:44       ` Hallvard B Furuseth
1998-03-19 12:08     ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199803161922.OAA28792@alderaan.gsfc.nasa.gov \
    --to=sabol@alderaan.gsfc.nasa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).