From: Alexander Holler <holler@ahsoftware.de>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Greg KH <gregkh@linuxfoundation.org>,
Josh Boyer <jwboyer@fedoraproject.org>,
Eric Curtin <ericcurtin17@gmail.com>,
Steve Calfee <stevecalfee@gmail.com>,
Valentina Manea <valentina.manea.m@gmail.com>,
Shuah Khan <shuah.kh@samsung.com>,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: First kernel patch (optimization)
Date: Mon, 21 Sep 2015 20:41:29 +0200 [thread overview]
Message-ID: <56004F59.6090706@ahsoftware.de> (raw)
In-Reply-To: <5600267A.8070605@gmail.com>
Am 21.09.2015 um 17:47 schrieb Austin S Hemmelgarn:
> On 2015-09-20 06:41, Alexander Holler wrote:
>> Am 20.09.2015 um 04:21 schrieb Theodore Ts'o:
>>> On Sat, Sep 19, 2015 at 07:47:22PM +0200, Alexander Holler wrote:
>>
>> Again, I don't think that encryption is an alternative. Besides that
>> there is always the thread that strong encrytion will become regulated,
>> there is also the very real thread that someone might end up in jail
>> when using encryption and throwing away the key to delete stuff. E.g.,
>> as to my knowledge, in the UK you might end up in jail if you don't hand
>> out a password. So what happens if you've deleted the key and are really
>> unable to hand it out and the people which have an interest in what
>> you've once stored don't believe you?
> First off, this is why I will never live in the UK. Secondly, this is
(First, it should, of course, read threat, not thread, my English
becomes worse when I'm getting angry, besides that I was working on a
problem with threads just before.)
Just in case of, I have not used the UK as an example because I might
hate it or similar (nothing of that is the case). I've used the UK as an
example to make it clear that such can happen in every country (besides
that I know that some kernel maintainers live there).. And e.g. the US
has had a time with regulated encryption (and I think there recently was
another attempt to regulate it again). And besides states, there might
be other people which might getting some unwanted ideas if they might
believe that there is something of value for them encrypted somewhere by
you. So, in my humble opinion, it's always better to get rid of
something clearly. That also helps against the problem that the
encryption used today, might be worthless tomorrow.
Regards,
Alexander Holler
next prev parent reply other threads:[~2015-09-21 18:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 19:53 First kernel patch (optimization) Eric Curtin
2015-09-15 20:11 ` Felipe Balbi
2015-09-16 0:09 ` Steve Calfee
2015-09-16 11:45 ` Austin S Hemmelgarn
2015-09-16 12:56 ` David Laight
2015-09-17 1:49 ` Jaime Arrocha
2015-09-17 8:45 ` David Laight
2015-09-16 13:24 ` Greg KH
2015-09-16 16:03 ` Eric Curtin
2015-09-16 16:40 ` Theodore Ts'o
2015-09-16 17:24 ` Raymond Jennings
2015-09-16 17:26 ` Josh Boyer
2015-09-18 3:12 ` Theodore Ts'o
2015-09-18 7:42 ` Greg KH
2015-09-18 9:31 ` Raymond Jennings
2015-09-18 19:08 ` Austin S Hemmelgarn
2015-09-19 2:26 ` Theodore Ts'o
2015-09-19 4:22 ` Sudip Mukherjee
2015-09-19 5:18 ` Greg KH
2015-09-19 12:20 ` Theodore Ts'o
2015-09-19 12:52 ` Alexander Holler
2015-09-19 14:14 ` Alexander Holler
2015-09-19 14:22 ` Theodore Ts'o
2015-09-19 17:47 ` Alexander Holler
2015-09-20 2:21 ` Theodore Ts'o
2015-09-20 10:41 ` Alexander Holler
2015-09-21 15:47 ` Austin S Hemmelgarn
2015-09-21 17:20 ` Alexander Holler
2015-09-21 18:41 ` Alexander Holler [this message]
2015-09-23 8:59 ` Alexander Holler
2015-09-28 6:54 ` Thiago Farina
2015-09-28 14:20 ` Greg KH
2015-09-16 20:02 ` Greg KH
2015-09-16 20:21 ` Eric Curtin
2015-09-16 22:38 ` Greg KH
2015-09-22 17:38 ` Linus Torvalds
2015-09-22 18:18 ` Eric Curtin
2015-09-25 22:06 ` Dmitry Torokhov
2015-09-26 13:28 ` Eric Curtin
2015-09-29 13:51 ` Austin S Hemmelgarn
2015-09-29 14:47 ` Eric Curtin
-- strict thread matches above, loose matches on Subject: below --
2015-09-15 19:52 Eric Curtin
2015-09-15 21:57 ` Alexander Duyck
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=56004F59.6090706@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=ahferroin7@gmail.com \
--cc=ericcurtin17@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah.kh@samsung.com \
--cc=stevecalfee@gmail.com \
--cc=tytso@mit.edu \
--cc=valentina.manea.m@gmail.com \
/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