Tag Info

New answers tagged

1

I encountered this error when I was forwarding ports with a full domain name instead of localhost: ssh -L 5900:host.name.com:5900 x11vnc The port was being opened only for localhost, so to accept connections with a fully qualified name, I had to add a binding port description: ssh -L *:5900:host.name.com:5900 x11vnc which would allow connections from ...


0

We encountered a similar use-case: automatically creating demo users with awful passswords, bypassing all password policies. Without further ado, here's a nasty-but-works hack based on the mailing list suggestion: Bourn shell function # example: set_password_insecure sybil magic # $1: username # $2: password set_password_insecure() { if [ -z "$1" ]; ...



Top 50 recent answers are included