Hello David,
On Oct 24 18:58 Suffield, David wrote (shortened):
Could you give me some more details what hpmud does to open
the device file so that I can let our security team have a
look at it or should they simply check all the files in io/hpmud/?
Yes, all the hplip i/o code is in
Hello David,
On Oct 23 21:31 Suffield, David wrote (shortened):
Changing OWNER=lp to OWNER=root is a valid change. The only
reason I changed it was I thought OWNER=lp would be more secure
than OWNER=root with MODE=0666.
I don't claim to be a security expert, but if OWNER=root is not
a
Hi Johannes,
As far as I understand it, traditional security in Unix/Linux
(i.e. without additional stuff like AppArmor or SELinux) is
done by a separation by using different user accounts.
Here changing the device file permissions is separated from
using the device file (under the
Hi Johannes,
HPLIP 2.7.10 - This release has the following changes:
1. Made a change to 55-hpmud.rules ...
I do not understand why there is OWNER=lp in 55-hpmud.rules.
When the owner is lp, then any CUPS filter script or backend
can change the permissions as it likes, for
