From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: failed decryption on gwene group?
Date: Sun, 04 Aug 2013 07:36:39 -0400 [thread overview]
Message-ID: <87k3k1sn5k.fsf@lifelogs.com> (raw)
In-Reply-To: <8761vm42s2.fsf@ericabrahamsen.net>
On Sun, 04 Aug 2013 10:18:21 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>> 3.2.x is ABI-compatible, so we call it with the same function calls as
>> any other GnuTLS version. If 3.2.2 has bugs on Arch Linux, they seem
>> local because I haven't heard about this problem from anyone else. To
>> be sure, simply use the `gnutls-cli' utility. If it fails similarly,
>> the problem is not Emacs.
EA> Oh, whoops, maybe I actually am using the gnutls-cli utility... At
EA> least:
EA> starttls-use-gnutls --> t
EA> starttls-gnutls-program --> "gnutls-cli"
EA> Sorry, should have mentioned that in the first post. What does this
EA> mean, then? It's definitely not an emacs thing?
If you see the Diffie-Hellman messages, you're probably using the
built-in GnuTLS integration. I think the `starttls-use-gnutls' and such
are deprecated now.
Regardless, to know for sure if GnuTLS 3.2.2 has issues, call
its `gnutls-cli' from the command line against your server and port.
That will tell you unambiguously.
Ted
next prev parent reply other threads:[~2013-08-04 11:36 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 [this message]
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=87k3k1sn5k.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).