From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: SSL problems on dovecot 2.1.7
Date: Thu, 09 May 2013 13:40:53 +0200 [thread overview]
Message-ID: <87li7oe5yy.fsf@dod.no> (raw)
In-Reply-To: <87mws4xwiz.fsf@topper.koldfront.dk>
>>>>> asjo@koldfront.dk (Adam Sjøgren):
>> - Peer's certificate issuer is unknown
>> - Peer's certificate is NOT trusted
> Shouldn't you fix those, according to your own logic?
Indeed I should. And I will do so when I figure out how.
But I don't think they are the real issue, because this article has that
same output and things seem to be working:
http://blog.josefsson.org/2009/04/16/cacert-and-gnutls/
Also, the "gnutls-cli" session I listed doesn't seem to stop when
encountering these snags, but continues down to the start of a cleartext
IMAP dialog.
From what (little) I know about CA-certifictes and signing, I don't
understand that I'm getting these messages...? Because the client
machine here is a debian testing machine, and the cacert.org root
certificate is already in /etc/ssl/certs/ on this machine.
When I tried to point the win7/emacs24/ma gnus/gnutls.dll combo at the
cacert.org root certificate, by adjusting gnutls-trustfiles:
(push "c:/ProgramFiles/emacs-24.3/etc/gnutls/cacert.org_root.crt" gnutls-trustfiles)
and then tried to open the imaps server with gnutls-log-level set to 5,
emacs 24 crashed on me.
When I try to open the imap server with gnutls-log-level set to 1, this
is what I get:
Opening connection to imap.mydomain.com via tls...
gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [1] (Emacs) setting the trustfile: c:/ProgramFiles/emacs-24.3/etc/gnutls/cacert.org_root.crt
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
(and there it just stops...)
With gnutls-log-level set to 2, this is what I get (which doesn't
enlighten me any more):
Opening connection to imap.mydomain.com via tls...
gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [2] (Emacs) allocating x509 credentials
gnutls.c: [2] (Emacs) using default verification flags
gnutls.c: [1] (Emacs) setting the trustfile: c:/ProgramFiles/emacs-24.3/etc/gnutls/cacert.org_root.crt
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [2] ASSERT: gnutls_constate.c:716
gnutls.c: [2] ASSERT: gnutls_buffers.c:955
gnutls.c: [2] ASSERT: gnutls_buffers.c:955
gnutls.c: [2] ASSERT: gnutls_buffers.c:955
gnutls.c: [2] ASSERT: signature.c:305
gnutls.c: [2] ASSERT: gnutls_buffers.c:955
gnutls.c: [2] ASSERT: gnutls_buffers.c:1037
gnutls.c: [2] ASSERT: gnutls_buffers.c:1146
gnutls.c: [2] ASSERT: session_ticket.c:684
gnutls.c: [2] ASSERT: gnutls_buffers.c:955
gnutls.c: [2] ASSERT: mpi.c:255
gnutls.c: [2] ASSERT: dn.c:1207
gnutls.c: [2] (Emacs) Deallocating x509 credentials
Quit
(Sigh! I feel a headache coming on...)
next prev parent reply other threads:[~2013-05-09 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:53 Steinar Bang
2013-05-09 10:14 ` Steinar Bang
2013-05-09 10:44 ` Adam Sjøgren
2013-05-09 11:40 ` Steinar Bang [this message]
2013-05-09 14:09 ` Bjørn Mork
2013-05-09 14:20 ` Steinar Bang
2013-05-09 18:24 ` James Cloos
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=87li7oe5yy.fsf@dod.no \
--to=sb@dod.no \
--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).