On Wed, Oct 22, 2003 at 07:55:56PM +0200, Evan Langlois wrote:
> The smart-card suggestion someone posed might be an idea.
I like the Schlumberger (now: Axalto) Cryptoflex[1] (NB not Cyberflex) cards
a lot. I have a few e-gate 32K[2] cards that I'm playing with here, I'm
using the USB token, but i
> They don't have to disassemble the ROM, when GPLed code is used to
> build it.
> You can't keep it secret when you added your crypto code to GPLed
> software (like LinuxBIOS or FILO).
Oh yes! My bad.
I agree 100%. I'm definately against illegal appropriation of GPL code. I'm
usually the fi
> They don't have to disassemble the ROM, when GPLed code is used to
> build it.
> You can't keep it secret when you added your crypto code to GPLed
> software (like LinuxBIOS or FILO).
>
> You want obfuscation. IMHO it is a bad idea in general.
Agreed - was just a thought
-- Evan
On Wed, Oct 22, 2003 at 08:25:28AM -0700, Alan Mimms wrote:
> One thing that encryption in the bootstrap CAN do is prevent Trojan
> attacks against the kernel image. If attackers can't find out what the
> encryption key is they can't create a substitute Trojan kernel. It
> plugs a hole.
That is
ent Center
Liberty Lake, Washington
v: 509-343-3524 f: 509-343-3501
-Original Message-
From: SONE Takeshi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2003 2:18 AM
To: Evan Langlois
Cc: [EMAIL PROTECTED]
Subject: Re: AMD64: Something's missing?
On Tue, Oct 21, 2003 at 1
On Wed, Oct 22, 2003 at 12:27:35PM +0200, Peter Stuge wrote:
> On Wed, Oct 22, 2003 at 05:31:46AM -0500, Evan Langlois wrote:
> > The boot image in this case would be a proprietary piece of software for
> > real-time network filtering. The algorythm for which is patented
> > technology. A user-in
On Wed, Oct 22, 2003 at 05:31:46AM -0500, Evan Langlois wrote:
> The boot image in this case would be a proprietary piece of software for
> real-time network filtering. The algorythm for which is patented
> technology. A user-input encryption key doesn't make sense as the box
> is stand-alone and
Encryption in boot process doesn't make sense to me.
What you want to protect is the data in the storage, not the boot image
(kernel).
Encryption of the storage is OS's bussiness, and the OS will ask you the
password before decrypting any data.
Don't assume the boot image is a Linux kernel!
On Tue, Oct 21, 2003 at 10:26:01PM +0200, Evan Langlois wrote:
>
> > EtherBoot can boot lots of things from the network or an IDE hard disk.
> > FILO can boot from IDE hard disk, IDE CDROM, floppy, and maybe more? 9load
> > I don't know much about except that it is used to load the plan9 kernel.
>
On Tue, Oct 21, 2003 at 10:26:01PM +0200, Evan Langlois wrote:
>
> I don't know much about FILO.
I should have included the URL where it lives: http://te.to/~ts1/filo/
Sorry about that.
> Can anyone comment on its compatibility with the LILO graphical features
> (displaying graphical menus/spla
> EtherBoot can boot lots of things from the network or an IDE hard disk.
> FILO can boot from IDE hard disk, IDE CDROM, floppy, and maybe more? 9load
> I don't know much about except that it is used to load the plan9 kernel.
I don't know much about FILO. Can anyone comment on its compatibility
Hi everyone.
This has a lot of basic stuff probably already well known on the list, but I
figured it might help someone. Felt like documenting a little. :)
On Mon, Oct 20, 2003 at 11:10:54PM +0100, Terry Blunt wrote:
> I *very* much like the idea of having as much of my system as possible
> open
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Stefan Reinauer <[EMAIL PROTECTED]> writes:
>
> > * Eric W. Biederman <[EMAIL PROTECTED]> [031013 15:23]:
> > > Sorry about that.
> >
> > I fixed it for Solo, others will follow once I have the Solo up again.
> >
> > > Before we declare this 2.0 i
Stefan Reinauer <[EMAIL PROTECTED]> writes:
> * Eric W. Biederman <[EMAIL PROTECTED]> [031013 15:23]:
> > Sorry about that.
>
> I fixed it for Solo, others will follow once I have the Solo up again.
>
> > Before we declare this 2.0 instead of 1.1.xxx
> > we should really have a target that will
* Eric W. Biederman <[EMAIL PROTECTED]> [031013 15:23]:
> Sorry about that.
I fixed it for Solo, others will follow once I have the Solo up again.
> Before we declare this 2.0 instead of 1.1.xxx
> we should really have a target that will build everything
> in the tree that a person has the compi
Stefan Reinauer <[EMAIL PROTECTED]> writes:
> * Stefan Reinauer <[EMAIL PROTECTED]> [031013 10:42]:
> > Building the Quartet target with latest CVS I get:
> > raminit.c:2378.43: is_cpu_pre_c0 undeclared
>
> ah.. northbridge/amd/amdk8/cpu_rev.c is the secret.
Sorry about that.
Before we declare
* Stefan Reinauer <[EMAIL PROTECTED]> [031013 10:42]:
> Building the Quartet target with latest CVS I get:
> raminit.c:2378.43: is_cpu_pre_c0 undeclared
ah.. northbridge/amd/amdk8/cpu_rev.c is the secret.
Stefan
--
Architecture Team
SuSE Linux AG
__
Building the Quartet target with latest CVS I get:
raminit.c:2378.43: is_cpu_pre_c0 undeclared
I'll look into it..
Stefan
--
Architecture Team
SuSE Linux AG
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo
18 matches
Mail list logo