git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: webmaster@kernel.org, Junio C Hamano <gitster@pobox.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Another git repo at kernel.org?
Date: Mon, 22 May 2017 21:43:26 +0200	[thread overview]
Message-ID: <CACBZZX7HYU1USdcX_=CDFiMDtdaySSjd0zv-Bb1Z9-nHxk8UvQ@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kYirjV0eQgB_ng-64HSPN_7njUMjnoNBkmWnx-rinsemQ@mail.gmail.com>

On Mon, May 22, 2017 at 8:34 PM, Stefan Beller <sbeller@google.com> wrote:
> The Git community considers using submodules for some parts of the
> code (a third party lib, SHA1DC, computing SHA1s that warn about
> potential attachs, see shattered.io) [1].
>
> We are also concerned about single point of failure there, so a repo
> at kernel.org
> mirroring the potential submodule[2] would be great.
>
> I cc'd the git mailing list as we may want to have further discussion who
> shall have access to the new repo.
>
> [1] https://public-inbox.org/git/20170520115429.12289-1-avarab@gmail.com/
> [2] https://github.com/cr-marcstevens/sha1collisiondetection

The access problem could be solved by none of us having access to the
repo, if the git.kernel.org admins are willing to set up a mirror of
the github repo, a cronjob running git-fetch with the appropriate
parameters to just fetch the master (or everything, but only master is
needed). Updating such a mirror with a daily cronjob would be more
than enough.

Less seriously but worth pointing out: It could also be solved by just
setting the user:password to foo:bar and publishing that in the
description & setting the repo to non-fast-forward only. This will
only be used by the git.git repo, which'll point at a specific sha1 in
its history, wouldn't that be a nice demo of the whole "give the repo
to your worst enemy but as long as you have the sha ... " parable
Linus posted on-list back in the day... :)

  reply	other threads:[~2017-05-22 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 18:34 Another git repo at kernel.org? Stefan Beller
2017-05-22 19:43 ` Ævar Arnfjörð Bjarmason [this message]
2017-05-23 15:13   ` Theodore Ts'o
2017-05-23 23:32     ` Junio C Hamano
2017-05-24  0:15       ` Stefan Beller

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACBZZX7HYU1USdcX_=CDFiMDtdaySSjd0zv-Bb1Z9-nHxk8UvQ@mail.gmail.com' \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sbeller@google.com \
    --cc=webmaster@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).