All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Drew DeVault <sir@cmpwn.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: clarify SMTP encryption settings
Date: Sun, 11 Apr 2021 12:48:40 +0700	[thread overview]
Message-ID: <f347c0bf-b08e-34d7-e1ae-796a3e619b8c@gmail.com> (raw)
In-Reply-To: <xmqqlf9rklkb.fsf@gitster.g>

On 10/04/21 07.52, Junio C Hamano wrote:
> Isn't SMTPS (running SMTP over SSL encrypted connection) the one
> that was once deprecated until it got resurrected)?
> 
> STARTTLS is not all that SMTP specific---POP and IMAP can also start
> in cleartext and upgrade with STARTTLS the same way, no?

Wikipedia entry on Opportunistic TLS [1] said that STARTTLS is not specific
to SMTP, but also to various protocols:
> The STARTTLS command for IMAP and POP3 is defined in RFC 2595, for SMTP in RFC 3207, for XMPP in RFC 6120 and for NNTP in RFC 4642. For IRC, the IRCv3 Working Group has defined the STARTTLS extension. FTP uses the command "AUTH TLS" defined in RFC 4217 and LDAP defines a protocol extension OID in RFC 2830. HTTP uses upgrade header. 

[1]: https://en.wikipedia.org/wiki/Opportunistic_TLS

-- 
An old man doll... just what I always wanted! - Clara

  parent reply	other threads:[~2021-04-11  5:51 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
2021-04-11  5:48   ` Bagas Sanjaya [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f347c0bf-b08e-34d7-e1ae-796a3e619b8c@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.