You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kw...@apache.org on 2026/09/15 12:55:02 UTC

(maven-site) branch feature/git-credential-helpers updated (4d4f7ab6 -> 0b9a9f16)

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a change to branch feature/git-credential-helpers
in repository https://gitbox.apache.org/repos/asf/maven-site.git


 discard 4d4f7ab6 Document support for Git Credential helpers for master password
     new 0b9a9f16 Document support for Git Credential helpers for master password

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (4d4f7ab6)
            \
             N -- N -- N   refs/heads/feature/git-credential-helpers (0b9a9f16)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/markdown/guides/mini/guide-encryption-4.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


(maven-site) 01/01: Document support for Git Credential helpers for master password

Posted by kw...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch feature/git-credential-helpers
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit 0b9a9f16df2bd9dd18b75720339701d4f4d55036
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Tue Sep 15 14:51:19 2026 +0200

    Document support for Git Credential helpers for master password
    
    Requires Maven 4 containing a release of plexus-sec-dispatcher including
    https://github.com/codehaus-plexus/plexus-sec-dispatcher/commit/626b42ed5cd488886119184795ba9433717b8330
---
 content/markdown/guides/mini/guide-encryption-4.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/markdown/guides/mini/guide-encryption-4.md b/content/markdown/guides/mini/guide-encryption-4.md
index 04299e61..f18d425a 100644
--- a/content/markdown/guides/mini/guide-encryption-4.md
+++ b/content/markdown/guides/mini/guide-encryption-4.md
@@ -59,6 +59,7 @@ This is the list of implementations (in parentheses the format of the `source`):
 4. [GnuPG Agent](https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html) (`gpg-agent:<agentSocketPath>(?non-interactive)`), requires one manual input per user session. The default agent socket path is `.gnupg/S.gpg-agent` within the user's home directory.
 5. [Pinentry](https://www.gnupg.org/related_software/pinentry/index.html) (`pinentry-prompt:<pinentry-binary-path>`), requires manual input of the password every time a decryption is required. The path should specify the absolute location of the pinentry binary to be used. The one used by GnuPG Agent can be found in `~/.gnupg/gpg-agent.conf` in property `pinentry-program`.
 6. 1Password CLI (`onepassword:<1Password Secret Reference URI>`), looks up secret values from a 1Password vault leveraging the [1Password CLI](https://developer.1password.com/docs/cli/get-started). The [1Password Secret Reference URI](https://developer.1password.com/docs/cli/secret-reference-syntax) always starts with `op://`.
+7. Git Credential helpers (`git-credential:<helper-name>?url=<url>`), uses a [git credential helper binary](https://git-scm.com/docs/gitcredentials) to retrieve the password. The given `<url>` must be an absolute URL (consisting out of `https://`, some host and a path) identifying the master key (it does not need to resolve or return something). There is a list of common helpers at <https://git-scm.com/doc/credential-helpers>.
 
 One has to pick a suitable source depending on the security and ease-of-use requirements.