From: Steven Stallion <sstallion@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Gmail vs upas
Date: Thu, 28 Nov 2019 11:13:10 -0600 [thread overview]
Message-ID: <CAGGHmKHKUR45qqZ7H9W6u+X0cFWSc7C7LjFncnzhZ3Ta-L9iZg@mail.gmail.com> (raw)
In-Reply-To: <8e0c5482-c573-4089-9271-05d34ad845a4@www.fastmail.com>
Thanks guys. I suspect I'm about to regret my lack of time mucking
about with tls on plan9:
% upas/fs -f /imaps/imap.gmail.com/sstallion@gmail.com
upas/fs: opening /imaps/imap.gmail.com/sstallion@gmail.com:
imap.gmail.com/imaps:tlsClient: tls: local invalid x509/rsa
certificate
% cat /sys/lib/tls/mail
x509 sha1=f0d1545c78815ee782d479b48841f24afa217c35
To verify, I pulled the server fingerprint using OpenSSL:
% openssl s_client -connect imap.gmail.com:993 </dev/null 2>/dev/null
| openssl x509 -fingerprint -noout -in /dev/stdin
SHA1 Fingerprint=F0:D1:54:5C:78:81:5E:E7:82:D4:79:B4:88:41:F2:4A:FA:21:7C:35
Any other ideas?
Steve
On Thu, Nov 28, 2019 at 10:01 AM David du Colombier <0intro@gmail.com> wrote:
>
> The TLS implementation on Plan 9 doesn't verify X.509 certificate chain,
> so the certificate bundle isn't useful. It's only used by Go programs.
>
> However, you need to add the server certificate fingerprint to /sys/lib/tls/mail,
> as Steve Simon said.
>
> --
> David du Colombier
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Te20476748ab5e4ba-Mde55e25da902ed343e0215c8
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2019-11-28 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:39 Steven Stallion
2019-11-28 15:55 ` [9fans] " Steve Simon
2019-11-28 16:00 ` David du Colombier
2019-11-28 17:13 ` Steven Stallion [this message]
2019-11-28 17:37 ` kvik
2019-11-28 17:44 ` Steven Stallion
2019-11-28 18:07 ` kvik
2019-11-28 18:59 ` David du Colombier
2019-11-28 20:28 ` Steven Stallion
2019-12-02 23:27 ` ori
2019-12-03 10:52 ` Richard Miller
2019-12-04 20:50 ` ori
2019-12-04 23:02 ` Richard Miller
2019-12-03 13:54 ` Anthony Martin
2019-11-28 17:33 ` kvik
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=CAGGHmKHKUR45qqZ7H9W6u+X0cFWSc7C7LjFncnzhZ3Ta-L9iZg@mail.gmail.com \
--to=sstallion@gmail.com \
--cc=9fans@9fans.net \
/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).