You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This backend use the crypt function, here an example where -d force the use of crypt encryption when generating the htpasswd file:
this application is running with root permissions
has access to all containers
has access to the base system
Please at least have your documentation not run people right into the most insecure encryption they could use.
Maybe rather show how to do it with auth on the frontend webserver if it's too hard to change in lxc?
The text was updated successfully, but these errors were encountered:
I don't see any security problem in using crypt to store passwd here. If your lxc host is compromised by an attacker (and he can read the htpasswd file) reverse the encryption to retrieve the lwp password is the less dangerous thing that the attacker can do.
Hi,
in the readme it says:
This backend use the crypt function, here an example where -d force the use of crypt encryption when generating the htpasswd file:
Please at least have your documentation not run people right into the most insecure encryption they could use.
Maybe rather show how to do it with auth on the frontend webserver if it's too hard to change in lxc?
The text was updated successfully, but these errors were encountered: