mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Emmanuel Fleury <fleury@cs.aau.dk>
To: Linux Kernel Mailing-list <linux-kernel@vger.kernel.org>
Cc: Kalin KOZHUHAROV <kalin@thinrope.net>
Subject: Re: [Transmeta hardware] Update of the CMS under Linux ?
Date: Mon, 06 Sep 2004 10:05:55 +0200	[thread overview]
Message-ID: <1094457952.22441.34.camel@rade7.e.cs.auc.dk> (raw)
In-Reply-To: <ch8lop$m3t$1@sea.gmane.org>

Hi,

Actually, I have an answer to my question by now.

The way the CMS is built-in on the hardware allow one way to upgrade the
firmware (and only one, as far as I understood in
http://www.realworldtech.com/page.cfm?ArticleID=RWT010204000000 and
http://www.realworldtech.com/page.cfm?ArticleID=RWT012704012616).

Each upgrade has to be signed with a certain private key (this private
key is known by the seller of the laptop (Toshiba in your case) and by
Transmeta itself... well I assume that in fact each entity has a partial
knowledge of the private key which makes impossible to one of these to
do something without the agreement of the other one).

So, the process for upgrading the CMS firmware is the following:

1) Load the upgrade in memory,
2) Check the signature of the upgrade with the public key stored in the
   ROM.
3) If the signature match with the upgrade, then apply the upgrade.

As you see, an upgrade (for Linux or Windows, whatever) requires the
agreement of both Transmeta AND the laptop seller. And you cannot easily
hack your way through.

I see only two solutions to do our own upgrade of the CMS:

1) Take the EPROM out and write our own public key on it...
   (risky and need a lot of hardware. I wouldn't recommand this way)

2) Crack the public/private keys of the hardware.
   (this is a known plaintext attack for the HP tablet-PC, and for the
    other hardwares we can only have access to the public-key which is
    making it more difficult but nothing that can resist to a brute
    force attack in the case we have enough Seti-like softwares
    running).

I have no idea if it is legal or not... it is not my concern now. 
I'm just seeking for solutions ! :)
I guess it depends if you are in the States or in Europe.

So, I am about here in my investigations and I still have this annoying
bug with the Xserver... Moreover, it seems that Transmeta is fully on
the Efficeon now and does not want to invest time and money on looking
for a bug in the Crusoe CMS (except if one of its customer is
specifically asking for it, which is very unlikely from Sony and/or
Fujitsu).

I am gathering some informations on a bug in the CMS here:
http://www.cs.auc.dk/~fleury/bug_cms/index.html

But, it looks like we are f**ked. :)

That's pretty annoying as these Transmeta laptops are an extremely cool
piece of hardware !!! :-/

Anyway, I won't give up so easily (for once that we have a nice bug to
fight with) !!! :)

Regards
-- 
Emmanuel Fleury

Computer Science Department, |  Office: B1-201
Aalborg University,          |  Phone:  +45 96 35 72 23
Fredriks Bajersvej 7E,       |  Fax:    +45 98 15 98 89
9220 Aalborg East, Denmark   |  Email:  fleury@cs.aau.dk


  reply	other threads:[~2004-09-06  8:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22  8:58 Emmanuel Fleury
2004-09-03  2:43 ` Kalin KOZHUHAROV
2004-09-06  8:05   ` Emmanuel Fleury [this message]
2004-09-06  8:50     ` Marcus Metzler
2004-09-06 15:58       ` Emmanuel Fleury
2004-09-06 16:03         ` Marcus Metzler
2004-09-06 14:29     ` Kalin KOZHUHAROV
2004-09-06 16:10       ` Emmanuel Fleury
2004-09-06 17:07         ` Marcus Metzler

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=1094457952.22441.34.camel@rade7.e.cs.auc.dk \
    --to=fleury@cs.aau.dk \
    --cc=kalin@thinrope.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®