Obstacles for kdbus
Obstacles for kdbus
Posted Apr 18, 2015 11:09 UTC (Sat) by mathstuf (subscriber, #69389)In reply to: Obstacles for kdbus by aigarius
Parent article: Obstacles for kdbus
Yes. I'm implementing the SecretService API in keepassx and I'm locking it down so that access is based on a per-application basis (so a malicious app can't rummage around once it is open). Determining the binary is dependent on the executable pointed to by /process/PID/exe. I'd be grateful for better solutions, but that's the best I can do right now. I'm pretty sure it isn't subject to PID races since the reply won't be hooked up if it gets replaced (though exec could happen I suppose).
Posted Apr 18, 2015 18:44 UTC (Sat)
by nybble41 (subscriber, #55106)
[Link] (1 responses)
Unless you're doing something to prevent LD_PRELOAD and ptrace(), I'm not sure what you intend to accomplish by this. Even ignoring any potential PID race conditions, the code which is running and has access to the message bus is not determined solely by /proc/PID/exe.
Posted Apr 18, 2015 19:11 UTC (Sat)
by mathstuf (subscriber, #69389)
[Link]
Obstacles for kdbus
Obstacles for kdbus