From: Alberto Luaces <aluaces@udc.es>
To: info-gnus-english@gnu.org
Subject: Re: Gmane with Gnus first timer
Date: Wed, 27 Sep 2017 18:04:21 +0200 [thread overview]
Message-ID: <874lrounzu.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <877ewk41ll.fsf@gmail.com>
Maxim Cournoyer writes:
> When I did, Emacs still complained that the server was deemed insecure
> because the "certificate signer was not found (self-signed)". I am not
> sure why it persists warning me about a self-signed certificate after
> I've explicitly given it my trust, nor do I know why the weak SHA1 issue
> is not raised anymore... But anyway, I consider our due diligence done,
> so at this point you may choose "Always" when presented the security
> prompt.
Thanks for the guide and congratulations for your new configuration.
I think all the hassle about the certificate is not worth the pain,
since after all you are downloading it by the same insecure method.
In this case I think it doesn't really matter, since all the lists and
postings are public.
--
Alberto
next prev parent reply other threads:[~2017-09-27 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 15:12 Maxim Cournoyer
2017-09-27 16:04 ` Alberto Luaces [this message]
2017-09-27 19:57 ` Maxim Cournoyer
2017-09-28 11:26 ` Alberto Luaces
2017-09-29 2:26 ` Maxim Cournoyer
2017-09-29 7:43 ` Alberto Luaces
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=874lrounzu.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--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).