threads / discuss / 42134

[git send-email] Less secure?

Subject: [git send-email] Less secure?

## tl;dr

2 messages between Apr 24, 2016 and Apr 24, 2016.

replies: 1people: 2as markdown or json

Neven Sajko· Apr 24, 2016, 20:54 UTC · lore

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?

Neven
Eric Wong· Apr 24, 2016, 22:36 UTC · re: Neven Sajko · lore

Re: [git send-email] Less secure?

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.

← back to recent threads