Joe Testa

It seems that the ssh-audit process is waiting for an incoming client connection. Try connecting to it with `ssh -p 2222 x@localhost`. > Does it work as intended in the...

> I have to ensure with you that the need of a running OpenSSH daemon is not among the prerequisites When you use the `-c` option, that tells ssh-audit to...

> Something triggers [Errno 98] Address already in use there but not > with OpenSSH commands. What can it be? I don't know what is causing that. But it doesn't...

@Ricky-Tigg : If I'm reading your last post correctly, you ran `ssh-audit -dvc` twice on the same machine? If so, then the first instance successfully bound to 2222/tcp, and the...

> Here freezing, This is normal & correct behavior. When you use `-c`, the tool acts as a server instead and waits for an SSH client to connect. When this...

@Ricky-Tigg : Are you still experiencing issues with using client scanning?

That output looks correct. ssh-audit is listening for an incoming client connection on port 2222 on both IPv4 and IPv6. Now what happens when you run "ssh ***@***.*** -p 2222"...

Github censored the SSH connection string I wrote, because it appeared to be an e-mail address. Try connecting to ssh-audit with "x[at- sign]localhost".

I meant: in one window, run: ssh-audit.py -c -p 2222 Then, in another window, run: ssh x[at-sign]localhost -p 2222

Looks like it worked correctly. The ssh-audit process successfully responded to your client connection.