> The code in sshd where the response is composed doesn't know what the
> reason for the failure is. I suspect thid dates back to the original
> Protocol 1 code becuase Protocol 1 didn't (I think) have a reason field.
> This passes the reason back up the stack and sends it to the client.
Sorry fo
On Wed, Nov 23, 2016 at 01:35:17PM -0500, Jiri B wrote:
> I was using ssh socks5 tunnel (-D) today and I saw many:
>
> channel 4: open failed: administratively prohibited: open failed
>
> messages. It seems non-resolvable hostnames on my gw (ie. end of ssh
> socks5 tunnel) is passed to clie
I was using ssh socks5 tunnel (-D) today and I saw many:
channel 4: open failed: administratively prohibited: open failed
messages. It seems non-resolvable hostnames on my gw (ie. end of ssh
socks5 tunnel) is passed to client as "prohibited" event.
This seems odd and confusing. GW is an ol
3 matches
Mail list logo
