The new version (https://github.com/matlink/gplaycli/releases/tag/0.2.2) fixes this issue.
A token authentication is now privided. By default, gplaycli will retrieve a token from a server I control, and use it to talk with the Google servers. In that way, username and password are not used anymore. I kept them in the credentials.conf file to let users know which options are available. I hope this version will be added to stretch since it fixes that RC bug, if everyone agrees. Le 13/11/2016 à 10:53, Matlink a écrit : > > Another solution would be to tell gplaycli to fetch the credentials > from a server. In this case, when the credentials are changed, I just > have to change this file on the server and every instance of gplaycli > will fetch this file and have the new credentials. > > Pros: > > * no need to update gplaycli when credentials change > * transparent for users > > Cons: > > * gplaycli is dependent to a server > * the server is aware of every gplaycli instances (privacy issues) > > > > Le 09/11/2016 à 09:53, matlink a écrit : >> I understand. We're looking for a solution that won't remove them and >> prevent anyone except me to change the password. >> >> >> Le 09/11/2016 à 09:43, Paul Wise a écrit : >>> On Wed, 2016-11-09 at 08:20 +0100, Matlink wrote: >>> >>>> there is a potential big issue with providing default credentials >>> The default shared credentials are the main advantage of this package. >>> I wouldn't have any reason to use it without them. >>> > > -- > Matlink - Sysadmin matlink.fr > Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/ > XMPP/Jabber : matl...@matlink.fr > Clé publique PGP : 0x186BB3CA > Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2
signature.asc
Description: OpenPGP digital signature
