From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] "Insecure" icon in gmail
Date: Thu, 16 May 2024 12:27:03 +0200 [thread overview]
Message-ID: <BA7D74F622D773A3C9F1903706DE303B@felloff.net> (raw)
In-Reply-To: <4C1B6B746BF77B2F88319BBFCBFEB08C@driusan.net>
> 3. Would it make sense to add a flag to use startls but not validate certificates for upas/smtp?
yes. i think that makes sense. Maybe "-C" as in disable thumbprint/certificate check?
--
cinap
next prev parent reply other threads:[~2024-05-16 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 21:21 Dave MacFarlane
2024-05-15 21:28 ` Stanley Lieber
2024-05-16 1:23 ` [9front] " Anthony Martin
2024-05-16 1:39 ` Kurt H Maier
2024-05-16 2:06 ` Dave MacFarlane
2024-05-16 2:51 ` Anthony Martin
2024-05-16 10:27 ` cinap_lenrek [this message]
2024-05-16 11:01 ` [9front] " sirjofri
2024-05-18 18:45 ` ori
2024-05-18 20:12 ` hiro
2024-05-18 22:27 ` sirjofri
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=BA7D74F622D773A3C9F1903706DE303B@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).