Sensors and grsecurity

Sensors and grsecurity

[David Cannings]

I have been trying to get sensors and grsecurity playing nicely however
it seems that this is impossible if /dev/port restrictions are enabled.
 Unfortunately, these restrictions come along with the ones on /dev/kmem
and /dev/mem, so I don't really want to disable them.

If my W83697HF only detects on the ISA bus, is it going to be impossible
to read data from it without access to /dev/port?

Thanks,

David

Sensors and grsecurity

[Jean Delvare]

> I have been trying to get sensors and grsecurity playing nicely
> however it seems that this is impossible if /dev/port restrictions are
> enabled.
> Unfortunately, these restrictions come along with the ones on /dev/kmem
> and /dev/mem, so I don't really want to disable them.
> 
> If my W83697HF only detects on the ISA bus, is it going to be
> impossible to read data from it without access to /dev/port?

The sensors-detect script uses /dev/port, but the driver itself
obviously doesn't (since it belongs to kernel space). Thus there should
be no issue (other than sensors-detect not working, but if you already
know which devices you have, you don't need it anyway.

-- 
Jean Delvare
http://khali.linux-fr.org/

Sensors and grsecurity

[David Cannings]

Jean Delvare wrote:
>> I have been trying to get sensors and grsecurity playing nicely
>> however it seems that this is impossible if /dev/port restrictions are
>> enabled.
>> Unfortunately, these restrictions come along with the ones on /dev/kmem
>> and /dev/mem, so I don't really want to disable them.
>> 
>> If my W83697HF only detects on the ISA bus, is it going to be
>> impossible to read data from it without access to /dev/port?
> 
> The sensors-detect script uses /dev/port, but the driver itself
> obviously doesn't (since it belongs to kernel space). Thus there should
> be no issue (other than sensors-detect not working, but if you already
> know which devices you have, you don't need it anyway.

My apologies for the question, I realise in hindsight that it does not
make sense!  Of course the driver doesn't use /dev/port, it works fine
with the restrictions enabled.

Thanks again for your help,

David