From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: nntp server news.gmane.org tries to use gnutls
Date: Wed, 08 May 2013 23:19:41 +0200 [thread overview]
Message-ID: <87sj1xi2z6.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <upzcppx1hfam.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> Yes, but that's what I was unsure about: is gunning for STARTTLS always
> the most reasonable thing to do...?
If it is available, I think encryption is, yes.
> (certificate validation failed, but that did not stop Gnus from
> continuing)
At least the CIA sniffers won't know what you were reading, although you
don't know for sure who was serving you articles.
[...]
> Possible solutions:
> - Automate the server certificate updates (once every 3 months)
> http://wiki.cacert.org/Software/CertApi
Does this allow renewal? It is unclear to me, but so it a lot of this
stuff.
> - Someone (ie. Lars) should get a higher level of trust with cacert.org
> and get longer-lived certs
Sounds like work to me, and I don't even have to do it...
> (I think I will try for the automated solution for my own certs)
Let us know how it goes!
Best regards,
Adam
--
"Hur långt man än har kommit Adam Sjøgren
är det alltid längre kvar" asjo@koldfront.dk
prev parent reply other threads:[~2013-05-08 21:19 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
2013-05-08 21:19 ` Adam Sjøgren [this message]
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=87sj1xi2z6.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).