Re: DAMN the reply button

1998-11-14 Thread H. Peter Anvin
> > We still use the MAC address (mostly because it's the only numbered > component we *know* will be present), but it's definitely forgeable. It's > just that our usual customer wouldn't know how to do it. (Plus, I'm not > sure they'd even want to, in significant numbers. They might want mo

Re: DAMN the reply button

1998-11-14 Thread Kai Henningsen
[EMAIL PROTECTED] (H. Peter Anvin) wrote on 13.11.98 in <[EMAIL PROTECTED]>: > Using the Ethernet address makes some amount of sense: although you > can set the Ethernet address if you want, it will really screw up your > network if you have the same address for more than one host, which is > usu

Re: DAMN the reply button

1998-11-14 Thread H. Peter Anvin
> > Then they wrote VM. > > Which has a command to set that serial number to anything you like. > > And yes, I've seen it used for software that looked at the serial number > for license purposes. > > I don't think it's worth it. It's far too easy to break. It's fake > security. > > MfG Ka

Re: DAMN the reply button

1998-11-14 Thread Kai Henningsen
[EMAIL PROTECTED] (BadlandZ) wrote on 11.11.98 in <[EMAIL PROTECTED]>: > (IMHO, maybe CPU, but BIOS for the sake of discussion). LINUX should > read (and not "soft" read) a serial number out of the BIOS, and not hold > it in software to be hacked. BIOS manufacture might be easier to Remember,

Re: DAMN the reply button

1998-11-12 Thread mattdm
> (IMHO, maybe CPU, but BIOS for the sake of discussion). LINUX should > read (and not "soft" read) a serial number out of the BIOS, and not hold > it in software to be hacked. BIOS manufacture might be easier to Any scheme like this can be hacked. Especially -- but certainly not limited to -- w