SSH Wide Compatability Mode Unsupported [SOLUTION] #792
Comments
|
I think i have the same issue, using the "Wide Compatibility Mode" too, same version of OS and Hydra. Here is my debug data: |
|
A quick search for this and libssh did not reveal the config changed required. I do not have time to work on this for the next weeks so if someone can send a PR this would be great ... |
|
Hello, this issue should be fixed in Kali Linux, as of today, with the latest version of kali-tweaks Steps to follow:
After that, it should work. Please report that the issue is indeed fixed. For the curious, details on the exact issue can be found at: https://gitlab.com/kalilinux/packages/kali-tweaks/-/merge_requests/8#note_1241868100 Thanks! |
vanhauser-thc
changed the title
|
I was told that it still fails, this time with a different error message: So I just updated kali-tweaks so that, in « SSH Wide Compatibility » mode, the legacy MACs are also enabled. This was released in kali-tweaks version For anyone interested to test, same procedure as above to update (steps 1, 2 and 3). Thanks! |
|
Still the same issue, i tried in latest kali. any update on this? regular ssh command words, medusa works, nmap script works, but not hydra. |
|
@chinnidiwakar Did you enable SSH "Wide Compatibility Mode" in Kali? This is enabled via command |
|
yes, the issue was after fixing that only.
i have also tried to add them to config file, that did not help either.
…On Tue, Sep 12, 2023 at 1:34 PM Arnaud Rebillout ***@***.***> wrote:
@chinnidiwakar <https://github.com/chinnidiwakar> Did you enable SSH
"Wide Compatibility Mode" in Kali? This is enabled via command kali-tweaks,
then in the menu Hardening.
—
Reply to this email directly, view it on GitHub
<#792 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLBMHDUNMUQA4YL7FK6YHDX2AJPJANCNFSM6AAAAAAQXMP374>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I ran into this problem with ubuntu |
|
@chinnidiwakar Just to be sure, can you give me the ouput of: Thanks |
|
[image: image.png]
here it is
…On Tue, Sep 12, 2023 at 2:40 PM Arnaud Rebillout ***@***.***> wrote:
@chinnidiwakar <https://github.com/chinnidiwakar> Just to be sure, can
you give me the ouput of:
ssh -G '*' | grep -i '^HostKeyAlgo' | cut -d' ' -f2- | sed 's/,/\n/g' | sort
Thanks
—
Reply to this email directly, view it on GitHub
<#792 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLBMHCGVLAEKPWM6RLHFYLX2ARHLANCNFSM6AAAAAAQXMP374>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@chinnidiwakar Didn't work, there's no image |
|
|
|
Yes it's visible, thanks! I find a bit surprising, as I don't get the same output on my side (also an up-to-date Kali system), I have a few more algos: Can you also share the output of those commands please: Thanks |
|
The only thing different on Kali Wide Compatibility config since the fix is.. Can you please confirm you are getting positive attempts using another SSH bruteforce utility such as crackmapexec? Any additional details for debugging on the target, that would be great. The original target I created the issue still works. |
|
|
|
|
|
@chinnidiwakar Thanks for the feedback. Something doesn't really match in your config though. We have the same config file Are you that you don't have some other config (in Besides, the list of algo proposed by the hydra (last line, |
|
and only this content in ssh_config |
|
Ok... What about your So far I can't explain why the command |
|
|
this is the default kali downloaded and using straight from kali.org website, and the same issue persists in 10 or more other kali's. so i dont even know where the issue is to fix. |
|
The file So please remove the file Also, this file is not Kali's default, what's in |
|
Hi Sorry for delayed Response, and Thanks for Noticing, that config file is a small workaround that i found on the stackoverflow, and forgot to remove it later, as you explained it think it takes precedence and not taking my kali-tweaks modifications, i removed the file and now hydra could crack it just as expected, thanks for your time and support with all these back and forth, i will try to reexecute all the commands and will share the output for future reference. Thanks again. |
Crackmapexec I did the kali twaek |
Description:
Running SSH in "Wide Compatibility Mode" causes hydra not to error out. This is enabled via
kali-tweaks->Hardeningor adding the following to/etc/ssh/ssh_config. The+indicates append to default.Versions
Kali Version 2022.3, Hydra v9.3
Error
Expected behavior
SSH bruteforcing should work correctly in Wide Compatibility mode. CrackMapExec works in the meantime:
The text was updated successfully, but these errors were encountered: