All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harley Paterson <harley.paterson@hotmail.co.nz>
To: unlisted-recipients:; (no To-header on input)
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: False negative authentication with multiple accounts on a SSH-GIT server
Date: Wed, 20 Jan 2021 19:11:21 +0000	[thread overview]
Message-ID: <DB8P189MB10465B7C7C89FDCD8F8C6155F9A20@DB8P189MB1046.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <YAg/wV05JYbzOdck@coredump.intra.peff.net>

Repost: Accedentialy forgot to CC this to the mailing list.

>> Unfortunately, this leaks whether a repository exists.  If Company XYZ
>> has a repository for each of its clients, it then becomes easy to see if
>> Company XYZ is doing work for a particular client by trying to see if a
>> repository exists.
> 
> I wonder how many hosting providers are confident that the code involved
> in this isn't vulnerable to a timing attack.
>
> I would say "not very certain" in the case of GitHub. I don't recall any
> analysis of the timing ever having happened.



I have to agree with this... It's certainly a risk, but if an attacker has enough
information to guess the repository names/URLs without triggering a rate
limiter, they already have a pretty good idea who Company XYZ is likely working
for, and what on.

HP.


      reply	other threads:[~2021-01-20 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  6:17 False negative authentication with multiple accounts on a SSH-GIT server Harley Paterson
2021-01-19 18:22 ` M. Buecher
2021-01-19 23:11 ` brian m. carlson
2021-01-20 12:42   ` Ævar Arnfjörð Bjarmason
2021-01-20 14:35     ` Jeff King
2021-01-20 19:11       ` Harley Paterson [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=DB8P189MB10465B7C7C89FDCD8F8C6155F9A20@DB8P189MB1046.EURP189.PROD.OUTLOOK.COM \
    --to=harley.paterson@hotmail.co.nz \
    --cc=git@vger.kernel.org \
    /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.