From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Greg KH <greg@kroah.com>
Cc: Richard <richard_siegfried@systemli.org>,
Andrea Tomassetti <andrea.tomassetti@devo.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: What to do when your patch gets ignored
Date: Sat, 11 Jun 2022 20:19:38 -0400 [thread overview]
Message-ID: <2571084.1654993178@turing-police> (raw)
In-Reply-To: <YqNWWx4jQU6hhHrS@kroah.com>
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
next prev parent reply other threads:[~2022-06-12 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:39 What to do when your patch gets ignored Andrea Tomassetti
2022-06-10 12:18 ` Richard
2022-06-10 12:52 ` Andrea Tomassetti
2022-06-10 14:34 ` Greg KH
2022-06-12 0:19 ` Valdis Klētnieks [this message]
2022-07-04 14:57 ` Andrea Tomassetti
2022-07-05 3:35 ` Valdis Klētnieks
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=2571084.1654993178@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=andrea.tomassetti@devo.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=richard_siegfried@systemli.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;
as well as URLs for NNTP newsgroup(s).