# [PATCH] credential/libsecret: erase matching creds only 5 messages from 2023-06-24 to 2023-07-26. Participants: M Hickford via GitGitGadget, Junio C Hamano, M Hickford. Thread: https://gitlist.dev/t/59907 ## M Hickford via GitGitGadget, 2023-06-24 07:21 Subject: [PATCH] credential/libsecret: erase matching creds only Message-ID: URL: https://gitlist.dev/e/pull.1527.git.git.1687591293705.gitgitgadget%40gmail.com ``` From: M Hickford Fix test "helper ... does not erase a password distinct from input" introduced in aeb21ce22e (credential: avoid erasing distinct password, 2023-06-13) Signed-off-by: M Hickford --- credential/libsecret: erase more carefully Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1527%2Fhickford%2Ffix-libsecret-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1527/hickford/fix-libsecret-v1 Pull-Request: https://github.com/git/git/pull/1527 .../libsecret/git-credential-libsecret.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/contrib/credential/libsecret/git-credential-libsecret.c b/contrib/credential/libsecret/git-credential-libsecret.c index ef681f29d5b..9110714601e 100644 --- a/contrib/credential/libsecret/git-credential-libsecret.c +++ b/contrib/credential/libsecret/git-credential-libsecret.c @@ -52,6 +52,8 @@ struct credential_operation { #define CREDENTIAL_OP_END { NULL, NULL } +static void credential_clear(struct credential *c); + /* ----------------- Secret Service functions ----------------- */ static char *make_label(struct credential *c) @@ -185,6 +187,7 @@ static int keyring_erase(struct credential *c) { GHashTable *attributes = NULL; GError *error = NULL; + struct credential existing = CREDENTIAL_INIT; /* * Sanity check that we actually have something to match @@ -197,6 +200,20 @@ static int keyring_erase(struct credential *c) if (!c->protocol && !c->host && !c->path && !c->username) return EXIT_FAILURE; + if (c->password) { + existing.host = g_strdup(c->host); + existing.path = g_strdup(c->path); + existing.port = c->port; + existing.protocol = g_strdup(c->protocol); + existing.username = g_strdup(c->username); + keyring_get(&existing); + if (existing.password && strcmp(c->password, existing.password)) { + credential_clear(&existing); + return EXIT_SUCCESS; + } + credential_clear(&existing); + } + attributes = make_attr_list(c); secret_password_clearv_sync(SECRET_SCHEMA_COMPAT_NETWORK, attributes, base-commit: 6ff334181cfb6485d3ba50843038209a2a253907 -- gitgitgadget ``` ## M Hickford via GitGitGadget, 2023-07-26 16:06 Subject: [PATCH v2] credential/libsecret: erase matching creds only Message-ID: URL: https://gitlist.dev/e/pull.1527.v2.git.git.1690387585634.gitgitgadget%40gmail.com In-Reply-To: ``` From: M Hickford The credential erase request typically includes protocol, host, username and password. credential-libsecret erases a stored credential if it matches protocol, host and username, regardless of password. This is confusing in the case the stored password differs from that in the request. This case can occur when multiple credential helpers are configured. Only erase credential if stored password matches request (or request omits password). This fixes test "helper ... does not erase a password distinct from input" introduced in aeb21ce22e (credential: avoid erasing distinct password, 2023-06-13) Signed-off-by: M Hickford --- credential/libsecret: erase more carefully Patch v2 has a more detailed commit message following https://lore.kernel.org/git/xmqqpmax5c4v.fsf@gitster.g/ Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1527%2Fhickford%2Ffix-libsecret-v2 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1527/hickford/fix-libsecret-v2 Pull-Request: https://github.com/git/git/pull/1527 Range-diff vs v1: 1: dcc429c1afc ! 1: b5d5c3159ad credential/libsecret: erase matching creds only @@ Metadata ## Commit message ## credential/libsecret: erase matching creds only - Fix test "helper ... does not erase a password distinct from input" - introduced in aeb21ce22e (credential: avoid erasing distinct password, - 2023-06-13) + The credential erase request typically includes protocol, host, username + and password. + + credential-libsecret erases a stored credential if it matches protocol, + host and username, regardless of password. + + This is confusing in the case the stored password differs from that + in the request. This case can occur when multiple credential helpers are + configured. + + Only erase credential if stored password matches request (or request + omits password). + + This fixes test "helper ... does not erase a password distinct from + input" introduced in aeb21ce22e (credential: avoid erasing distinct + password, 2023-06-13) Signed-off-by: M Hickford .../libsecret/git-credential-libsecret.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/contrib/credential/libsecret/git-credential-libsecret.c b/contrib/credential/libsecret/git-credential-libsecret.c index ef681f29d5b..9110714601e 100644 --- a/contrib/credential/libsecret/git-credential-libsecret.c +++ b/contrib/credential/libsecret/git-credential-libsecret.c @@ -52,6 +52,8 @@ struct credential_operation { #define CREDENTIAL_OP_END { NULL, NULL } +static void credential_clear(struct credential *c); + /* ----------------- Secret Service functions ----------------- */ static char *make_label(struct credential *c) @@ -185,6 +187,7 @@ static int keyring_erase(struct credential *c) { GHashTable *attributes = NULL; GError *error = NULL; + struct credential existing = CREDENTIAL_INIT; /* * Sanity check that we actually have something to match @@ -197,6 +200,20 @@ static int keyring_erase(struct credential *c) if (!c->protocol && !c->host && !c->path && !c->username) return EXIT_FAILURE; + if (c->password) { + existing.host = g_strdup(c->host); + existing.path = g_strdup(c->path); + existing.port = c->port; + existing.protocol = g_strdup(c->protocol); + existing.username = g_strdup(c->username); + keyring_get(&existing); + if (existing.password && strcmp(c->password, existing.password)) { + credential_clear(&existing); + return EXIT_SUCCESS; + } + credential_clear(&existing); + } + attributes = make_attr_list(c); secret_password_clearv_sync(SECRET_SCHEMA_COMPAT_NETWORK, attributes, base-commit: a80be152923a46f04a06bade7bcc72870e46ca09 -- gitgitgadget ``` ## Junio C Hamano, 2023-07-26 17:15 Subject: Re: [PATCH v2] credential/libsecret: erase matching creds only Message-ID: URL: https://gitlist.dev/e/xmqqzg3id27e.fsf%40gitster.g In-Reply-To: ``` "M Hickford via GitGitGadget" writes: > From: M Hickford > > The credential erase request typically includes protocol, host, username > and password. > > credential-libsecret erases a stored credential if it matches protocol, > host and username, regardless of password. > > This is confusing in the case the stored password differs from that > in the request. This case can occur when multiple credential helpers are > configured. > > Only erase credential if stored password matches request (or request > omits password). This is much better. > This fixes test "helper ... does not erase a password distinct from > input" introduced in aeb21ce22e (credential: avoid erasing distinct > password, 2023-06-13) This was still confusing for a patch that does not touch anything in t/, but after re-reading aeb21ce22e and the above a few times, I think I get it. Adding the following , when t0303 is run with GIT_TEST_CREDENTIAL_HELPER set to "libsecret". at the end may help, but perhaps it is too obvious for folks who are ready to actually review this change---presumably they are familiar with how t0303 is to be used and read that without being told from the context? Thanks. ``` ## M Hickford, 2023-07-26 19:44 Subject: Re: [PATCH v2] credential/libsecret: erase matching creds only Message-ID: URL: https://gitlist.dev/e/CAGJzqskUL23Grv84uuFpm0kJFvNQE1PvR%3D67WLDt6bAA2OxmXw%40mail.gmail.com In-Reply-To: ``` On Wed, 26 Jul 2023 at 18:15, Junio C Hamano wrote: > This was still confusing for a patch that does not touch anything in > t/, but after re-reading aeb21ce22e and the above a few times, I > think I get it. Adding the following > > , when t0303 is run with GIT_TEST_CREDENTIAL_HELPER set to > "libsecret". > > at the end may help, but perhaps it is too obvious for folks who are > ready to actually review this change---presumably they are familiar > with how t0303 is to be used and read that without being told from > the context? Good idea, the clearer the better. I'll add this in patch v3. ``` ## M Hickford via GitGitGadget, 2023-07-26 19:46 Subject: [PATCH v3] credential/libsecret: erase matching creds only Message-ID: URL: https://gitlist.dev/e/pull.1527.v3.git.git.1690400814492.gitgitgadget%40gmail.com In-Reply-To: ``` From: M Hickford The credential erase request typically includes protocol, host, username and password. credential-libsecret erases a stored credential if it matches protocol, host and username, regardless of password. This is confusing in the case the stored password differs from that in the request. This case can occur when multiple credential helpers are configured. Only erase credential if stored password matches request (or request omits password). This fixes test "helper (libsecret) does not erase a password distinct from input" when t0303 is run with GIT_TEST_CREDENTIAL_HELPER set to "libsecret". This test was added in aeb21ce22e (credential: avoid erasing distinct password, 2023-06-13). Signed-off-by: M Hickford --- credential/libsecret: erase more carefully Patch v3 adds instructions how to run the fixed test Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1527%2Fhickford%2Ffix-libsecret-v3 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1527/hickford/fix-libsecret-v3 Pull-Request: https://github.com/git/git/pull/1527 Range-diff vs v2: 1: b5d5c3159ad ! 1: 6b3db416c61 credential/libsecret: erase matching creds only @@ Commit message Only erase credential if stored password matches request (or request omits password). - This fixes test "helper ... does not erase a password distinct from - input" introduced in aeb21ce22e (credential: avoid erasing distinct - password, 2023-06-13) + This fixes test "helper (libsecret) does not erase a password distinct + from input" when t0303 is run with GIT_TEST_CREDENTIAL_HELPER set to + "libsecret". This test was added in aeb21ce22e (credential: avoid + erasing distinct password, 2023-06-13). Signed-off-by: M Hickford .../libsecret/git-credential-libsecret.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/contrib/credential/libsecret/git-credential-libsecret.c b/contrib/credential/libsecret/git-credential-libsecret.c index ef681f29d5b..9110714601e 100644 --- a/contrib/credential/libsecret/git-credential-libsecret.c +++ b/contrib/credential/libsecret/git-credential-libsecret.c @@ -52,6 +52,8 @@ struct credential_operation { #define CREDENTIAL_OP_END { NULL, NULL } +static void credential_clear(struct credential *c); + /* ----------------- Secret Service functions ----------------- */ static char *make_label(struct credential *c) @@ -185,6 +187,7 @@ static int keyring_erase(struct credential *c) { GHashTable *attributes = NULL; GError *error = NULL; + struct credential existing = CREDENTIAL_INIT; /* * Sanity check that we actually have something to match @@ -197,6 +200,20 @@ static int keyring_erase(struct credential *c) if (!c->protocol && !c->host && !c->path && !c->username) return EXIT_FAILURE; + if (c->password) { + existing.host = g_strdup(c->host); + existing.path = g_strdup(c->path); + existing.port = c->port; + existing.protocol = g_strdup(c->protocol); + existing.username = g_strdup(c->username); + keyring_get(&existing); + if (existing.password && strcmp(c->password, existing.password)) { + credential_clear(&existing); + return EXIT_SUCCESS; + } + credential_clear(&existing); + } + attributes = make_attr_list(c); secret_password_clearv_sync(SECRET_SCHEMA_COMPAT_NETWORK, attributes, base-commit: a80be152923a46f04a06bade7bcc72870e46ca09 -- gitgitgadget ```