-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
RSTP password is shown in log #110891
Comments
Hey there @hunterjm, @uvjustin, @allenporter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) stream documentation |
First, i´m using version 0.64 from "reolink_dev". I have 2x E1 Outdoor and 1 Reolink Video Doorbell WiFi. I can confirm the errors. For some errors, username/password are displayed with *** I think that the error is in the stream worker code. When it comes to the error "Error demuxing stream: [Errno 110] Operation timed out" then the username/password is displayed as a clear name. Some additional information about the error, all come from the Reolink Video Doorbell WiFi.
If the following errors occur, username/password are displayed in plain names:
|
I see this as well in my logs for the Error demuxing stream message. Could we mask the password so it does not show up in the logs? |
do we really have to have our passwords be visible unencrypted in logs? 😕
|
Stream today has code to redact credentials and so the update that needs to happen is for this log line to also use it:
|
The problem
I am using https://github.com/JurajNyiri/HomeAssistant-Tapo-Control to control and monitor my Tapo C125 camera.
When the stream of my camera is not working in HA, I check and found this issue.
I report this issue to JurajNyiri/HomeAssistant-Tapo-Control#519, and the issue was closed due to the log was come from https://www.home-assistant.io/integrations/stream/, not tapo's.
In this screenshot, I use green color to block the username and password of rstp uri, and red box show some password is already become *, so I think there may be some places where the password is not processed.
What version of Home Assistant Core has the issue?
core-2024.2.2
What was the last working version of Home Assistant Core?
core-2024.2.2
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Stream
Link to integration documentation on our website
https://www.home-assistant.io/integrations/stream/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: