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

[PATCH v2 0/2] http: store credential when PKI auth is used

From
John Szakmeister <john@szakmeister.net>
Date
Mar 12, 2021, 00:48 UTC
Message-ID
<20210312004842.30697-1-john@szakmeister.net>

Here's my second attempt at getting the certificate password into the credential store. I tested from a working PKI setup and found curl--at least reasonable recent versions of it--return CURLE_SSL_CERTPROBLEM:

       CURLE_SSL_CERTPROBLEM (58)
              problem with the local client certificate.
It appears there could be another possible error from curl:
       CURLE_SSL_CONNECT_ERROR (35)
              A  problem  occurred  somewhere  in the SSL/TLS handshake. You
              really want the error buffer and read the message there as it
              pinpoints the problem slightly more. Could be  certificates  (file
              formats, paths, permissions), passwords, and others.

This seems less likely to be a bad client password scenario, so I did not look for this particular error to reject it.

I also added one other small patch to remove the check of a non-empty password before calling credential_store() for proxy_auth, as credential_store() already checks for a non-empty password and gracefully handles it when it doesn't.

-John
John Szakmeister (2):
  http: store credential when PKI auth is used
  http: drop the check for an empty proxy password before approving
 http.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)
-- 
2.30.1
Next: John Szakmeister
Message 1 of 9 in “http: store credential when PKI auth is used”
  1. 0/2 http: store credential when PKI auth is usedJohn Szakmeister, Mar 12, 2021
  2. 1/2 http: store credential when PKI auth is usedJohn Szakmeister, Mar 12, 2021
  3. Junio C HamanoMar 12, 2021
  4. brian m. carlsonMar 12, 2021
  5. Jeff KingMar 12, 2021
  6. John SzakmeisterMar 12, 2021
  7. 2/2 http: drop the check for an empty proxy password before approvingJohn Szakmeister, Mar 12, 2021
  8. Jeff KingMar 12, 2021
  9. John SzakmeisterMar 12, 2021

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.