Package: gplaycli Followup-For: Bug #823004 Hi Matlink,
the way gplaycli is shipped makes it problematic for several reasons: - Sharing account passwords violates Google's ToS - Someone could abuse that account for spamming via gmail, prompting Google to disable the account - Everyone can change the password (just checked) breaking every installation of gplaycli - It probably makes it easier to track gplaycli users (probably more problems if I'd dig more) So the right approach must be: Use debconf to ask for google account credentials (no defaults), then generate the Android ID by some other means. AFAICS this currently means that another tools needs to be included/packaged to generate this. You probably know better what the general approach is, if you could outline them I'd be more than happy to help with implementing this. Bumping the bug severity accordingly. Regards, Lee -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (101, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
