unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: 31313@debbugs.gnu.org
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#31313: 26.1; gnutls.c: [0] (Emacs) Received alert: Handshake failed
Date: Sun, 29 Apr 2018 17:01:17 -0400	[thread overview]
Message-ID: <87a7tlpw0y.fsf@gmail.com> (raw)
In-Reply-To: <CAHZoxq-DD5CaDUUZSmQgvd5YyUAxkMtpZ75fCyAUyFcdcYr0Tg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 82 bytes --]

[forwarding to list, please use "Reply All" to keep 31313@debbugs.gnu.org on Cc]


[-- Attachment #2: Type: message/rfc822, Size: 562 bytes --]

From: Eric Hanchrow <eric.hanchrow@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Subject: Re: bug#31313: 26.1; gnutls.c: [0] (Emacs) Received alert: Handshake failed
Date: Sun, 29 Apr 2018 20:45:27 +0000
Message-ID: <CAHZoxq_SrMuem99tGrwmdLnnC+vv-Os_HKDSnCFBJ2NLdcZvdA@mail.gmail.com>

Is there any more information that I could supply that would help in
debugging?

[-- Attachment #3: Type: text/plain, Size: 54 bytes --]



I think setting gnutls-log-level could be helpful.


  parent reply	other threads:[~2018-04-29 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 19:59 bug#31313: 26.1; gnutls.c: [0] (Emacs) Received alert: Handshake failed Eric Hanchrow
2018-04-29 20:38 ` Noam Postavsky
2018-04-29 21:01 ` Noam Postavsky [this message]
2018-04-29 22:32 ` Noam Postavsky
2018-04-30  2:34 ` Eli Zaretskii
2018-04-30  5:26   ` Eli Zaretskii
2018-05-02  2:47     ` Eric Hanchrow
2018-05-02 14:53       ` Eli Zaretskii
2018-05-03  3:24         ` Eric Hanchrow
2018-05-03 17:43           ` Eli Zaretskii
2018-05-04 22:49             ` Eric Hanchrow
2018-05-05  6:39               ` Eli Zaretskii
     [not found]   ` <CAHZoxq-_BUSvfaEbysKnvFN2tFpU+HhhFyR6G73Z6iKDXtOuTQ@mail.gmail.com>
2018-04-30 14:26     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7tlpw0y.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31313@debbugs.gnu.org \
    --cc=eric.hanchrow@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).