Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262782AbUACHyS (ORCPT ); Sat, 3 Jan 2004 02:54:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265930AbUACHyS (ORCPT ); Sat, 3 Jan 2004 02:54:18 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:36358 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id S262782AbUACHyP (ORCPT ); Sat, 3 Jan 2004 02:54:15 -0500 Date: Fri, 2 Jan 2004 23:51:29 -0800 (PST) From: Andre Hedrick To: Christophe Saout cc: Bartlomiej Zolnierkiewicz , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: CPRM ?? Re: Possibly wrong BIO usage in ide_multwrite In-Reply-To: <1073047522.4239.6.camel@leto.cs.pocnet.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1554 Lines: 45 Christophe, Fair enough, and point taken. Thanks for the clarification. I am puzzled by the need to modify buffers on the fly inside the FSM. This is straight out of some unpublished information, so it struck a raw nerve. Just be aware this tends to follow the design and could be used for such. Cheers, Andre Hedrick LAD Storage Consulting Group On Fri, 2 Jan 2004, Christophe Saout wrote: > 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/