> > Ok, it is much more dangerous for the hardware to do a cat /dev/zero >/
> > dev/bios than cat /dev/zero >/dev/sda, but in both cases the system
> > is a) unusable and needs reinstall/repair and b) can be quite easily
> > repaired.
>
> Can it really be repaired easily? I thought that the procedure was to go with
> your tail between your legs to your vendor and ask nicely for a new set of BIOS
> chips.
The german computer mag CT published a flash rom writer circuit. The way I
went was putting the "destroyed" flash chip into another computer after it
bootet correctly and then starting the flash utility and reflashing it.
Works fine, isn't everybody's thing maybe, though.
> > Taking away a driver's universal usability for "system security" or
> > whatever is IMHO not the way we should go.
>
> Agreed. How about having a sysctl variable which needs to be set in order to
> allow writing to the BIOS? Also, doesn't the official BIOS generally come with
> checksums to prevent accidental damage? Couldn't we use these?
I implemented a writable /proc/bios, maybe we could make something like
"echo unprotect >/proc/bios", too.
Stefan.
-- .signature: no such file or directory.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu