Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754571AbeAGTkv (ORCPT + 1 other); Sun, 7 Jan 2018 14:40:51 -0500 Received: from mail-it0-f54.google.com ([209.85.214.54]:43858 "EHLO mail-it0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754356AbeAGTku (ORCPT ); Sun, 7 Jan 2018 14:40:50 -0500 X-Google-Smtp-Source: ACJfBos5JWVuLMdZbgLkFQGvoHEFmlY/NN78UfLNe9SNpIYThad7p8NPqppTHy6CRzA2qNXQCillNHvjcNE0otQfD2I= MIME-Version: 1.0 In-Reply-To: <59407ee2-6413-7a8a-02d4-492bd3276a84@canonical.com> References: <59407ee2-6413-7a8a-02d4-492bd3276a84@canonical.com> From: Linus Torvalds Date: Sun, 7 Jan 2018 11:40:49 -0800 X-Google-Sender-Auth: 74fu4jwCgYHmMAiIHIh33DWdjFM Message-ID: Subject: Re: [GIT PULL] apparmor fix for 4.15-rc7 To: John Johansen Cc: LKLM Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sun, Jan 7, 2018 at 5:53 AM, John Johansen wrote: > > can you please pull the following regression fix for apparmor. Pulled. I do note that you still don't seem to have any signatures on your key. You've used it for a couple of months, any chance to get somebody to sign it? Even without signatures, it's a fine key and validates that it's the same person (or controlling entity) that keeps doing this, but it would be even better if there was an actual chain of trust in addition to the basic key. Linus