# [git send-email] Less secure? 2 messages from 2016-04-24 to 2016-04-24. Participants: Neven Sajko, Eric Wong. Thread: https://gitlist.dev/t/42134 ## Neven Sajko, 2016-04-24 20:54 Subject: [git send-email] Less secure? Message-ID: URL: https://gitlist.dev/e/CAL%2BbK4Ms5WLSiWEPhXOX2i5T9UdcaZyD%2BkaTZpVsd0NZBts%2B7A%40mail.gmail.com ``` 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, 2016-04-24 22:36 Subject: Re: [git send-email] Less secure? Message-ID: <20160424223657.GA25762@dcvr.yhbt.net> URL: https://gitlist.dev/e/20160424223657.GA25762%40dcvr.yhbt.net In-Reply-To: ``` Neven Sajko wrote: > 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. ```