Hi Jordon
Thanks for taking the time to report this bug in Ubuntu.
By just uncommenting that one line you will create a proxy loop - the
gateway.example.com needs to be setup with a ProxyCommand None entry
as well. So its nothing todo with a non-existent host - its just a
misconfiguration IMHO.
Actually I got this:
You don't exist, go away!
ssh_exchange_identification: Connection closed by remote host
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1025418
Title:
Using
And:
/bin/bash: Cannot allocate memory
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1025418
Title:
Using ProxyCommand w/a non-existant host results in infinite spawns.
To
Jordon,
Thank you for your report.
It seems that you have misconfigured the ssh client, and the ssh client
is then calling itself recursively in an infinite loop to fulfil its
proxy as you have configured it.
This is not a vulnerability in ssh, as you aren't crossing a privilege
boundary. You
@racb Setting aside the fact that you think I don't know how to
configure a server or prevent it, the faulty logic is that because you
can fork bomb already this problem doesn't matter and it's not worth it
yeah? I don't know if that's funny or what...
--
You received this bug notification
