From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 62743C43334 for ; Sun, 12 Jun 2022 00:21:47 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1o0BMP-0001QJ-RU for kernelnewbies@archiver.kernel.org; Sat, 11 Jun 2022 20:21:45 -0400 Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1o0BKQ-0007HM-Np for kernelnewbies@kernelnewbies.org; Sat, 11 Jun 2022 20:19:42 -0400 Received: by mail-qk1-x733.google.com with SMTP id g15so387559qke.4 for ; Sat, 11 Jun 2022 17:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vt-edu.20210112.gappssmtp.com; s=20210112; h=sender:from:to:cc:subject:in-reply-to:references:mime-version :content-transfer-encoding:date:message-id; bh=SrV4GusZBgmR22K8yzP6IMT4Qm3BvYWwmXvEb9AJ/D0=; b=YV/PtFwbQUOIVDlBB2ERII1WOz0jcYtXA1xBaIM2cUuQm3cMrC9/TX2iupg93UIszv EjDl5C/s+dPu9Vyj3n2TXX4BkVp0NfN7NkOW8+55QsC/0IOoc7MXz1lnoYJhq9+KAuHa iKOqAGIz7fwRAtOcGAbWm4flBX24xkS2YVWwjpdNneYkbZgFisb5QhQ+l3Yh6aPMzNzJ HZCDcJ2pVRV/pOSi+pQTmeH/8M38B1qYnU7fh6H/bscbNms1hdR8txZ0GhY5hhYXvgAx Onj1t4sNx/gIoeSzPKyUthiHQiR3CTjtlxN5fUz0iGT4hiiRkRtFxppbZsJWN3/zBbQo jJEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=SrV4GusZBgmR22K8yzP6IMT4Qm3BvYWwmXvEb9AJ/D0=; b=PW53NcwZuPfsjVJrwSfMa32FaxP0ZtRmZ1slQNAaPbPyeIcp7uXyEYC/dtqbdZr/9O 6jQBlEQa7CLF2cZK+FzFYYSc/Rece8vsU82e1eLxqiY62xwWAOSQqkfIT0idLD5tClJF NFymGxkN+NqmbIAlmNNJqXGhk6JT2s6rG+kXq7adjm3vR71MfWZFmC8b9kqv8J4Ywk/i IMyldIoioVHI4S3XQnTntdU1238hVBz0tqfTn1zDlCFlXtLVNYk6Qkd/cbeN9XrzMoU5 HROyvErGPbK/nAMMh4fVdWrVKpLXaIMoeLCAbE9ElcaOKLI1Jdp2OxjBbdOtP/J/RSLj eWwA== X-Gm-Message-State: AOAM533dGoO9XjXZIUjifDfjM6Wa+2F9Dy6dd/sZGxOtXySQkKHMd+wV SESDy7unYssj+i06uxFsWIzgwcd3Iok5QQ== X-Google-Smtp-Source: ABdhPJze59Br26/yJEhx20VvjVN3pzmUlApQIqZMjnXG1meIFAFvydERHqasfQyytA15kil1w83BUQ== X-Received: by 2002:a05:620a:917:b0:6a6:b76b:d6b4 with SMTP id v23-20020a05620a091700b006a6b76bd6b4mr23960991qkv.279.1654993180842; Sat, 11 Jun 2022 17:19:40 -0700 (PDT) Received: from turing-police ([2601:5c0:c380:d60:f276:1cff:fe8f:1dec]) by smtp.gmail.com with ESMTPSA id d1-20020a05620a240100b0069c72b41b59sm3124057qkn.2.2022.06.11.17.19.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 11 Jun 2022 17:19:40 -0700 (PDT) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.10.0-pre 07/05/2021 with nmh-1.7+dev To: Greg KH Subject: Re: What to do when your patch gets ignored In-reply-to: References: <68cfc625-4ec6-4694-28bd-f75673dac951@systemli.org> Mime-Version: 1.0 Date: Sat, 11 Jun 2022 20:19:38 -0400 Message-ID: <2571084.1654993178@turing-police> Cc: Richard , Andrea Tomassetti , kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org On Fri, 10 Jun 2022 16:34:03 +0200, Greg KH said: > Now deleted. > > Note, this footer requires kernel developers to delete any email sent > with it as it is not compatible with the kernel license at all. I had a standard form letter for that sort of nonsense, which asked if they wanted us to just hit delete, which would almost certainly leave lots of copies recoverable off all the systems involved, by any competent computer security expert, or if they were willing to indemnify us for the expenses involved in checking our (rather large) e-mail cluster, track down any copies on disk (including unlinked but not over-written blocks) and guarantee a forensically secure overwrite, and regenerate backup tapes that didn't include the blocks that the e-mail landed on in various passes through the queues. Oh, and the knock-on cost of downtime, as several thousand people would be idled while the email systems were down. (We actually once collected some $300K from a contractor who negligently set off the Halon, for everybody who couldn't get work done in the 3 hours it took to get everything back up.)now Other gotcha #1: We were trying to buy some fairly small equipment under rules that basically said we could accept the first reasonable offer rather than a full competitive bid. One company missed out because they sent *me* the offer - and I had to send them a reply that said "Nice offer. Too bad I had to delete it rather than forwarding it to my boss who has approval authority". Guess what happened while they got their act together and re-sent it? Yup - somebody else got an offer in first.... Other gotcha #2: Some legal experts say that blindly tagging *everything* with this footer rather than doing the right thing and using PGP or other crypto for stuff that actualy *is* sensitive, is basically an admission that they don't actually have a *clue* what data is or isn't sensitive. This can come back and bite them big time if there's an actual breach and there's now evidence of incompetence.... _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies