[Diagnostics file leaks passwords]

1 minute ago, bmartino1 said:

To reproduce this is the question. How is the docker getting that data passed to unraid.

 

It's a field in the container's settings, likely being passed with the docker run command on container start.

 

The 'bug' is that ps.txt needs to be sanitized or at the very least warn the user sensitive information may be stored there

[Diagnostics file leaks passwords]

7 minutes ago, bmartino1 said:

and couldn't find my password or mention of it.

 

I've already waned 2 separate users in their threads in General, and verified the same thing was happening in mine. Note that each of them were using separate VPN enabled containers, deluge and sabnzbd

 

Here's one that's still up in the support thread you linked, their password is in plain text in system/ps.txt:

 

 

 

[Diagnostics file leaks passwords]

5 hours ago, bmartino1 said:

where in the diagnostic file did you have aynomize set

 

Not sure what you're referring to, but 'Anonymize diagnostics' was checked before generating

 

5 hours ago, bmartino1 said:

the may be a public key but not private key

 

It's the user name and password in plain text, as shown in my original post. If you're running a VPN enabled docker container, such as @binhex delugevpn in my example - the user name and password are included in the generated diagnostics set in 'system/ps.txt' 

[Unraid OS version 6.9.0-rc2 available]

1 hour ago, Johnster said:

Can anyone please point to an article that explains what spin down/spin up array button does? I only used it to see my HDD temperatures, but I have no ideea how this affects my array. If i press "Spin down" my temp disappears. Is that normal?

It just puts the drives into a low powered sleep mode, which stops the spindle motor - hence the spin down. Any activity directed towards the drive wakes them up and starts the spindle spinning once again - hence the spin up. It's normal for the temperature to not be displayed, as the drives are effectively turned off.

[[6.7.x] Very slow array concurrent performance]

30 minutes to copy 122 files totaling 22MB is a bit maddening, is there a hot fix we can do in the meantime?