From: Junio C Hamano <gitster@pobox.com>
To: sndanailov@wired4ever.net
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: git-send-email: difference between ssl and tls smtp-encryption
Date: Mon, 10 Oct 2022 12:11:47 -0700 [thread overview]
Message-ID: <xmqqy1tn1ojw.fsf@gitster.g> (raw)
In-Reply-To: <20221010172859.13832-1-sndanailov@wired4ever.net> (sndanailov@wired4ever.net's message of "Mon, 10 Oct 2022 19:28:59 +0200")
sndanailov@wired4ever.net writes:
> From: Sotir Danailov <sndanailov@wired4ever.net>
>
> New explanation for the difference between these values.
> It's hard to understand what they do based only on the names.
True. The names we use, 'ssl' and 'tls', emerged historically and
are not the best ones in retrospect.
It may also help understanding if you mentioned STARTTLS somewhere
in the description of "explicit" one, as (some) readers may be more
familiar with that term than "implicit vs explicit".
> --smtp-encryption=<encryption>::
> - Specify the encryption to use, either 'ssl' or 'tls'. Any other
> - value reverts to plain SMTP. Default is the value of
> + Specify the encryption to use, either 'ssl' or 'tls'. Any other
> + value reverts to plain SMTP. The difference between the two for Git is
> + that 'ssl' uses implicit encryption and defaults to port 465, 'tls'
> + uses explicit encryption and defaults to port 25. Other ports might be
> + used by the SMTP server. Default is the value of
> `sendemail.smtpEncryption`.
>
> --smtp-domain=<FQDN>::
next prev parent reply other threads:[~2022-10-10 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 17:28 [PATCH] docs: git-send-email: difference between ssl and tls smtp-encryption sndanailov
2022-10-10 19:11 ` Junio C Hamano [this message]
2022-10-10 19:44 ` brian m. carlson
2022-10-10 23:56 ` Junio C Hamano
2022-10-11 0:20 ` Aaron Schrab
2022-10-11 14:06 ` Philip Oakley
2022-10-11 15:49 ` Sotir Danailov
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=xmqqy1tn1ojw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sndanailov@wired4ever.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