git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Paul Jolly <paul@myitcv.io>
To: git@vger.kernel.org
Subject: git-credential-libsecret not prompting to unlock keyring
Date: Wed, 12 Sep 2018 13:43:51 +0100	[thread overview]
Message-ID: <CACoUkn4Q_tJW=Gn7i_fSbwm9sw2Me_KPv_Pq4eUD+cOXd1tnqQ@mail.gmail.com> (raw)

Hi,

For some reason today, after an apt update, my combination of GNOME
keyring and git-credential-libsecret stopped working. Stopped working
in so far as I am no longer prompted by GNOME keyring to unlock my
keyring, instead I get prompted for the password that git is looking
for.

Trace output below; would appreciate any pointers.

Many thanks

==========

$ GIT_CURL_VERBOSE=1 GIT_TRACE=1 git push
13:38:59.324799 git.c:415               trace: built-in: git push
13:38:59.325070 run-command.c:637       trace: run_command:
GIT_DIR=.git git-remote-https origin
https://github.com/myitcv/go-modules-by-example
* Couldn't find host github.com in the .netrc file; using defaults
*   Trying 192.30.253.113...
* TCP_NODELAY set
* Connected to github.com (192.30.253.113) port 443 (#0)
* found 133 certificates in /etc/ssl/certs/ca-certificates.crt
* found 399 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
*        server certificate verification OK
*        server certificate status verification SKIPPED
*        common name: github.com (matched)
*        server certificate expiration date OK
*        server certificate activation date OK
*        certificate public key: RSA
*        certificate version: #3
*        subject: businessCategory=Private
Organization,jurisdictionOfIncorporationCountryName=US,jurisdictionOfIncorporationStateOrProvinceName=Delaware,serialNumber=5157550,C=US,ST=California,L=San
Francisco,O=GitHub\, Inc.,CN=github.com
*        start date: Tue, 08 May 2018 00:00:00 GMT
*        expire date: Wed, 03 Jun 2020 12:00:00 GMT
*        issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert
SHA2 Extended Validation Server CA
*        compression: NULL
* ALPN, server accepted to use http/1.1
> GET /myitcv/go-modules-by-example/info/refs?service=git-receive-pack HTTP/1.1
Host: github.com
User-Agent: git/2.19.0
Accept: */*
Accept-Encoding: deflate, gzip
Accept-Language: en-GB, *;q=0.9
Pragma: no-cache

< HTTP/1.1 401 Authorization Required
< Server: GitHub Babel 2.0
< Content-Type: text/plain
< Content-Length: 60
< WWW-Authenticate: Basic realm="GitHub"
< X-GitHub-Request-Id: EF1E:073A:6C8091:C2DB67:5B9908E8
< X-Frame-Options: DENY
<
* Connection #0 to host github.com left intact
13:39:05.084588 run-command.c:637       trace: run_command:
'/home/myitcv/dev/git/contrib/credential/libsecret/git-credential-libsecret
get'
Password for 'https://myitcv@github.com':

             reply	other threads:[~2018-09-12 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 12:43 Paul Jolly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-12 12:47 git-credential-libsecret not prompting to unlock keyring Paul Jolly
2018-09-13  9:26 ` Paul Jolly

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACoUkn4Q_tJW=Gn7i_fSbwm9sw2Me_KPv_Pq4eUD+cOXd1tnqQ@mail.gmail.com' \
    --to=paul@myitcv.io \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).