> On 2016-10-21, Kapetanakis Giannis <[email protected]> wrote: > > Hi, > > > > # dmidecode > > # dmidecode 3.0 > > Scanning /dev/mem for entry point. > > /dev/mem: Operation not permitted > > > > I guess this is similar to > > http://marc.info/?l=openbsd-misc&m=147575799412450&w=2 > > > > where stu@ said: > > "Kernel virtual memory access is no longer permitted by the kernel on a > > normally running system. The relevant parts of net-snmp will need to be > > disabled or rewritten" > > sthen@ != stu@ > > > Any way to get through that and read DMI entries? > > There is a sysctl kern.allowkmem: > > KERN_ALLOWKMEM > Allow userland processes access to /dev/kmem. When running with a > securelevel(7) greater than 0, this variable may not be changed. >
For the simple reason that this is 2016 not 1986, and userland code that can sniff through the kernel's physical address space is a ridiculous process. It needs to die; or have proper device driver interface that gives it exactly what it needs.
