Nmap Development mailing list archives

Bad ssh keys cause script failure


From: Peter Davis <peter.davis8 () gmail com>
Date: Tue, 15 Sep 2015 14:55:59 +1000

Hello,

It seems that if one an ssh key matches an nmap target and the ssh key is
bad in some way, the nmap script `ssh-hostkey` fails. Obviously not
directly an nmap problem, but thought you might like to know. This is using
a freshly installed 6.87 from homebrew. Relevant traceback is below.

......

Completed Service scan at 14:47, 0.00s elapsed (1 service on 1 host)

NSE: Script scanning 192.168.11.31.

NSE: Starting runlevel 1 (of 2) scan.

NSE: Starting address-info against 192.168.11.31.

NSE: Starting ssh-hostkey against 192.168.11.31:22.

NSE: Starting sshv1 against 192.168.11.31:22.

Initiating NSE at 14:47

NSE: Finished address-info against 192.168.11.31.

NSE: Finished sshv1 against 192.168.11.31:22.

NSE: ssh-hostkey against 192.168.11.31:22 threw an error!

/usr/local/bin/../share/nmap/nselib/ssh2.lua:86: assertion failed!

stack traceback:

[C]: in function 'assert'

/usr/local/bin/../share/nmap/nselib/ssh2.lua:86: in function 'payload'

/usr/local/bin/../share/nmap/nselib/ssh2.lua:199: in function
'fetch_host_key'

/usr/local/bin/../share/nmap/scripts/ssh-hostkey.nse:277: in function
</usr/local/bin/../share/nmap/scripts/ssh-hostkey.nse:267>

(...tail calls...)


Completed NSE at 14:47, 0.01s elapsed

.....


Regards,

Peter
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: