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

Securing Passwords #352

Open
jwiesel opened this issue Feb 16, 2025 · 2 comments
Open

Securing Passwords #352

jwiesel opened this issue Feb 16, 2025 · 2 comments

Comments

@jwiesel
Copy link

jwiesel commented Feb 16, 2025

Hi @meatpiHQ ,
thanks for providing your great devices and open source firmware!

Working with it for a bit now I realized that passwords are not protected in the current (4.04) firmware.

  1. User interface: The passwords (e.g. WiFi, MQTT, battery alert) are shown as normal text fields () instead of passwords (<input type=password)
  2. API: The /check_status endpoint contains the passwords in free text as well. It would be great to
    a. either remove / redact them from the api-endpoints
    b. or add a feature to enable authentication (e.g. HTTP-based with username + password) when accessing the config data
@meatpiHQ
Copy link
Owner

Hey @jwiesel Thanks for the suggestions.

User interface: The passwords (e.g. WiFi, MQTT, battery alert) are shown as normal text fields () instead of passwords (<input type=password)

I'll include this in the next release.

API: The /check_status endpoint contains the passwords in free text as well. It would be great to
a. either remove / redact them from the api-endpoints
b. or add a feature to enable authentication (e.g. HTTP-based with username + password) when accessing the config data

I'll have to look into the best way to go about it.

@jwiesel
Copy link
Author

jwiesel commented Feb 20, 2025

Thanks a lot!

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