> On 07-Oct-98 Gerard Roudier wrote:
> > The chip also maps its IO registers at offset 0x80 of its PCI
> > configuration space. So, your command is just doing a register dump while
> > the chip is running. Normally, the only IO register that can be accessed
> > while the SCRIPTS processor is running is the ISTAT register.
>
> So you're saying that having /proc/bus/pci/* world-readable is a significant
> security hole?
Not at all. But I was suggesting that allowing to read more than the first
64 bytes of PCI config space, even under root account, is a bad idea, at
least for 53C8XX PCI devices. In fact, I think it is a bad idea in
general, since getting side effects while reading the device specific area
of the PCI config space of a device is probably affecting some other PCI
devices. It is rather a nice way to break a running system than a real
security hole, in my opinion.
Regards,
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/