You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A windows SID is somewhat analogous to a *nix UID.
The data is already available in this method. It can be converted to a string using ConvertSidToStringSidW then stored in the process struct.
This would be a windows only function/value. It could be handled by having OS specific traits (WindowsProcessExt, LinuxProcessExt, etc) to enhance the process struct based on context or by having a fake method on every trait impl.
The text was updated successfully, but these errors were encountered:
Normally, Uid would already allow you to have access to this information. The problem here is that the SID of the process and the SID of the user don't match. So I decided to use the user name as Uid instead, meaning that I even though I manipulate this information at some point, I don't store it. So until the SID mismatch bug is fixed, you won't be able to have access to this information from sysinfo.
A windows SID is somewhat analogous to a *nix UID.
The data is already available in this method. It can be converted to a string using
ConvertSidToStringSidW
then stored in the process struct.This would be a windows only function/value. It could be handled by having OS specific traits (WindowsProcessExt, LinuxProcessExt, etc) to enhance the process struct based on context or by having a fake method on every trait impl.
The text was updated successfully, but these errors were encountered: