Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't require plaintext password #28

Open
pixelherodev opened this issue Aug 26, 2019 · 1 comment
Open

Shouldn't require plaintext password #28

pixelherodev opened this issue Aug 26, 2019 · 1 comment

Comments

@pixelherodev
Copy link

Storing the password in plain text even just on the local computer is problematic, but requiring it in plaintext on a 3rd-party site (home.mycroft.ai) is completely unacceptable.

@iointerrupt
Copy link

iointerrupt commented Oct 12, 2021

It looks like ultimately the credentials are used by the pianobar stored locally ~/.config/pianobar/config. Afterwards the skill only uses it to determine if pianobar exits abnormally due to login error.

An advanced user might just modify the ~/.config/pianobar/config file themselves, or if you do use the home.mycroft.ai to setup the credentials, there wouldnt be a need to store it in constantly in Mycroft.AI settings file (or in home.mycroft.ai) afterwards. If the user changes their Pandora credentials, they can just retype the username and password in the MyCroft.ai UI and when the device finally updates the configuration from the web, it could "blank" out those values in the mycrofts config file. The check that it does to validate the username and password are blank doesnt need to be there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants