From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Date: Wed, 21 Oct 2020 01:17:33 +0100 [thread overview]
Message-ID: <49a25295917cd00dc5210e660e9e3f70@quintile.net> (raw)
Hi people,
I have had to renew my certificate for tls and am getting a strange error from imap4d
when trying to collect email from my iphone.
tls reports failed: factotum_rsa_open: no key matches proto=rsa service=tls role=client
Which does not make sense to me as my factotum has my new ras key in it:
key proto=rsa service=tls role=client owner=* size=2048 ek=10001 !dk=...
I have also put the same key in bootes factotum so it can be used for smtp outgoing mail, and rebooted to populate bootes factotum.
I have updated /sys/lib/tls/mail.pem, I even remembered to import the PEM
certificate (profile as apple calls it) into my phone.
What have I missed? why can't tlssrv find my key in my factotum?
-Steve
next reply other threads:[~2020-10-21 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 0:17 Steve Simon [this message]
2020-10-21 3:45 ` [9fans] Lucio De Re
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=49a25295917cd00dc5210e660e9e3f70@quintile.net \
--to=steve@quintile.net \
--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).