Comment 3 for bug 1940907
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: gist-paste command is too old and can no longer authenticate | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Hi,
it seems that the individual change to overcome
https:/
would be
https:/
But a bit more wide-reaching the old auth flow in general is also deprecated and going away (depending on your account type) already.
Therefore one most likely also wants all of:
https:/
Because without the new Auth flow it seems logins via the tool are failing now as well:
Old:
gist-paste --login
Obtaining OAuth2 access_token from github.
GitHub username: ...
GitHub password:
Traceback (most recent call last):
...
New:
gist-paste --login
Requesting login parameters...
Please sign in at https:/
and enter code: XXXX-YYYY
Success! https:/
root@i:~# gist-paste -f test -p -d 'test'
(type a gist. <ctrl-c> to cancel, <ctrl-d> when done)
Foo
https:/
And yes those two changes are in v6.0 and later which matches Ubuntu 21.04 and later.
I'm not sure if this is more an SRU [1] or an item for the newly re-forming backports team [2].
I'd wonder if there are use cases left that still work fine in the current version and that might be broke/changed by upgrading - if that is the case then more backports. If not then an SRU might apply indeed.
P.S. I was only triaging this, but not working on it. So anyone else that comes by, feel free to work on it - there will be no collision with me :-)
[1]: https:/
[2]: https:/