I'm sorry to revive this old topic. I'm astonished that after 8 years, it hasn't been fixed.
I would like to push this up once more. The reason is any user interaction that is not by designed suppose to happen, should be considered a user experience bug and fixed. Crafting a fork bomb by design is out of the scope of this context. One is a malicious conscious creation of a piece of code, while a user misconfiguration is not. It is easily preventable by creating a hardcoded automatic implicit exclusion of the gateway. It is not normal that a user could create a recursive infinite loop with a piece of configuration like this. We are responsible to protect the user in such a case. The issue is not limited to Ubuntu, but to all systems that embedded OpenSSH. It should, therefore, be pushed upstream. I have sent an email to the OpenSSH developer mailing list and it would be welcome if Ubuntu were to request a fix as well. I will do the same request at RedHat. Thank you for your cooperation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025418 Title: Using ProxyCommand w/a non-existant host results in infinite spawns. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1025418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
