18 May
2013
18 May
'13
11:41 p.m.
On Thursday 16 of May 2013 05:36:18 Timothy Pearson wrote:
The problem is not whether it is created pipe or socket, but in the "where" is
created. And this problem remains the same as for v3.5.13.x branch and the
current master GIT.
1) It is used tdm: folder is created by root, root is owner of the folder and
permissions 0644 prevent users to create files here.
2) Not used tdm: folder is created by first user, this user is owner of the
folder and permissions 0644 make it impossible to create files here.
In both of these cases kdesktoplockcontrol not work.
Slavek
--
Hi all,
during the research around kdesktop_lock I found that kdesktoplockcontrol
(formerly pipe, now socket) can never work. Pipe / socket is created in
folder /tmp/tdesocket-global, but into this folder can enter and write
only 'root'. The folder is created with permissions 0644, which is a bit
unusual for the folders.
I also noticed (when I was allowed to write to the folder
tdesocket-global also for others) that kdesktoplockcontrol and
kdesktoplockcontrol_out are created but never removed.
Please can anyone confirm my findings?
How kdesktoplockcontrol was intended?
Currently obviously can never work.
Slavek
Much of this has been fixed in GIT. The pipes are rarely used, which is
why they became non-functional without detection some time ago, but are
part of the smart card login system.
Tim