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

Re: [PATCH] credential/wincred: store password_expiry_utc

From
M Hickford <mirth.hickford@gmail.com>
Date
May 2, 2023, 09:38 UTC
Message-ID
<CAGJzqsm4LmpYE46v2=y4=A+Och44zaQyzTXQRteX-KNSzA_18g@mail.gmail.com>
In-Reply-To
<xmqqa5yn3d0k.fsf@gitster.g>
On Mon, 1 May 2023 at 23:25, Junio C Hamano <gitster@pobox.com> wrote:
Show 34 quoted lines
>
> M Hickford <mirth.hickford@gmail.com> writes:
>
> > Thanks Johannes for the review and the fix. I'll include it in any patch v2.
> >
> >> But I have to wonder: why even bother with `git-wincred`? This credential
> >> helper is so ridiculously limited in its capabilities, it does not even
> >> support any host that is remotely close to safe (no 2FA, no OAuth, just
> >> passwords). So I would be just as happy if I weren't asked to spend my
> >> time to review changes to a credential helper I'd much rather see retired
> >> than actively worked on.
> >
> > git-credential-wincred has the same capabilities as popular helpers
> > git-credential-cache, git-credential-store, git-credential-osxkeychain
> > and git-credential-libsecret. Any of which can store OAuth credentials
> > generated by a helper such as git-credential-oauth [1]. This is
> > compatible with 2FA (any 2FA happens in browser). Example config:
> >
> >     [credential]
> >         helper = wincred
> >         helper = oauth
> >
> > This patch to store password_expiry_utc is necessary to avoid Git
> > trying to use OAuth credentials beyond expiry. See
> > https://github.com/git/git/commit/d208bfdfef97a1e8fb746763b5057e0ad91e283b
> > for background (I'll add to commit message v2).
>
> So, even though earlier Dscho sounded negative on extending wincred
> helper, are we now on track of enhancing its capabilities?  The v3
> is now queued in my tree and nobody who knows Windows seem to have
> made any comments on either v2 or v3---I am wondering if the lack
> of comments is a good news or no interest.
>
> Thanks.

Thanks to Johannes's fixes for v1, the latest patch should be correct, but it would be prudent to wait for a Windows user to test.

The utility of storing password_expiry_utc is universal to all credential helpers. The latest commit message references the introduction of this attribute (d208bfdfef97a1e8fb746763b5057e0ad91e283b) for background. I repeat the arguments in [1], I hope they are persuasive.

[1] https://lore.kernel.org/git/CAGJzqs=D8hmcxJKGCcz-NqEQ+QDYgi_aO02fj59kQoHZgiW3OQ@mail.gmail.com/
Previous: Junio C HamanoNext: Johannes Sixt
Message 5 of 11 in “credential/wincred: store password_expiry_utc”
  1. credential/wincred: store password_expiry_utcM Hickford via GitGitGadget, Mar 25, 2023
  2. Johannes SchindelinMar 28, 2023
  3. M HickfordMar 30, 2023
  4. Junio C HamanoMay 1, 2023
  5. M HickfordMay 2, 2023
  6. Johannes SixtMay 2, 2023
  7. Felipe ContrerasMay 2, 2023
  8. credential/wincred: store password_expiry_utcM Hickford via GitGitGadget, Mar 30, 2023
  9. Junio C HamanoMar 30, 2023
  10. M HickfordApr 3, 2023
  11. credential/wincred: store password_expiry_utcM Hickford via GitGitGadget, Apr 3, 2023

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.