public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens@endorphin.org>
To: Paul Walker <paul@black-sun.demon.co.uk>
Cc: linux-kernel@vger.kernel.org, Bill Davidsen <davidsen@tmr.com>,
	linux-crypto@nl.linux.org, James Morris <jmorris@redhat.com>
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Mon, 17 Jan 2005 22:04:49 +0100	[thread overview]
Message-ID: <1105995889.14565.47.camel@ghanima> (raw)
In-Reply-To: <20050117192946.GT7782@black-sun.demon.co.uk>

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

On Mon, 2005-01-17 at 19:29 +0000, Paul Walker wrote:
> On Mon, Jan 17, 2005 at 08:14:58PM +0100, Fruhwirth Clemens wrote:
> 
> > > Unlikely to go to mainline kernel. Mainline folks are just too much in love
> > > with their backdoored device crypto implementations [1]. 
> 
> Just to add back in Jari's link, so the folks added know what you're talking
> about:
> 
> > [1]  http://marc.theaimsgroup.com/?l=linux-kernel&m=107419912024246&w=2

You will find the same information on my site. Therefore, I do NOT
decline this vulnerability. I decline it's security implications. It's
on the same level as the vulnerability, that you will give away your
root password under torture.[2]

Nothing about kernel crypto is backdoored. If Ruusu thinks different, he
should show me source code. Till then, treat it as FUD.

<off-topic>
[2] I think the torture vulnerability is more serious than any
watermarking "attack". "Rubberhosing" can be fixed btw.
http://web.archive.org/web/20031214064240/http://www.rubberhose.org/
Unfortunately, original site is down and source code outdated.
</off-topic>

-- 
Fruhwirth Clemens <clemens@endorphin.org>  http://clemens.endorphin.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-17 21:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:58 Announce loop-AES-v3.0b file/swap crypto package Jari Ruusu
2005-01-17  4:26 ` Bill Davidsen
2005-01-17  5:10   ` Willy Tarreau
2005-01-17 15:08   ` Jari Ruusu
2005-01-17 19:14     ` Fruhwirth Clemens
2005-01-17 19:29       ` Paul Walker
2005-01-17 21:04         ` Fruhwirth Clemens [this message]
2005-01-17 21:39           ` Paul Walker
2005-01-18 15:35           ` Jari Ruusu
2005-01-18 17:23             ` Andries Brouwer
2005-01-18 18:38               ` Venkat Manakkal
2005-01-19  0:18                 ` Dan Hollis
2005-01-19  0:46                   ` Kyle Moffett
2005-01-19 17:03                   ` Bill Davidsen
2005-01-19 17:57                     ` Fruhwirth Clemens
2005-01-19 21:24                       ` James Morris
2005-01-19 22:18                         ` Fruhwirth Clemens
2005-01-20 16:42                       ` Bill Davidsen
2005-01-17 21:26       ` markus reichelt
2005-01-17 23:11         ` Fruhwirth Clemens
2005-01-18  0:06           ` Daniel Harvey
2005-01-18 23:30             ` Peter_22
2005-01-18  9:49           ` jerome etienne
2005-01-18 15:36             ` Jari Ruusu
2005-01-20 22:38           ` markus reichelt
2005-01-21 18:29       ` Sytse Wielinga
2005-01-17 20:28     ` Andreas Jellinghaus
2005-01-17 21:38     ` Paul Walker

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=1105995889.14565.47.camel@ghanima \
    --to=clemens@endorphin.org \
    --cc=davidsen@tmr.com \
    --cc=jmorris@redhat.com \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@black-sun.demon.co.uk \
    /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