Notes about work in progress items and other long term cleanups.
Details
Details
Description
Thu, May 25
Thu, May 25
gniibe added a comment to T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control.
Since it's ABI change, I created a branch: https://dev.gnupg.org/source/libassuan/history/gniibe%252Ft6487/
Wed, May 24
Wed, May 24
gniibe added a comment to T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control.
I conclude that adding two public functions for pipe connection of client will be useful (and solve the pid_t issue, by successfully hiding those use cases).
Wed, May 17
Wed, May 17
svuorela updated the task description for T6494: GOST Infos.
werner changed the edit policy for T6494: GOST Infos.
gniibe added a comment to T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control.
For (2-2), there are two use cases in GnuPG.
(A) In call-daemon.c (for SCD and TPM2D), wait_child_thread cares about daemon termination to clean up resources. In this case, it calls waitpid/WaitForSingleObject.
(B) In call-pinentry.c, watch_sock cares about dangling pinentry. When it detects client's EOF on the socket (between the client and gpg-agent), it kills pinentry process. In this case, it calls kill/TerminateProcess.
gniibe added a comment to T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control.
Finished the step to have cleaner semantics of the implementation by: rA6350f796fdd1: w32: Cleaner semantics for PID and Process handle.
Tue, May 16
Tue, May 16
gniibe renamed T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control from libassuan: Deprecate assuan_get_pid and improve use cases for process control to libassuan: Clear semantics for assuan_get_pid and improve use cases for process control.
Mon, May 15
Mon, May 15
gniibe triaged T6487: libassuan: Clear semantics for assuan_get_pid and improve use cases for process control as Wishlist priority.
Nov 9 2022
Nov 9 2022
werner added a comment to T4656: Windows 64-bit: functions which use pid_t.
AFAIK, Microsoft stated that the value of a HANDLE will always fit into a DWORD; i.e. only the lower 32 bits are used even on a 64 bit Windows.
gniibe added a comment to T4656: Windows 64-bit: functions which use pid_t.
Now, we implemented fd passing on Windows in libassuan.
Note that the process identifier (represented by DWORD) and handle for a process (represented by HANDLE) are different things.
Nov 7 2022
Nov 7 2022
gniibe changed the status of T6236: libassuan: Support sendfd/recvfd (possibly by new API) on Windows, a subtask of T4655: Windows 64-bit: gnupg_fd_t, assuan_fd_t and int for fd in the API, and casts, from Open to Testing.
gniibe changed the status of T6236: libassuan: Support sendfd/recvfd (possibly by new API) on Windows, a subtask of T4656: Windows 64-bit: functions which use pid_t, from Open to Testing.
Oct 12 2022
Oct 12 2022
Oct 5 2022
Oct 5 2022
Mar 31 2022
Mar 31 2022
gniibe added a comment to T4655: Windows 64-bit: gnupg_fd_t, assuan_fd_t and int for fd in the API, and casts.
SOCKET handle is UINT_PTR on Windows. It is u_int on original MinGW, it is UINT_PTR (and unsinged __int64_t) on MinGW-W64.
Mar 29 2022
Mar 29 2022
gniibe added a comment to T4656: Windows 64-bit: functions which use pid_t.
Original MinGW and MinGW-w64 handle differently.
For MinGW-w64 on 64-bit machine, pid_t is 64-bit integer.
For original MinGW on 64-bit machine, pid_t is 32-bit integer.
Aug 13 2021
Aug 13 2021
Jul 31 2019
Jul 31 2019
werner triaged T4655: Windows 64-bit: gnupg_fd_t, assuan_fd_t and int for fd in the API, and casts as Wishlist priority.