5 ms·
Was wondering what the limits are on this service - turns out they quite sensibly restrict the number of shells allowed per source IP address. This script shows
by gertruded 4y ago
Was wondering what the limits are on this service - turns out they quite sensibly restrict the number of shells allowed per source IP address. This script shows it starts refusing new SSH sessions after a few connections back to itself:
#!/usr/bin/expect
set timeout -1
spawn torsocks ssh root@segfault.net
while (true) {
expect " password:"
send "segfault\n"
expect "\[~]"
send "gsocket -s NzdlMWQxNGQM ssh root@segfault.net\n"
expect "t\])? "
send "yes\n"
}
Eventually starts showing this in response:
[ERROR]
--> You (172.22.0.21) have to many servers running
--> Read https://www.thc.org/segfault/youcheapfuck
--> Contact us on Telegram: https://t.me/thorg
Connection to 127.31.33.7 closed.
Also their Tor hidden service currently seems to be inaccessible. Perhaps there's a hard limit on the number of connections via that route, given that one can't restrict per any individual source due to the design of Tor.