From: Robert Pluim <rpluim@gmail.com>
To: Prateek Sadhukhan <psadhukh@gmail.com>
Cc: ding@gnus.org
Subject: Re: gwene fingerprint changed
Date: Mon, 11 Jan 2021 18:56:01 +0100 [thread overview]
Message-ID: <87bldv4atq.fsf@gmail.com> (raw)
In-Reply-To: <87bldvri6l.fsf@gmail.com> (Prateek Sadhukhan's message of "Mon, 11 Jan 2021 13:58:34 +0530")
Prateek Sadhukhan <psadhukh@gmail.com> writes:
> Hi,
>
> I searched over the net but could not find anything related so here goes.
>
> I access my newsgroups using news.gwene.org. Offlate when I start gnus,
> I am getting a message that the fingerprint has changed and whether I want
> to still connect. It gives me an option whether I want to accept the
> certificate only for this session or permanently etc.
>
> Is this anything to worry about?
That means that the certificate that news.gwene.org has changed, as it
does every 3 months. If the message youʼre getting identifies the
certificate as belonging to gwene.org, then youʼre ok. If not, someone
might be trying to intercept traffic, or thereʼs a misconfigured https
proxy in the middle somewhere.
Robert
next prev parent reply other threads:[~2021-01-11 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 8:28 Prateek Sadhukhan
2021-01-11 17:56 ` Robert Pluim [this message]
2021-01-11 18:16 ` James Cloos
2021-01-12 8:12 ` Prateek Sadhukhan
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=87bldv4atq.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
--cc=psadhukh@gmail.com \
/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).