public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Fredrik Skolmli <fredrik@frsk•net>
To: Pierre Habouzit <madcoder@debian•org>
Cc: "Tom Preston-Werner" <tom@github•com>,
	"Santi Béjar" <santi@agolina•net>,
	git@vger•kernel.org, "Junio C Hamano" <gitster@pobox•com>
Subject: Re: [PATCH] add instructions on how to send patches to the mailing list with Gmail
Date: Sun, 2 Nov 2008 16:01:00 +0100	[thread overview]
Message-ID: <20081102150100.GF13242@frsk.net> (raw)
In-Reply-To: <20081102091006.GA4066@artemis>

On Sun, Nov 02, 2008 at 10:10:06AM +0100, Pierre Habouzit wrote:

> > > Warning: It is not secure.
> > 
> > It is true that the certificate is not verified, but since the patches
> > are destined for a public mailing list, this does not represent a
> > large problem.
> 
> What he means is that the password is cleartext ;)
> (I think)

The way I read and understand it, the issues arises if a MITM-attack takes
place.  If the client doesn't verify the certificate, an attacker can easily
get the username and password. 

So unless someone creates a separate gmail-account for submitting patches,
one should really trust the connection (ie not a public wlan), or verify the
certificate before transmitting the password.

-- 
Kind regards,
Fredrik Skolmli

      reply	other threads:[~2008-11-02 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01  7:28 [PATCH] add instructions on how to send patches to the mailing list with Gmail Tom Preston-Werner
2008-11-01 10:00 ` Santi Béjar
2008-11-01 20:40   ` Tom Preston-Werner
2008-11-02  9:10     ` Pierre Habouzit
2008-11-02 15:01       ` Fredrik Skolmli [this message]

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=20081102150100.GF13242@frsk.net \
    --to=fredrik@frsk$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=madcoder@debian$(echo .)org \
    --cc=santi@agolina$(echo .)net \
    --cc=tom@github$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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