Joe Testa

@egberts : Thanks for posting this. I added this link to the project's wiki. I think that's a good long-term home for it rather than as an issue. Thanks again!

@zomfg: At long last, I've finally checked in a fix for this issue! (See https://github.com/jtesta/ssh-audit/commit/263267c5ad013d314574fcd9bc6a744699e226c5.) If you have an opportunity to give it a try, please let me know how...

Is the target host available on the public Internet? If so, I'd like to test against it. Could I get the host/IP? You could e-mail it to me at jtesta...

@zomfg : Thanks for the quick response! I updated the `master` branch with a fix for the built-in policies. Might you be able to test it again?

Supporting multiple CA types per individual host key for _built-in_ policies wasn't part of the plan here. The primary goal was to support _custom_ policies with mixed host key/CA key...

I just realized that the original issue (and title) do talk about the built-in policies. I suppose at some point along the way, I re-framed it in my mind in...

Sure thing! And thanks for reporting this, and thanks for helping test!

@BjoernAkAManf : can you reproduce this problem against a host available on the public Internet? If so, what is its hostname/IP? Otherwise, can you describe the server software & configuration...

@BjoernAkAManf : I tested the `master` version of ssh-audit against the latest version of Apache MINA SSHD (v2.10.0 as of this writing), and it appears to work (see below). So...

Closing this issue since #170 tracks the goal more appropriately.