Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: failed decryption on gwene group?
Date: Sat, 03 Aug 2013 21:02:19 +0800	[thread overview]
Message-ID: <87bo5f3p2c.fsf@ericabrahamsen.net> (raw)

I sort of doubt this is a gnus problem, but I've seen related
discussions here, and I don't know where else to post, so...

I'm subscribed to the Hacker News feed via gwene, as
gwene.com.ycombinator.news. Recently, opening the group has failed like
so:

gnutls.c: [1] Discarded message[136] due to invalid decryption
gnutls.c: [0] (Emacs) fatal error: Decryption has failed.
gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data
gnutls.c: [1] Discarded message[33] due to invalid decryption
gnutls.c: [0] (Emacs) fatal error: Decryption has failed.
apply: Server closed connection

I'm on archlinux, running emacs-version "24.3.1" and the arch gnutls
package is at version 3.2.3-1.

For a while I had gnutls-min-prime-bits set to 1024 (something I found
from this list), which got rid of the warning on the third line. Then
arch's gnutls package was updated, and I started getting these
decryption errors, I removed that customization, thinking it was the
source of the problem, but now it appears it isn't -- I'm not getting
this error for any group but the ycombinator one, presumably because
it's got this one broken message.

I've catchup'd articles in this group several times, and over various
restarts and refreshes the unread count in the *Group* buffer continues
to be updated, but I can never enter the group.

Is something actually broken in this group's message data? Or maybe
there's something I can change in my setup to fix it? Any hints very
welcome...

Eric




             reply	other threads:[~2013-08-03 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-03 13:02 Eric Abrahamsen [this message]
2013-08-03 13:11 ` Lars Magne Ingebrigtsen
2013-08-03 14:58   ` Ted Zlatanov
2013-08-04  2:18     ` Eric Abrahamsen
2013-08-04 11:36       ` Ted Zlatanov
2013-08-04 15:02         ` Eric Abrahamsen
2013-08-05  2:19           ` Lars Magne Ingebrigtsen
2013-08-05  2:54             ` Eric Abrahamsen
2013-08-05  7:41               ` Julien Danjou
2013-08-05  8:36                 ` Eric Abrahamsen
2013-08-05 13:11                   ` Adam Sjøgren
2013-08-06  2:51                     ` Eric Abrahamsen
2013-08-06  3:10                       ` Eric Abrahamsen
2013-08-06  3:35                         ` Eric Abrahamsen
2013-08-08  6:25                           ` Eric Abrahamsen
2013-08-03 13:51 ` Wolfgang Jenkner

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=87bo5f3p2c.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).