На 5.06.25 г. в 15:49 ч., Johannes Schindelin via Cygwin написа: [SNIP]
and bisecting my problem to https://github.com/cygwin/cygwin/commit/48e7d632689313106d16b0de035fb955c54492b2, the following diff (which partially reverts that commit) fixes it for me:
Dunno what is correction in v3.6.3 but functionality is restored.
```diff diff --git a/winsup/cygwin/uinfo.cc b/winsup/cygwin/uinfo.cc index 83883f9f65..795a00cc1a 100644 --- a/winsup/cygwin/uinfo.cc +++ b/winsup/cygwin/uinfo.cc @@ -1996,10 +1996,12 @@ pwdgrp::fetch_account_from_windows (fetch_user_arg_t &arg, cyg_ldap *pldap) if (sid_id_auth (sid) == 5 /* SECURITY_NT_AUTHORITY */ && sid_sub_auth (sid, 0) == SECURITY_APPPOOL_ID_BASE_RID) break; +#if 0 /* AzureAD SIDs */ if (sid_id_auth (sid) == 12 /* AzureAD ID */ && sid_sub_auth (sid, 0) == 1 /* Azure ID base RID */) break; +#endif /* Samba user/group SIDs */ if (sid_id_auth (sid) == 22) break; ``` Now, the commit message of that commit includes the name of the reporter, which helped me find https://inbox.sourceware.org/cygwin/pbli6jecn5go2h7heebwivkwz6xf5h2stvq5fxna4u6pql6uht@7xpentpxjiak/ as the original reason for that commit. That request only talked about `S-1-15-3-*`, though, and not about `S-1-12-1-*`. And the commit message makes it sound as if my SID would never resolve by `LookupAccountSid()`, but it clearly does. So I am not quite sure what to make of this finding... Should the `S-1-12-1-*` part of 48e7d63268 (Cygwin: fetch_account_from_windows: skip LookupAccountSid for SIDs known to fail, 2025-04-10) simply be dropped? Or was there another clever idea to exploit a shortcut that would side-step the need to call `LookupAccountSid()` for those SIDs and set `ret = TRUE`? Puzzled, Johannes
[SNIP] Thanks for all your efforts. Regards, Roumen Petrov -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
