git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [git send-email] Less secure?

From
EWEric Wong <normalperson@yhbt.net>
Date
Apr 24, 2016, 22:36 UTC
Message-ID
<20160424223657.GA25762@dcvr.yhbt.net>
In-Reply-To
<CAL+bK4Ms5WLSiWEPhXOX2i5T9UdcaZyD+kaTZpVsd0NZBts+7A@mail.gmail.com>
Neven Sajko <nsajko@gmail.com> wrote:
Show 6 quoted lines
> Gmail by default doesn't allow usage through send-email.
> They say that send-email is "less secure" and that enabling it
> makes it easier to break into my account.
> 
> Is send-email really less secure than the Gmail web browser
> interface?

Like any email client, git send-email is only as secure as your own practices. It can use git's native git-credential system for handling passwords.

According to the following post from Javier, you will need an extra password if you have two-factor auth enabled with Gmail:

http://mid.gmane.org/CALZVapn9KjXCpO+zaYuB6RSnG747u4a7e_m_HDg+uH-uz8UhQg@mail.gmail.com

Additionally, since (AFAIK) you can still get multiple Gmail accounts, there's no reason you need to use your primary email account (that might be tied to your private/personal life) for sending patches to a public mailing list.

Disclaimer: I have little experience with Gmail myself and do
not endorse Google (or any corporation).  I just care deeply
about the continued existence of vendor-neutral messaging.
Previous: Neven Sajko
Message 2 of 2 in “[git send-email] Less secure?”
  1. Neven SajkoApr 24, 2016
  2. Eric WongApr 24, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.