Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265529AbUABMpi (ORCPT ); Fri, 2 Jan 2004 07:45:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265530AbUABMph (ORCPT ); Fri, 2 Jan 2004 07:45:37 -0500 Received: from websrv.werbeagentur-aufwind.de ([213.239.197.241]:20178 "EHLO mail.werbeagentur-aufwind.de") by vger.kernel.org with ESMTP id S265529AbUABMp0 (ORCPT ); Fri, 2 Jan 2004 07:45:26 -0500 Subject: Re: CPRM ?? Re: Possibly wrong BIO usage in ide_multwrite From: Christophe Saout To: Andre Hedrick Cc: Bartlomiej Zolnierkiewicz , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1073047522.4239.6.camel@leto.cs.pocnet.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 02 Jan 2004 13:45:22 +0100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1111 Lines: 25 Am Fr, den 02.01.2004 schrieb Andre Hedrick um 05:43: > I am sorry but adding in a splitter to CPRM is not acceptable. > Digital Rights Management in the kernel is not acceptable to me, period. > > Maybe I have misread your intent and the contents on your website. > > Device-Mappers are one thing, intercepting buffers in the taskfile FSM > transport is another. This stinks of CPRM at this level, regardless of > your intent. Do correct me if I am wrong. I can assure you I was never having DRM or anything like this in mind nor making fundamental changes to the IDE layer. It was just that ++bi_idx that bugged me. Must be a misunderstanding, sorry. :) The only thing I'm having on my website is a device-mapper target that does basically the same as cryptoloop tries to. It's just about encrypting sensitive data on top of any other device, nothing else. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/