pwnesia / ssb Goto Github PK

I'm sorry for writing here but it was the only way to contact you,
You are good in the cybersecurity field? Then you can write for us about your own tool on GitHub and the use of it.
Your article will be published with your name and a link to your website and social media accounts if you want. Please reply to us at Email: kalitutwrite @ gmail.com
Walid Salame
kalitut .com
Twitter:@xKaliSec

With -p22

WithOUT -p22

Even tho the port is same (in the info section) the password didnt show up until i added the -p22

I went through process but running it on Ubuntu isnt cleared. Do we have to install any dependencies?

root$:~/ssb# go run main.go
main.go:3:8: cannot find package "ktbs.dev/ssb/internal/runner" in any of:
/usr/lib/go/src/ktbs.dev/ssb/internal/runner (from $GOROOT)
/root/go/src/ktbs.dev/ssb/internal/runner (from $GOPATH)

miss_lacoste97) on Snapchat

Bedo

I just want the ability to read passwords from stdin. Ive tried -w - , no -w, nothing has worked.

it would be cool if we could supply a username list to be iterated with the password list.

Just asking if you could add a feature to bruteforce the user from a wordlist.

Hello,
Thank you for this useful tool. Here is the problem I'm facing.

Client and server have to agree on a cipher among other things, but I'm trying to test a server and I get the following errors.
[ERR] Failed 'admin': ssh: handshake failed: ssh: no common algorithm for client to server cipher; client offered: [[email protected] [email protected] aes128-ctr aes192-ctr aes256-ctr], server offered: [aes128-cbc 3des-cbc aes192-cbc aes256-cbc].

The problem with this is that I have created a ~/.ssh/config file and copied it into the [/etc/ssh_config] and also into /etc/ssh/ssh_config included in the file all available ciphers that are needed.

My understanding is that ssh prioritize the command line options, then the personal directory config file, then the global config file in the /etc directory.

Here is the content of these config files:

Ciphers 3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],[email protected]
MACs hmac-sha1,hmac-sha1-96,hmac-sha2-256,hmac-sha2-512,hmac-md5,hmac-md5-96,[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
HostKeyAlgorithms ssh-ed25519,[email protected],[email protected],[email protected],ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
KexAlgorithms diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,curve25519-sha256,[email protected],[email protected]

When I directly invoke do ssh it works without any problem, and if I use the [-G] switch the ssh command prints out the current configurations which does indeed show the content the config files above including all cipher entries.

My question is, why does ssb tool show the errors above (of the missing ciphers) even though ssh is configured to use these ciphers available at the remote server?

I may be missing somehting here, or maybe the tool calls ssh in a different manner that does not allow it to load the config file.

Please advice,
Thanks

Ini kenapa ya? ada log kayak gitu apa bisa ganti method atau ciphernya manual?