Retrieve pid and sid from tcp connection |
patch
|
2013-03-06 22:08:31 UTC |
6.94 KB |
no flags
|
Details |
Mingw plattform fixes |
patch
|
2013-03-06 22:08:53 UTC |
1.84 KB |
no flags
|
Details |
some fixes |
patch
|
2013-03-06 22:09:49 UTC |
2.06 KB |
no flags
|
Details |
GetTcpTable2() isn't available in msvc windows XP headers (indicated by using _WIN32_WINNT 0x0501). |
patch
|
2013-03-07 09:49:40 UTC |
840 bytes |
no flags
|
Details |
fixed related debug mesage eol |
patch
|
2013-03-07 09:50:33 UTC |
787 bytes |
no flags
|
Details |
Make _dbus_credentials_add_pid() plattform independent. |
patch
|
2013-03-07 09:50:58 UTC |
4.35 KB |
no flags
|
Details |
Do not retrieve credential information from the wrong side of the connection. |
patch
|
2013-03-08 10:25:00 UTC |
909 bytes |
no flags
|
Details |
Refactored to use dbus_pid_t instead of unsigned long. |
patch
|
2013-03-08 12:21:14 UTC |
3.39 KB |
no flags
|
Details |
Rename the term 'unix_pid' to 'pid' in variables and functions. |
patch
|
2013-03-08 12:23:56 UTC |
11.19 KB |
no flags
|
Details |
Use dbus_pid_t instead of unsigned long. |
patch
|
2013-03-08 12:24:58 UTC |
3.38 KB |
no flags
|
Details |
Add function get_peer_pid_from_tcp_handle() which returns pid and sid from tcp connection peer. |
patch
|
2013-03-08 14:32:57 UTC |
8.32 KB |
no flags
|
Details |
Further debug message eol fix |
patch
|
2013-03-08 22:19:34 UTC |
2.38 KB |
no flags
|
Details |
Use table class which has been implemented in wine 1.5.3. |
patch
|
2013-03-08 22:21:00 UTC |
1.33 KB |
no flags
|
Details |
Add debug message for returning from get_peer_pid_from_tcp_handle(). |
patch
|
2013-03-08 22:22:47 UTC |
694 bytes |
no flags
|
Details |
Add function get_peer_pid_from_tcp_handle() which returns pid and sid from tcp connection peer (combined) |
patch
|
2013-03-11 15:47:20 UTC |
8.64 KB |
no flags
|
Details |
updated |
patch
|
2013-04-04 15:30:52 UTC |
8.67 KB |
no flags
|
Details |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.