From: Junio C Hamano <gitster@pobox.com>
To: "Sören Krecker" <soekkle@freenet.de>
Cc: git@vger.kernel.org, sunshine@sunshineco.com
Subject: Re: [PATCH v3 1/1] Replace SID with domain/username
Date: Tue, 02 Jan 2024 09:43:45 -0800 [thread overview]
Message-ID: <xmqqsf3feilq.fsf@gitster.g> (raw)
In-Reply-To: <20231231091245.2853-2-soekkle@freenet.de> ("Sören Krecker"'s message of "Sun, 31 Dec 2023 10:12:45 +0100")
Sören Krecker <soekkle@freenet.de> writes:
> Replace SID with domain/username in error message, if owner of repository
> and user are not equal on windows systems.
>
> Old message:
> '''
> fatal: detected dubious ownership in repository at 'C:/Users/test/source/repos/git'
> 'C:/Users/test/source/repos/git' is owned by:
> 'S-1-5-21-571067702-4104414259-3379520149-500'
> but the current user is:
> 'S-1-5-21-571067702-4104414259-3379520149-1001'
> To add an exception for this directory, call:
>
> git config --global --add safe.directory C:/Users/test/source/repos/git
> '''
>
> New massage:
"massage"???
> '''
> fatal: detected dubious ownership in repository at 'C:/Users/test/source/repos/git'
> 'C:/Users/test/source/repos/git' is owned by:
> 'DESKTOP-L78JVA6/Administrator'
> but the current user is:
> 'DESKTOP-L78JVA6/test'
> To add an exception for this directory, call:
>
> git config --global --add safe.directory C:/Users/test/source/repos/git
> '''
The same "does this lose information?" comment applies to this one
as well, as the fundamental approach is unchanged.
> +static BOOL user_sid_to_user_name(PSID sid, LPSTR *str)
> +{
> + SID_NAME_USE pe_use;
> + DWORD len_user = 0, len_domain = 0;
> + BOOL translate_sid_to_user;
> +
> + /* returns only FALSE, because the string pointers are NULL*/
> + LookupAccountSidA(NULL, sid, NULL, &len_user, NULL, &len_domain,
> + &pe_use);
> + /*Alloc needed space of the strings*/
> + ALLOC_ARRAY((*str), (size_t)len_domain + (size_t)len_user);
> + translate_sid_to_user = LookupAccountSidA(NULL, sid, (*str) + len_domain, &len_user,
> + *str, &len_domain, &pe_use);
> + *(*str + len_domain) = '/';
> + if (translate_sid_to_user == FALSE) {
> + FREE_AND_NULL(*str);
> + }
Is this "FREE_AND_NULL" about clearing after you see an error? If
so, shouldn't "overwrite the byte after the domain part with a slash"
be done only when you have no error, i.e., perhaps
translate_sid_to_user = LookupAccountSidA(...);
if (!translate_sid_to_user)
FREE_AND_NULL(*str);
else
(*str)[len_domain] = '/';
or something along the line?
> + return translate_sid_to_user;
> +}
next prev parent reply other threads:[~2024-01-02 17:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 12:03 [PATCH 0/1 v2] Replace SID with domain/username on Windows Sören Krecker
2023-12-29 12:03 ` [PATCH v2 1/1] Replace SID with domain/username Sören Krecker
2024-01-02 16:20 ` Junio C Hamano
2024-01-02 17:33 ` Junio C Hamano
2023-12-31 4:08 ` [PATCH 0/1 v2] Replace SID with domain/username on Windows Eric Sunshine
2023-12-31 9:12 ` [PATCH V3 0/1] " Sören Krecker
2023-12-31 9:12 ` [PATCH v3 1/1] Replace SID with domain/username Sören Krecker
2024-01-02 17:43 ` Junio C Hamano [this message]
2024-01-02 19:15 ` [PATCH V4 0/1] Replace SID with domain/username on Windows Sören Krecker
2024-01-02 19:15 ` [PATCH V4 1/1] Replace SID with domain/username Sören Krecker
2024-01-03 0:43 ` Junio C Hamano
2024-01-03 8:21 ` Matthias Aßhauer
2024-01-03 22:22 ` Junio C Hamano
2024-01-04 19:22 ` [PATCH v5 0/1] Replace SID with domain/username on Windows Sören Krecker
2024-01-04 19:22 ` [PATCH v5 1/1] Adds domain/username to error message Sören Krecker
2024-01-04 20:09 ` Junio C Hamano
2024-01-06 11:29 ` [PATCH v6 0/1] mingw: give more details about unsafe directory's ownership Sören Krecker
2024-01-06 11:29 ` [PATCH v6 1/1] " Sören Krecker
2024-01-07 20:02 ` Johannes Sixt
2024-01-08 17:38 ` [PATCH v6 0/1] mingw: give more details about unsafe directory's Sören Krecker
2024-01-08 17:38 ` [PATCH v7 1/1] mingw: give more details about unsafe directory's ownership Sören Krecker
2024-01-08 19:18 ` Junio C Hamano
2024-01-09 19:27 ` Johannes Sixt
2024-01-09 20:06 ` Junio C Hamano
2024-01-09 21:05 ` Johannes Sixt
2024-01-09 22:34 ` Junio C Hamano
2024-01-08 17:51 ` [PATCH v6 0/1] mingw: give more details about unsafe directory's Dragan Simic
2023-12-31 9:18 ` [PATCH V3 0/1] Replace SID with domain/username on Windows Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsf3feilq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=soekkle@freenet.de \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.