git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC v2] git-secure: extend interactive authentication to more Git operations

From
VDVictor Duprez <duprezvictor4@gmail.com>
Date
Jul 31, 2025, 09:36 UTC
Message-ID
<1753954588-934281@smtp-cli>
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
Message 1 of 1 in “[RFC v2] git-secure: extend interactive authentication to more Git operations”
  1. Victor DuprezJul 31, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.