From: Jiri Kosina <jkosina@suse.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
ksummit-discuss@lists.linuxfoundation.org,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] dev/maintainer workflow security
Date: Mon, 13 Jul 2015 10:32:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1507131027000.7522@pobox.suse.cz> (raw)
In-Reply-To: <1436599873.2243.10.camel@HansenPartnership.com>
On Sat, 11 Jul 2015, James Bottomley wrote:
> > - personal security (keep commit credentials secure from theft)
>
> This second one is a bit of a red herring: Assuming you did steal my
> credentials, how would you use them without being detected?
If the credentials can be used both to push to ra.kernel.org and to access
your "local" copy of the GIT repo (on your notebook / desktop / storage),
I can just push the malicious commit (*) to both repos and you might not
notice immediately (because you wouldn't get non-fast-forward hint from
git).
(*) or just ammend some already existing one so that you wouldn't
notice extra commit when preparing pull request
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2015-07-13 8:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 14:38 Jason Cooper
2015-07-10 15:50 ` Josh Boyer
2015-07-10 16:23 ` Theodore Ts'o
2015-07-10 19:45 ` Steven Rostedt
2015-07-10 20:34 ` Olof Johansson
2015-07-11 1:19 ` Jason Cooper
2015-07-10 22:08 ` Kees Cook
2015-07-11 1:48 ` Jason Cooper
2015-07-11 7:31 ` James Bottomley
2015-07-11 16:02 ` Jason Cooper
2015-07-11 16:38 ` Theodore Ts'o
2015-07-13 23:15 ` Kees Cook
2015-07-13 8:32 ` Jiri Kosina [this message]
2015-07-13 14:07 ` Konstantin Ryabitsev
2015-07-13 15:39 ` James Bottomley
2015-07-13 16:02 ` Mark Brown
2015-07-13 16:05 ` Konstantin Ryabitsev
2015-07-13 16:14 ` James Bottomley
2015-07-13 18:22 ` Theodore Ts'o
2015-07-13 16:46 ` Geert Uytterhoeven
2015-07-13 17:12 ` josh
2015-07-13 19:37 ` Jiri Kosina
2015-07-15 18:42 ` Steven Rostedt
2015-07-13 23:25 ` Kees Cook
2015-07-14 7:47 ` James Bottomley
2015-07-14 16:20 ` Kees Cook
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=alpine.LNX.2.00.1507131027000.7522@pobox.suse.cz \
--to=jkosina@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jason@lakedaemon.net \
--cc=jwboyer@fedoraproject.org \
--cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox