linux-kernel - Re: [PATCH] Changes to integrate RAR with SEP and fix RAR problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Oct 2009 14:29:36 -0700
From:	Greg KH <greg@...ah.com>
To:	Mark Allyn <mark.a.allyn@...el.com>
Cc:	linux-kernel@...r.kernel.org, alan@...ux.intel.com,
	charles.f.johnson@...el.com
Subject: Re: [PATCH] Changes to integrate RAR with SEP and fix RAR problems

On Tue, Oct 06, 2009 at 01:45:53PM -0700, Mark Allyn wrote:
> SEP stands for Security Processor; a dedicated processor
> that does encryption, decryption, key management, and
> secure storage.
> 
> RAR stands for Restricted Access Region; this is memory
> aboard the MID platform that is restricted (via hardware)
> from access by software running on the x86 processor.
> Dedicated 'smart' peripherals such as sound, video, and
> encryption can access these regions of memory. They are here
> to help protect copyrighted midia from being illegally copied.

How does it allow "fair-use" copying?  To prevent that is considered
illegal in some juristictions :)

> This is upstream revision 4 of the RAR driver.
> 
> This is a patch referenced from the linux-next repository
> as pulled on October 6, 2009; from the following URL:

Why are you deleting the existing driver entirely?  Why not just patch
it to have whatever new things you need here?

> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> 
> This is a modified RAR driver to include integration with
> the SEP driver
> 
> Plese be aware that the SEP driver requires this driver
> in order to compile and run. There are API function calls
> within this driver that are required by the SEP driver.
> 
> Other drivers being developed in the future will also 
> require this driver.

What drivers?  In what way will it be required?

Your patch contains a number of obvious problems that
scripts/checkpatch.pl would have caught.  Please run it through that
before submitting it again.

I'll not take this version for the above reasons.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/