All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jon Ringle <jringle@gridpoint.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"Ringle, Jonathan" <Jonathan.Ringle@gridpoint.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add option to build with -O3
Date: Wed, 05 Mar 2014 13:14:42 -0500	[thread overview]
Message-ID: <9247.1394043282@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 05 Mar 2014 01:19:17 -0500." <alpine.DEB.2.02.1403050111490.24331@jringle-ubuntu>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

On Wed, 05 Mar 2014 01:19:17 -0500, Jon Ringle said:

>  If you are not the intended recipient, please contact the sender by reply
> email and destroy all copies of the original message.

Is your company willing to indemnify my organization for the costs of tracking
down *all* copies of the message (including, but not restricted to, those on
backup tapes, copies automatically committed to WORM-based compliance stores by
our mail system, and already logically deleted but not yet overwritten blocks
on disk), and securely clearing the data sufficient to prevent its recovery by
an experienced forensics analyst armed with a subpoena and a "preserve
evidence" order?

And does your company's clientele realize that in case of a miscue on
the part of one of your staff, you're relying on an unknown third party's
good will to secure their confidential information, instead of relying on
actual cryptography to secure their data?

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2014-03-05 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  0:01 [PATCH] Add option to build with -O3 Jon Ringle
2014-03-05  5:09 ` Greg KH
2014-03-05  5:37   ` Jon Ringle
2014-03-05  6:08     ` Greg KH
2014-03-05  6:19       ` Jon Ringle
2014-03-05  6:31         ` Greg KH
2014-03-05 18:14         ` Valdis.Kletnieks [this message]
2014-03-06 13:28     ` Richard Weinberger
2014-03-07 12:39       ` Austin S Hemmelgarn
2014-03-07 12:42         ` Richard Weinberger
2014-03-07 12:51           ` Austin S Hemmelgarn
2014-03-07 13:48             ` Borislav Petkov
2014-03-05  7:32   ` Jon Ringle
2014-03-06  4:43     ` Greg KH
2014-03-05  7:36 jon
2014-03-06 12:28 ` Austin S Hemmelgarn

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=9247.1394043282@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=Jonathan.Ringle@gridpoint.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jringle@gridpoint.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.