From: Victor Duprez <duprezvictor4@gmail.com>
To: git@vger.kernel.org
Subject: [RFC v2] git-secure: extend interactive authentication to more Git operations
Date: Thu, 31 Jul 2025 11:36:28 +0200 [thread overview]
Message-ID: <1753954588-934281@smtp-cli> (raw)
Subject: [RFC v2] git-secure: extend interactive authentication to more Git operations
To: git@vger.kernel.org
From: Victor Duprez <duprezvictor4@gmail.com>
Hello Git community,
Following up on my initial RFC [1], I would like to submit a v2 of the git-secure concept â a secure wrapper for sensitive Git operations.
ð Whatâs changed:
- Support for more operations: now also covers pull, fetch, and submodule updates.
- Verifies token validity before proceeding.
- Shows explicit error messages on authentication failure.
- English & French READMEs added, with usage examples.
- Working script and repo here: https://github.com/VictorNafs/git-secure-hub
ð¬ I would greatly appreciate feedback on:
- Making this concept native (via optional plumbing commands or flags),
- Security model consistency with Gitâs philosophy,
- Integration possibilities or risks.
Thanks again for your attention and guidance.
Best regards,
Victor Duprez
[1] https://lore.kernel.org/git/1753544769-115114@smtp-cli
reply other threads:[~2025-07-31 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1753954588-934281@smtp-cli \
--to=duprezvictor4@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).