incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de.INVALID>
Subject Re: [discuss] Apache OpenWhisk Incubator Proposal
Date Fri, 14 Oct 2016 15:00:47 GMT
PS we could Force the use of the new -S git Option and verify it with the Pub key stored at
the asf.
Needs a few Experiments but might work.

Lg,
Strub
--------------------------------------------
On Fri, 14/10/16, Mark Struberg <struberg@yahoo.de.INVALID> wrote:

 Subject: Re: [discuss] Apache OpenWhisk Incubator Proposal
 To: "general@incubator.apache.org" <general@incubator.apache.org>
 Date: Friday, 14 October, 2016, 16:51
 
 
 
 > Git repositories are effectively
 cryptographically-signed (weak/strong,
 >
 immaterial to this discussion), so a readonly mirror on ASF
 hardware is
 > equivalent to a read/write
 repository living on GitHub.
 
 
 Allow me to disagree. The
 hashes are cryptographically strong. But it's only sha1
 hashes and no real signing. The sha1 hashes only the things
 you tell him. Try to do  git config user.name "Foo
 Baz" and you are Mr Foo Baz from now on. If you push
 this to github then your own authentity is lost for the
 commit. I could e.g. also commit something with your name
 and your email ;) We still hope that this would get catched
 if the commit gets mirrored to the list...
 
 The -s option is btw something
 completely different.
 
 
 But Felix is right, it's a foundation wide
 question and we should continue this discussion on the infra
 lists.
 
 
 txs
 and LieGrue,
 strub
 
 
 > On Friday, 14 October 2016, 16:26, Greg
 Stein <gstein@gmail.com>
 wrote:
 > > On Fri, Oct 14, 2016 at
 8:37 AM, Mark Struberg <struberg@yahoo.de.invalid>
 > wrote:
 > 
 >>  The problem with github is that we
 (ASF) cannot give any guarantees if the
 >>  main stuff doesn't originate
 from our own hardware.
 >> 
 > 
 > Git repositories are
 effectively cryptographically-signed (weak/strong,
 > immaterial to this discussion), so a
 readonly mirror on ASF hardware is
 >
 equivalent to a read/write repository living on GitHub.
 > 
 > 
 >>  Not whether the ticket system
 doesn't loose all tickets (didn't 
 > that
 >>  happen in
 the past?) nor whether really only IP clean stuff got
 committed.
 >> 
 >
 
 > All commits, issues, PRs, etc
 will/must be sent to ASF mailing lists for
 > archival. Some projects do/have used third
 party systems. The ASF doesn't
 >
 mind, as long as we capture that work into our archives.
 > 
 > 
 >>  You e.g. have no clue if someone
 else uses your email and name in a commit
 >>  and pushes it.
 >>  Everyone else can create a commit
 with your email and name in GIT, there
 >>  is no check. And when pulling in
 changes, a faked one might get piggy
 >>  packed and introduce a backdoor. I
 know this might be close to paranoid but
 >>  it is theoretically possible.
 >> 
 > 
 > We require that anybody committing to a
 GitHub repository authenticates
 > with
 BOTH: GitHub, and the ASF. No commits without that
 multiple
 > authentication.
 > (this is based on our current experiments
 with Whimsy and Traffic Server;
 > same
 rules would apply to this podling)
 > 
 > 
 >>  The workflow
 with git hosted @ASF is btw pretty much exactly the same
 for
 >>  committers. And a PR
 integration does exist as well. So I don't see 
 > what
 >>  you
 miss?
 >> 
 > 
 > ASF repositories mirrored to GitHub cannot
 merge/close PRs. They cannot
 > manage
 issues. They cannot use labels. There is a large amount of
 GitHub
 > tooling that is not available to
 ASF-based projects/workflows. The Github
 > repository is a simple mirror. ...
 OpenWhisk proposes to continue using
 >
 their GitHub workflows and tooling during incubation. At the
 *end* of
 > incubation, the Foundation
 will allow them to stay (as we'll be allowing
 > other projects to similarly change their
 focal point of development), or
 > they
 will be required to shift their focal point to ASF-based
 workflows (as
 > we require today).
 > 
 > Cheers,
 > 
 > -g
 > 
 
 ---------------------------------------------------------------------
 To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
 For additional commands, e-mail: general-help@incubator.apache.org
 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message