From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 86D0EABA for ; Mon, 13 Jul 2015 08:32:32 +0000 (UTC) Received: from mail.emea.novell.com (mail.emea.novell.com [130.57.118.101]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CFD33A7 for ; Mon, 13 Jul 2015 08:32:31 +0000 (UTC) Date: Mon, 13 Jul 2015 10:32:06 +0200 (CEST) From: Jiri Kosina To: James Bottomley In-Reply-To: <1436599873.2243.10.camel@HansenPartnership.com> Message-ID: References: <20150710143832.GU23515@io.lakedaemon.net> <20150710162328.GB12009@thunk.org> <1436599873.2243.10.camel@HansenPartnership.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Josh Boyer , ksummit-discuss@lists.linuxfoundation.org, Jason Cooper Subject: Re: [Ksummit-discuss] [CORE TOPIC] dev/maintainer workflow security List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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