From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nntp server news.gmane.org tries to use gnutls
Date: Wed, 08 May 2013 13:38:57 +0200 [thread overview]
Message-ID: <upzcppx1hfam.fsf@dod.no> (raw)
In-Reply-To: <87zjw5j1y7.fsf@topper.koldfront.dk>
>>>>> asjo@koldfront.dk (Adam Sjøgren):
> To me it sounds like a feature - default to the most reasonable thing
> to do.
Yes, but that's what I was unsure about: is gunning for STARTTLS always
the most reasonable thing to do...?
> It sounds like a bug if it doesn't work, though.
Indeed.
> I don't think I have done anything like that to make it work - I may
> be misremembering though. Looks like I just have (require 'gnutls) and
> that's it.
I tried Katsumi Yamaoka's workaround, but that didn't work for me. I
just got
Opening nntp server on news.gmane.org...done
apply: Server closed connection
Since then it has sometimes worked and sometimes not. Entering
gmane.discuss worked, but entering this group immediately after,
failed.
So now I tried upping the GNUTls log level in Messages, by doing
(setq gnutls-log-level 1)
in the scratch buffer.
And then entering this group worked without a hitch... but I don't know
if this was coincidental or an actual effect. Have the gmane servers
had some issues today, I wonder...?
This is what the increased log level said:
Opening nntp server on news.gmane.org...
gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
news.gmane.org certificate could not be verified.
gnutls.c: [1] (Emacs) certificate signer was not found: news.gmane.org
gnutls.c: [1] (Emacs) certificate validation failed: news.gmane.org
Opening nntp server on news.gmane.org...done
(certificate validation failed, but that did not stop Gnus from
continuing)
>> (BTW it would be nice if the gmane.org certs were signed by cacert
>> instead of being self-signed)
> They just have to be updated quite often, which is a {b,ch}ore.
Possible solutions:
- Automate the server certificate updates (once every 3 months)
http://wiki.cacert.org/Software/CertApi
- Someone (ie. Lars) should get a higher level of trust with cacert.org
and get longer-lived certs
- Both of the above
(I think I will try for the automated solution for my own certs)
next prev parent reply other threads:[~2013-05-08 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 11:00 nnimap unable to open server unknown service 993 Steinar Bang
2013-05-07 16:05 ` David Engster
2013-05-07 21:34 ` Steinar Bang
2013-05-07 21:42 ` nntp server news.gmane.org tries to use gnutls (Was: nnimap unable to open server unknown service 993) Steinar Bang
2013-05-07 21:53 ` nntp server news.gmane.org tries to use gnutls Adam Sjøgren
2013-05-07 23:20 ` Steinar Bang
2013-05-08 0:17 ` Katsumi Yamaoka
2013-05-08 8:44 ` Adam Sjøgren
2013-05-08 11:38 ` Steinar Bang [this message]
2013-05-08 21:19 ` Adam Sjøgren
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=upzcppx1hfam.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).