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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 06 May 2015 03:50:13 +0300
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Benjamin Gaignard <benjamin.gaignard@...aro.org>,
	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Hans Verkuil <hverkuil@...all.nl>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Rob Clark <robdclark@...il.com>,
	Thierry Reding <treding@...dia.com>,
	Dave Airlie <airlied@...hat.com>,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Tom Gall <tom.gall@...aro.org>
Subject: Re: [RFC] How implement Secure Data Path ?

On Tuesday 05 May 2015 09:27:52 Christoph Hellwig wrote:
> On Tue, May 05, 2015 at 05:39:57PM +0200, Benjamin Gaignard wrote:
> > Since few months I'm looking for Linaro to how do Secure Data Path (SPD).
> > I have tried and implemented multiple thinks but I always facing
> > architecture issues so I would like to get your help to solve the
> > problem.
> > 
> > First what is Secure Data Path ? SDP is a set of hardware features to
> > garanty that some memories regions could only be read and/or write by
> > specific hardware IPs. You can imagine it as a kind of memory firewall
> > which grant/revoke accesses to memory per devices. Firewall configuration
> > must be done in a trusted environment: for ARM architecture we plan to
> > use OP-TEE + a trusted application to do that.
> > 
> > One typical use case for SDP in a video playback which involve those
> > elements: decrypt -> video decoder -> transform -> display
> 
> Sounds like a good enough reason not to implement it ever.

The irony of it is to post an RFC on they day before 
http://www.defectivebydesign.org/dayagainstdrm/ :-)

-- 
Regards,

Laurent Pinchart

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ