From: "Bud P. Bruegger" <bruegger@ancitel.it>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Forrester <forrester@ancitel.it>,
John@csclub.uwaterloo.ca, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU as a "virtual smart card"?
Date: Fri, 4 Sep 2009 15:40:39 +0200 [thread overview]
Message-ID: <20090904154039.09fd1cad@bud-laptop> (raw)
In-Reply-To: <20090904131228.GH23700@csclub.uwaterloo.ca>
> Well if you look at intel's current wireless chips, they have some
> firmware that runs on them, but because the instruction set of that
> processor is secret and the addresses of all the devices inside the
> chip are secret, it would be very hard to reverse engineer the
> firmware and hence make changes to it. Not impossible of course, but
> very hard.
>
> To some extent, if you want it secret, make a custom chip, not
> software. Software can't be secret, only hard to get at.
Hmmm. Hardware would surely be the best solution. A hard smartcard
and lots of headaches are gone. I'm looking at a temporary solution
where smartcards have not arrived yet (too slow, not in this year's
budget..) and where username pwd is an even worse idea ;-)
And soft credentials are difficult...
The plain old PKCS#12 would not survive a day in today's malware
environment. It wouldn't even be worth-while using it..
I'm looking for a pragmatic way of getting something useful, very
difficult to exploit by malware and reasonably hard to not be figured
out right off.
Working on this, I feel like someone who wants to invent a perpetuum
mobile...
I'm wondering whether there would be a way of finding some framework in
which "puzzles" can be plugged in that bring the necessary obfuscation
and delay of being cracked. The framework should use one puzzle to
protect the next (sequential instead of parallel cracking)...
any ideas whether such a thing is even possible?
best cheers
-b
next prev parent reply other threads:[~2009-09-04 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 16:08 [Qemu-devel] QEMU as a "virtual smart card"? Bud P. Bruegger
2009-09-01 22:27 ` Laurent Vivier
2009-09-01 23:47 ` Jamie Lokier
2009-09-02 14:58 ` Blue Swirl
2009-09-03 15:09 ` Bud P. Bruegger
2009-09-03 18:51 ` Blue Swirl
2009-09-04 12:08 ` Paul Brook
2009-09-04 13:12 ` Lennart Sorensen
2009-09-04 13:40 ` Bud P. Bruegger [this message]
2009-09-05 2:21 ` Jamie Lokier
2009-09-02 6:58 ` [Qemu-devel] " Paolo Bonzini
2009-09-02 9:17 ` François Revol
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=20090904154039.09fd1cad@bud-laptop \
--to=bruegger@ancitel.it \
--cc=John@csclub.uwaterloo.ca \
--cc=blauwirbel@gmail.com \
--cc=forrester@ancitel.it \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).