4 ms·

getting a connection refused error ssh: connect to host chat2.shazow.net port 22: Connection refused

• shazow 10y ago
  There's a bug that is crashing it, alas. https://github.com/shazow/ssh-chat/issues/166 https://github.com/shazow/ssh-chat/issues/166 Pretty sure the bug is in the autocomplete function, if anyone wants to tackle it. I might disable it for now.
  • deleted 10y ago
    [deleted]
  • smellf 10y ago
    Jerks are also piping /dev/random into it, looks like that may be crashing it.
    • verroq 10y ago
      I guess we can't use ssh for everything.
      • Cpoll 10y ago
        That's not ssh's fault; you can pipe /dev/random into just about anything and get the same result. Rate-limiting isn't the job of the protocol, in this case - it's the job of the chat server application.
      • dvanduzer 10y ago
        The lesson is that you can't authorize indiscriminate access to public services on the internet for single-factor authenticated users. edit: Ugh, Wordy. Shorter: Identity is more than a public key.
        • mikeash 10y ago
          Also, security is more than identity. You still need to be robust against malicious input even if you know exactly who all your users are.
          • dvanduzer 10y ago
            Indeed. The third leg that solves this problem is known to the industry as Accounting.