find.exe -ls reports owner as "archive", does not report owner_group (GROUP_SECURITY_INFORMATION)

Open
#80 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start by tracing the find.exe -ls path that formats owner information and compare its current behavior with the reported Cygwin output. Read the linked Microsoft Security Information documentation, focusing on GROUP_SECURITY_INFORMATION. Done means -ls reports the owner group instead of the repeated archive value on the described Windows setup.

Written by the indexing model from the issue text.

Description

C-bug

find.exe -ls reports owner as "archive", does not report owner_group:

$ find.exe . -ls
0 4 archive 0 0 0 9 Jun 5 09:32 .
0 2048 archive 0 0 0 2097168 Jun 5 09:30 .\xxx
0 4 archive 0 0 0 0 Jun 5 09:14 .\myfile

Cygwin 3.6.9 on French Windows 11 reports this:
$ find . -ls
1487791 9 drwxr-xr-x 2 aucou Aucun 9 Jun 5 11:32 .
1487906 17 -rwxr-xr-x 1 aucou Aucun 2097168 Jun 5 11:30 ./xxx
1487792 1 -rw-r--r-- 1 aucou Aucun 0 Jun 5 11:14 ./myfile

It is important to get the Windows GROUP_SECURITY_INFORMATION" (group identity) in this case.
Please read https://learn.microsoft.com/en-us/windows/win32/secauthz/security-information

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.