From: Jeff King <peff@peff.net>
To: jaseem abid <jaseemabid@gmail.com>
Cc: "Egor Ryabkov" <egor.ryabkov@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Carlos Martín Nieto" <cmn@elego.de>
Subject: Re: Git fetch/pull stopped working
Date: Fri, 11 May 2012 16:28:28 -0400 [thread overview]
Message-ID: <20120511202828.GA17750@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH-tXsCi+zL5hKAHROA0hVfvOr07o4cknS8jy9qngapwB77QnQ@mail.gmail.com>
On Sat, May 12, 2012 at 01:25:42AM +0530, jaseem abid wrote:
> On Sat, May 12, 2012 at 12:17 AM, Egor Ryabkov <egor.ryabkov@gmail.com> wrote:
> > Problem solved.
> >
> > Turns out that was a miscommunication on out side: the guy who setup
> > the keys on that box left, and his access to GH repo has been revoked.
> >
> > And GitHub returns "repo not found" rather than "you have no access
> > rights for this repository".
>
> I have seen a lot of github guys in this list. I hope they will fix
> this soon. I had this issue a long time back and now I'm understanding
> what exactly happened then :)
This is not a bug, but rather the intentional behavior. It is there to
prevent an information leak about the names of private repositories that
the user has. Git-daemon has the same behavior by default (though it has
a "friendly" mode if you are willing to leak that information for your
site).
-Peff
prev parent reply other threads:[~2012-05-11 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 22:45 Git fetch/pull stopped working Egor Ryabkov
2012-05-07 23:44 ` Junio C Hamano
2012-05-08 0:10 ` Carlos Martín Nieto
2012-05-08 20:18 ` Jeff King
2012-05-08 13:59 ` Egor Ryabkov
2012-05-08 19:37 ` Junio C Hamano
2012-05-08 20:08 ` Jeff King
2012-05-08 20:29 ` Carlos Martín Nieto
2012-05-08 21:28 ` Egor Ryabkov
2012-05-11 18:47 ` Egor Ryabkov
2012-05-11 19:55 ` jaseem abid
2012-05-11 20:28 ` Jeff King [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=20120511202828.GA17750@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cmn@elego.de \
--cc=egor.ryabkov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaseemabid@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).