Hi,
> # ls -la /dev/null
> crw-rw-rw- 1 root root 1, 3 2009-12-12 12:30 /dev/null
> # x11vnc -quiet -storepasswd foo /dev/null
> stored passwd in file /dev/null
> # ls -la /dev/null
> crw------- 1 root root 1, 3 2009-12-12 12:30 /dev/null
>
> x11vnc also claims to write to block devices with return code 0 even
> though it fails.
Due to this bug report the -storepasswd error reporting has been improved
in the x11vnc 0.9.9 dev tarball:
http://x11vnc.sourceforge.net/dev/x11vnc-0.9.9.tar.gz
i.e., the reason for the failure is now reported.
Regarding writing to character devices like /dev/null, I'm not sure
why x11vnc shouldn't write to them if the user requests it.
Regarding changing the permissions, I don't feel this is a bug. I think
it is better to err on the safe safe side to prevent other users from
being able to read the VNC password. It's unfortunate that running
x11vnc -storepasswd with root privileges one can change the permissions
of device files in, e.g., /dev, but this is the expected behavior.
Also note that it is the libvncserver library package, not x11vnc,
that changes the pemissions to 0600.
With the above x11vnc 0.9.9 tarball I cannot reproduce the behavior
you describe WRT block devices: if done as ordinary user it fails, if
done as root it actually does write it to the first 8 bytes.
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
