From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Magnus Henoch <magnus.henoch@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: TLS problem: gnutls-e-again
Date: Sat, 05 Mar 2016 17:04:52 +0100 [thread overview]
Message-ID: <m3fuw4lxln.fsf@gnus.org> (raw)
In-Reply-To: <CADrNgJU3u5C-wxzYNuGHHsut88MdDcXJm2M26Fb_FjUOrg4gww@mail.gmail.com> (Magnus Henoch's message of "Sat, 5 Mar 2016 13:37:29 +0000")
Magnus Henoch <magnus.henoch@gmail.com> writes:
> Connecting to xmpp.l.google.com:5222...
> gnutls.el: (err=[gnutls-e-again] Resource temporarily unavailable, try again.)
> boot: (:priority NORMAL :hostname gmail.com :loglevel 0 :min-prime-bits nil
> :trustfiles (/opt/local/share/curl/curl-ca-bundle.crt) :crlfiles nil :keylist nil
> :verify-flags nil :verify-error (:hostname . t) :callbacks nil)
> magnus.henoch@gmail.com: connection lost: ‘STARTTLS negotiation failed:
> GnuTLS error: #<process jabber>, gnutls-e-again’
>
> Unfortunately, my attempts at creating a self-contained test case have failed
> so far... What jabber.el does, is that it opens an asynchronous network
> connection (:nowait t), performs XMPP feature negotiation in cleartext, and
> then attempts to do STARTTLS using gnutls-negotiate.
On non-blocking sockets, gnutls-boot no longer waits for the connection
to complete. But if you try to talk to it before it's completed, it
should block the communication until that has happened, so what function
is it that gets that return value?
Anyway, there should be a way to specify that you want TLS negotiation
to complete even on non-blocking sockets, so I've now added this to the
trunk. It should probably fix your use case, too.
Could you try updating from git and running jabberd again?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-03-05 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 13:37 TLS problem: gnutls-e-again Magnus Henoch
2016-03-05 16:04 ` Lars Magne Ingebrigtsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-05 19:05 Magnus Henoch
2016-03-06 9:20 ` Lars Magne Ingebrigtsen
2016-05-31 18:22 ` Ted Zlatanov
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=m3fuw4lxln.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=magnus.henoch@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.