Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: failed decryption on gwene group?
Date: Mon, 05 Aug 2013 10:54:33 +0800	[thread overview]
Message-ID: <8761vkzw2e.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3pptskhga.fsf@stories.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> $ gnutls-cli -s -p 563 news.gmane.org
>> Processed 157 CA certificate(s).
>> Resolving 'news.gmane.org'...
>> Connecting to '80.91.229.13:563'...
>>
>> - Simple Client Mode:
>>
>> Then it waits for a prompt. I'm not quite sure that's conclusive,
>> though: I'm able to open most groups through this server, right now it
>> only appears to be two or three gwene groups in particular that fail to
>> decrypt properly...
>
> No, at that point it hasn't started doing anything encryption-ey, so
> it's not conclusive.
>
> Port 563 isn't doing STARTTLS, but straight TLS.  So drop the -s and see
> what it says.

Without the "-s" option I get an untrusted certificate error:

$ gnutls-cli -p 563 news.gmane.org
Processed 157 CA certificate(s).
Resolving 'news.gmane.org'...
Connecting to '80.91.229.13:563'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
 - subject `C=NO,ST=Some-State,O=Gmane,CN=news.gmane.org', issuer `C=NO,ST=Some-State,O=Gmane,CN=news.gmane.org', RSA key 1024 bits, signed using RSA-SHA1, activated `2011-12-04 06:38:42 UTC', expires `2014-12-03 06:38:42 UTC', SHA-1 fingerprint `c0ec2f016cff4a43c1a7c7834b480b3ac54e90f9'
	Public Key Id:
		d21a01452b5a9b06106946930e64717869ff7ae0
	Public key's random art:
		+--[ RSA 1024]----+
		|=O+.ooo          |
		|+*o+ . .         |
		|= + + o          |
		| . + = o         |
		|  . + + S        |
		|   . . =         |
		|    . +          |
		|     E .         |
		|      .          |
		+-----------------+

- Status: The certificate is NOT trusted. The certificate issuer is unknown. 
*** Verifying server certificate failed...
*** Fatal error: Error in the certificate.
*** Handshake has failed
GnuTLS error: Error in the certificate.




  reply	other threads:[~2013-08-05  2:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-03 13:02 Eric Abrahamsen
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 [this message]
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=8761vkzw2e.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).