Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Is explicit inhibition of authentication supported now?
Date: Mon, 10 Jun 2013 00:14:41 -0400	[thread overview]
Message-ID: <m2obbeeh5a.fsf@lifelogs.com> (raw)
In-Reply-To: <mailman.25474.1368199821.855.info-gnus-english@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

On Fri, 10 May 2013 23:30:00 +0800 XeCycle <XeCycle@Gmail.com> wrote: 

X> Some time ago I was told that upon connecting a NNTP server the
X> authinfo file is always read, so as not to miss any lines with
X> `force' for the server.  But it causes inconvenience when my
X> authinfo file is encrypted.

X> So I came again to ask, can I now inhibit reading of
X> authentication information for a specific server?  If not, I'm
X> seriously requesting this feature.  I do have some sort of GPG
X> agent running, but I think it better to give this option.

Hi Carl,

see the attached patch.  I am not sure if the parameter will be called
`nntp-auth' but please try applying the patch once and see if the logic
is correct.  Let me know if you're not sure how to use this.

Thanks
Ted


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: nntp-auth.patch --]
[-- Type: text/x-patch, Size: 1277 bytes --]

diff --git a/lisp/nntp.el b/lisp/nntp.el
index 58135a1..1a9cf55 100644
--- a/lisp/nntp.el
+++ b/lisp/nntp.el
@@ -258,6 +258,9 @@ to insert Cancel-Lock headers.")
 This is usually slower, but on misconfigured servers that don't
 update their active files often, this can help.")
 
+(defvoo nntp-auth t
+  "If nil, never try to authenticate NNTP.")
+
 ;;; Internal variables.
 
 (defvoo nntp-retrieval-in-progress nil)
@@ -1191,11 +1194,12 @@ If SEND-IF-FORCE, only send authinfo to the server if the
   (let* ((list (netrc-parse nntp-authinfo-file))
 	 (alist (netrc-machine list nntp-address "nntp"))
          (auth-info
-          (nth 0 (auth-source-search
-		  :max 1
-		  :host (list nntp-address (nnoo-current-server 'nntp))
-		  :port `("119" "nntp" ,(format "%s" nntp-port-number)
-			  "563" "nntps" "snews"))))
+          (when nntp-auth
+            (nth 0 (auth-source-search
+                    :max 1
+                    :host (list nntp-address (nnoo-current-server 'nntp))
+                    :port `("119" "nntp" ,(format "%s" nntp-port-number)
+                            "563" "nntps" "snews")))))
          (auth-user (plist-get auth-info :user))
          (auth-force (plist-get auth-info :force))
          (auth-passwd (plist-get auth-info :secret))

[-- Attachment #3: Type: text/plain, Size: 162 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

       reply	other threads:[~2013-06-10  4:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.25474.1368199821.855.info-gnus-english@gnu.org>
2013-06-10  4:14 ` Ted Zlatanov [this message]
2013-06-28 16:20   ` Ted Zlatanov
2013-06-29  2:09     ` XeCycle
2013-05-10 15:30 XeCycle

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=m2obbeeh5a.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=info-gnus-english@gnu.org \
    /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).