Skip site navigation (1)Skip section navigation (2)
Date:      Sat,  2 Dec 2000 16:39:39 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        "Kenneth D. Merry" <ken@kdm.org>
Cc:        hackers@FreeBSD.ORG, stable@FreeBSD.ORG
Subject:   Re: PCIOCGETCONF/PCIOCREAD requires write permission?
Message-ID:  <14889.27531.660040.955219@grasshopper.cs.duke.edu>
In-Reply-To: <20001201174408.A17122@panzer.kdm.org>
References:  <200012012056.eB1KuDI32343@orthanc.ab.ca> <20001201174408.A17122@panzer.kdm.org>

next in thread | previous in thread | raw e-mail | index | archive | help

Kenneth D. Merry writes:
 > As for PCIOCREAD, it only allows reading of PCI registers, so the question
 > there is whether there are any potential security implications to allowing
 > non-root users to read PCI registers.  If reading configuration registers
 > caused performance degredation, for instance.

I think that you might be able to crash an alpha with an unaligned
access trap by reading an int or short an from an unaligned offset in
config space.  At least this used to be true..  I'd vote for leaving
the access permissions as is. 

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14889.27531.660040.955219>