From: Pavel Machek <pavel@ucw.cz>
To: Tasos Parisinos <t.parisinos@sciensis.com>
Cc: Andi Kleen <andi@firstfloor.org>,
herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
randy.dunlap@oracle.com, indan@nul.nu
Subject: Re: [PATCH resend][CRYPTO]: RSA algorithm patch
Date: Tue, 3 Apr 2007 16:03:07 +0000 [thread overview]
Message-ID: <20070403160307.GA5266@ucw.cz> (raw)
In-Reply-To: <46111D03.5020905@sciensis.com>
Hi!
> >>The best environment to deploy such functionality is
> >>in updating by remote,
> >>executable code (programs, libs and modules) on
> >>embedded devices running
> >>Linux, that have some form of kernel physical
> >>security, so one can't
> >
> >How would that physical security look like? Would it
> >include DMA
> >protection?
> >
> >For example to do any useful form of graphics you need
> >user controllable DMA, which can normally touch
> >everything.
> >There are various other similar "backdoors" for root.
> >
> >I'm somewhat sceptical because all kernels will need
> >access
> >to the direct mapping to operate and there are also
> >various
> >interfaces that can be as root (ab)used to change it.
> >
> >And when you can do that they can change function
> >pointers
> >and jump to arbitary code or change the kernel page
> >tables
> >and map arbitary code.
> >
> >Disallowing all this would probably end up with a quite
> >useless kernel.
> >
> >
> >>There are already some systems that implement and
> >>utilize such functionality that
> >>use windows platforms, and other Linux distros that
> >>use userland
> >
> >Yes, at least the Vista variant was just broken. And
> >its designers spent
> >a lot of effort on it, but it didn't help.
> >
> Please read the thread i gave you for some details for
> things you ask
>
> Have in thought that we mostly talk here about embedded
> devices
> that run Linux in a very restricted environment where
> only specific
> applications are allowed to exist and run, there are no
> user logons
> and these applications need to be updated by remote once
> in a while
> over public networks. These applications need not be
> tampered with
What kind of applications are we talking about here? I'd like to hack
hardware I own.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-04-03 16:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 9:52 [PATCH resend][CRYPTO]: RSA algorithm patch Tasos Parisinos
2007-04-02 12:27 ` Andi Kleen
2007-04-02 11:50 ` Tasos Parisinos
2007-04-02 13:28 ` Andi Kleen
2007-04-02 15:10 ` Tasos Parisinos
2007-04-02 15:28 ` Andi Kleen
2007-04-03 16:03 ` Pavel Machek [this message]
2007-04-04 9:55 ` Tasos Parisinos
2007-04-04 12:01 ` Pavel Machek
2007-04-06 21:30 ` Bill Davidsen
2007-04-06 23:06 ` Indan Zupancic
2007-04-07 3:53 ` Bill Davidsen
2007-04-11 10:14 ` Tasos Parisinos
2007-04-11 14:37 ` Indan Zupancic
2007-04-12 8:34 ` Tasos Parisinos
2007-04-12 9:35 ` Satyam Sharma
2007-04-12 12:22 ` Indan Zupancic
2007-04-12 12:40 ` Andi Kleen
2007-04-12 14:20 ` Satyam Sharma
2007-04-12 15:01 ` Indan Zupancic
2007-04-12 18:38 ` Satyam Sharma
2007-04-12 19:05 ` Indan Zupancic
2007-04-12 19:57 ` Satyam Sharma
2007-04-12 20:44 ` Indan Zupancic
2007-04-12 21:13 ` Satyam Sharma
2007-04-12 22:51 ` Indan Zupancic
2007-04-12 21:28 ` David Wagner
2007-04-12 23:31 ` Indan Zupancic
2007-04-13 13:56 ` Tasos Parisinos
2007-04-12 13:09 ` Indan Zupancic
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=20070403160307.GA5266@ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@firstfloor.org \
--cc=herbert@gondor.apana.org.au \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=t.parisinos@sciensis.com \
/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