| Summary: | Mistake in config can result in fork bomb | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | petoju | ||||
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED DUPLICATE | ||||||
| Severity: | enhancement | ||||||
| Priority: | P5 | ||||||
| Version: | 8.1p1 | ||||||
| Hardware: | Other | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 3057 *** closing resolved bugs as of 8.6p1 release |
Created attachment 3343 [details] ssh_config causing fork bomb When writing ssh_config, an innocuous mistake in ssh_config leads to a fork bomb. One example is this config, use it when connecting to any host: Host proxy Hostname doesnotmatter.example.com Host * ProxyJump proxy OpenSSH client tries to connect to the proxy first. To connect to the proxy, it has to connect to the very same proxy. It could be more complicated, but the issue is in the cycle. Why is it annoying: one can effectively kill own system like this by mistake. No warning is provided. What could OpenSSH do about it: warn that there is a cycle, recommend excluding "proxy" from ProxyJump and bail out.