Received: by 10.223.176.5 with SMTP id f5csp997999wra; Tue, 30 Jan 2018 23:21:20 -0800 (PST) X-Google-Smtp-Source: AH8x225k2LtS1oThgs2AZSMJtFVaC/my63r9gNBMVoaioCCnbdW3IumekpEQytnp+13gGTfdHg75 X-Received: by 10.99.114.93 with SMTP id c29mr26274670pgn.419.1517383279884; Tue, 30 Jan 2018 23:21:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517383279; cv=none; d=google.com; s=arc-20160816; b=r/1MJk/hTVQO79xqMP82aeYGRqocsSQj/t4Qmj4aCZj30+M5N2gw/Udb/jlHMHyzNf 268CR39hQa96Vx0Jt3H71uAGK0tNezudv0FHGvcpYdDXvMUpzRmHdP9Abb9i7+e0VhQH S6jLIYx8Bkn4PdsROCPXlGafWVb9OQyd/6VvIJ4MYVdQ/tR1B7l9N7SliKmE9JL1hQ6n fk0fMrSgGiRFYNAJ/ZCOO0BGiNLobbdNpd4kgT0ahFAORrrT0+ttsGqPXYq4tgogPozu 1jFtQOhzyDvsZBJdZFMuBt8KUp7FGXIcjPG8OOnR5j9/3q5Q5AZPe2H/1zGlNPL50z+1 mwxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :organization:in-reply-to:subject:cc:to:from :arc-authentication-results; bh=uX/nwiioTDYO8Hk8aaazxhm2XOtc9TpJqAyFl0qZ4KU=; b=dBYbWwdeMJ2egkighHV6vl5VHWikpX07RR7bPbvU8v9i6UujmZmuY9lguDGmXE1Nn8 hAiwAfpNsg/8j8Jit9msERY8Oln5tsh5OI8fEdB4fLnTQFSHFFpvIxP+215yVAZJ8+qs aQnq5EZqGeFbkct1QpFBpMyveJIZIpauN39HrxutOEPlbQRlXKKL3Tt2OLpk/3vpNnVu pRPKyHcah1gt2mJdImFw1ewIm0toM0eGvbO9/WbsSCg6O2p99G2hWCoCaG1SHKR8a8yU 9Atd1qaqiSLWchsBSClt6rcPKvelnipgGdhOwS1SY229jED/sE2VwmHPzq7cKFmjsBW2 IMRA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o7-v6si1401302pll.114.2018.01.30.23.21.05; Tue, 30 Jan 2018 23:21:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752401AbeAaHSQ (ORCPT + 99 others); Wed, 31 Jan 2018 02:18:16 -0500 Received: from mga02.intel.com ([134.134.136.20]:14550 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750983AbeAaHSP (ORCPT ); Wed, 31 Jan 2018 02:18:15 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2018 23:18:14 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,438,1511856000"; d="scan'208";a="26861716" Received: from kumarvi1-mobl1.ger.corp.intel.com (HELO localhost) ([10.252.51.113]) by fmsmga001.fm.intel.com with ESMTP; 30 Jan 2018 23:18:12 -0800 From: Jani Nikula To: Konstantin Ryabitsev , corbet@lwn.net Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] Documentation/process: kernel maintainer PGP guide In-Reply-To: <20180130184917.GA32095@gmail.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20180130184917.GA32095@gmail.com> Date: Wed, 31 Jan 2018 09:18:11 +0200 Message-ID: <87bmhajy30.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Jan 2018, Konstantin Ryabitsev wrote: > This guide is an adapted version of the more general "Protecting Code > Integrity" guide written and maintained by The Linux Foundation IT for > use with open-source projects. It provides the oft-lacking guidance on > the following topics: > > - how to properly protect one's PGP keys to minimize the risks of them > being stolen and used maliciously to impersonate a kernel developer > - how to configure Git to properly use GnuPG > - when and how to use PGP with Git > - how to verify fellow Linux Kernel developer identities > > I believe this document should live with the rest of the documentation > describing proper processes one should follow when participating in > kernel development. Placing it in a wiki on some place like kernel.org > would be insufficient for a number of reasons -- primarily, because only > a relatively small subset of maintainers have accounts on kernel.org, > but also because even those who do rarely remember that such wiki > exists. Keeping it with the rest of in-kernel docs should hopefully give > it more visibility, but also help keep it up-to-date as tools and > processes evolve. FWIW, agreed on having this with the kernel documentation. I can't say I reviewed it, but glancing through I didn't spot any errors either. Lots of good stuff. Just one nit, I think it would be better to move the Maintainer: bit from the end near the top as a reStructuredText field list. See 'git grep :Author:' under Documentation for examples. Could even add a MAINTAINERS entry to improve your chances of being Cc'd on changes. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center