{"thread":{"id":"63883","subject":"[RFC v2] git-secure: extend interactive authentication to more Git operations","startedAt":"2025-07-31T09:36:36Z","lastAt":"2025-07-31T09:36:36Z","messageCount":1,"participants":["Victor Duprez"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"523090","messageId":"1753954588-934281@smtp-cli","threadId":"63883","inReplyTo":null,"subject":"[RFC v2] git-secure: extend interactive authentication to more Git operations","fromName":"Victor Duprez","fromEmail":"duprezvictor4@gmail.com","sentAt":"2025-07-31T09:36:28Z","receivedAt":"2025-07-31T09:36:36Z","isPatch":false,"sender":{"key":"duprezvictor4@gmail.com","avatar":null},"body":"Subject: [RFC v2] git-secure: extend interactive authentication to more Git operations\nTo: git@vger.kernel.org\nFrom: Victor Duprez <duprezvictor4@gmail.com>\n\nHello Git community,\n\nFollowing 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.\n\n🆕 What’s changed:\n- Support for more operations: now also covers pull, fetch, and submodule updates.\n- Verifies token validity before proceeding.\n- Shows explicit error messages on authentication failure.\n- English & French READMEs added, with usage examples.\n- Working script and repo here: https://github.com/VictorNafs/git-secure-hub\n\n💬 I would greatly appreciate feedback on:\n- Making this concept native (via optional plumbing commands or flags),\n- Security model consistency with Git’s philosophy,\n- Integration possibilities or risks.\n\nThanks again for your attention and guidance.\n\nBest regards,  \nVictor Duprez\n\n[1] https://lore.kernel.org/git/1753544769-115114@smtp-cli\n\n"}]}