From: Ted Zlatanov <tzz@lifelogs.com>
To: Gijs Hillenius <gijs@hillenius.net>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.
Date: Sun, 26 Sep 2010 07:27:48 -0500 [thread overview]
Message-ID: <87tylc1ygr.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxr46gv9.fsf@hillenius.net> (Gijs Hillenius's message of "Sun, 26 Sep 2010 10:36:42 +0200")
On Sun, 26 Sep 2010 10:36:42 +0200 Gijs Hillenius <gijs@hillenius.net> wrote:
GH> Doing this off-list, hope that is ok. i'll bring it there when I feel
GH> confident my contribution is useful.
No, please use the ding list. I use GMane so if you send me e-mail I
may not notice it for a while, and you'll feel ignored :) I've done
that unintentionally to a few people already. So I hope you don't mind
but I've cc-ed ding back.
GH> Yet, just now, all of a sudden, I realised:
GH> In *Messages* I get:
GH> Opening TLS connection to `mail.hillenius.net'...
GH> Opening TLS connection with `gnutls-cli -p imaps mail.hillenius.net'...failed
GH> Opening TLS connection with `gnutls-cli -p imaps mail.hillenius.net --protocols ssl3'...failed
GH> Opening TLS connection with `openssl s_client -connect mail.hillenius.net:imaps -no_ssl2 -ign_eof'...done
GH> That is two fails and a 'error but I'll ignore it". Could *that* explain
GH> why my .authinfo.gpg gets accessed *three* times? So far my explanation
GH> was that I'm accessing /three/ servers, a) xs4all 4 news, b)
GH> hillenius.net 4 mail and c) gmane 4 ding...
It should get opened once per server+port combination. But even that's
not necessary: we should look at the file age and know if it needs to be
reopened in auth-source. I want to fix the auth-source issues you and
others have reported, now that the (broken) GnuTLS support is checked
in, so I'll work on that over the next few days.
Ted
next prev parent reply other threads:[~2010-09-26 12:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OwjUu-0007Om-00@quimby.gnus.org>
2010-09-18 6:19 ` Ted Zlatanov
2010-09-18 11:47 ` Lars Magne Ingebrigtsen
2010-09-20 2:30 ` Ted Zlatanov
2010-09-20 8:14 ` Lars Magne Ingebrigtsen
2010-09-20 15:03 ` Ted Zlatanov
2010-09-25 12:47 ` Gijs Hillenius
2010-09-25 13:56 ` Lars Magne Ingebrigtsen
2010-09-25 15:12 ` Ted Zlatanov
[not found] ` <87mxr46gv9.fsf@hillenius.net>
2010-09-26 12:27 ` Ted Zlatanov [this message]
2010-09-26 12:38 ` tls.el I added '--insecure' (Was :Re: [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users.) Gijs Hillenius
2010-09-26 20:53 ` tls.el I added '--insecure' Ted Zlatanov
2010-09-20 10:47 ` [gnus git] Add ~/.authinfo to the default, since that's probably most useful for users Sebastian Krause
2010-09-20 14:59 ` Ted Zlatanov
2010-09-20 18:40 ` Michael Albinus
2010-09-20 14:27 ` Richard Riley
2010-09-20 15:01 ` Ted Zlatanov
2010-09-20 15:29 ` Richard Riley
2010-09-18 12:50 ` Sebastian Krause
2010-09-18 15:40 ` Lars Magne Ingebrigtsen
2010-09-18 21:29 ` Sebastian Krause
2010-09-18 21:31 ` Lars Magne Ingebrigtsen
2010-09-20 11:03 ` Robert Pluim
2010-09-20 14:10 ` Richard Riley
2010-09-20 14:59 ` Robert Pluim
2010-09-20 15:26 ` Ted Zlatanov
2010-09-20 15:43 ` Tibor Simko
2010-09-20 15:53 ` Robert Pluim
2010-09-21 16:19 ` 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=87tylc1ygr.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=gijs@hillenius.net \
/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).