List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Mon, Jun 4, 2012 at 4:41 PM, Brian Harring <ferringb@...> wrote:
> If that doesn't answer your question/concerns, be more explicit
How about a scenario:
1. Gentoo dev commits a bunch of stuff to the tree. Top of tree is signed.
2. Hacker commits something to the tree. Top of tree is not signed.
No need for preimage attacks or whatever on sha1 - they just log into
the server and do a git commit or whatever right into the tree.
3. Gentoo dev commits a bunch of stuff to the tree. Top of tree is signed.
4. Rsync mirror update happens - top of tree is signed, so update
If you go back and look at the tree you see a bunch of signed and
unsigned commits. How do you easily detect how the unsigned ones got
there (via a dev with a merge commit, or via other means)? Either way
they'll be parents of merge commits - since merge commits have two
parents - the pre-commit gentoo-x86 tree, and the incoming commits.
Andreas - I'm pretty sure a merge commit still includes a tree.