From: Junio C Hamano <gitster@pobox.com>
To: "Drew DeVault" <sir@cmpwn.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] send-email: clarify SMTP encryption settings
Date: Fri, 09 Apr 2021 18:09:31 -0700 [thread overview]
Message-ID: <xmqqczv3kks4.fsf@gitster.g> (raw)
In-Reply-To: <CAJMW3X0O81L.8TNFDEFUNML1@taiga> (Drew DeVault's message of "Fri, 09 Apr 2021 20:57:30 -0400")
"Drew DeVault" <sir@cmpwn.com> writes:
>> I couldn't find a justification for our log message to call
>> STARTTLS-style explicit TLS "deprecated". When you send an updated
>> version, please give a reference.
>
> The main concern with STARTTLS is downgrade attacks. I'll note this in
> the commit message for v2.
> ...
> If I may propose a bold alternative: what I added as "ssl/tls", i.e.
> "modern" SSL, should be "yes", no encryption should be "no", and if you
> specifically need starttls: "starttls".
Well, "is starttls deprecated" given to search engine gives me
SMTPS (implicit SSL) has been deprecated/obsolete since
SMTP+STARTTLS (explicit SSL) was defined in RFC2487.
as the "featured snippet", and there are debates like "SMTPS has
been deprecated since forever (late 90's or thereabouts)"
https://news.ycombinator.com/item?id=10556797
I strongly prefer to keep our documentation out of that mess by not
taking sides. To me, both are valid options to make the world safer
over cleartext, and we won't have to make recommendations when both
are available.
Thanks.
next prev parent reply other threads:[~2021-04-10 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 21:18 [PATCH] send-email: clarify SMTP encryption settings Drew DeVault
2021-04-09 22:04 ` Eric Sunshine
2021-04-09 23:14 ` Georgios Kontaxis
2021-04-09 23:39 ` Drew DeVault
2021-04-10 0:52 ` Junio C Hamano
2021-04-10 0:57 ` Drew DeVault
2021-04-10 1:09 ` Junio C Hamano [this message]
2021-04-11 5:48 ` Bagas Sanjaya
2021-04-10 1:39 ` brian m. carlson
2021-04-10 1:42 ` Drew DeVault
2021-04-10 16:43 ` Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqczv3kks4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sir@cmpwn.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://80x24.org/mirrors/git.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).