6 ms·

Hey everyone, thanks for dropping by the main ssh-chat server (chat.shazow.net). That one is running a fairly old version of the software (/uptime -> 13579h33m2

by shazow 10y ago

Hey everyone, thanks for dropping by the main ssh-chat server (chat.shazow.net). That one is running a fairly old version of the software (/uptime -> 13579h33m20.784837542s). I just deployed the latest Github release on an east-coast server here, please come help test it: ssh chat2.shazow.net Binary releases are available here if you're interested in running your own: https://github.com/shazow/ssh-chat/releases/ https://github.com/shazow/ssh-chat/releases/

xrattlesnake 10y ago
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.
hyh1048576 10y ago
Is chat2 dead? I entered sentence in Chinese and now I can't see anything after login or re-login. And it's so dead that the ssh process has to be killed by a signal 15. ^C and ^D won't work.
- teraflop 10y ago
  ^C doesn't work because the SSH client is passing it through to the remote server (which is normally what you want), not because the client itself is stuck. ssh has a little-known "escape character" feature for situations like this. You can type <ENTER> ~. to tell the client itself to exit, or <ENTER> ~? for a list of other escape commands.
  - jsmthrowaway 10y ago
    It doesn't hurt to mash <ENTER> a few times, either, just to tell ssh that you're serious. I used to have it not work occasionally until I started mashing -- probably because it passed the newline through and I didn't make it to ~ fast enough, so whap-whap-whap ~. is my muscle memory for killing ssh now. This is extremely useful information if you do a lot of work on remote servers, particularly when you restart networking and lock yourself out. You can get your shell back without having to kill the terminal or open another to kill ssh, which I see a lot of people do. It's too bad it's little-known. ~C is useful too so you can alter your forwarding setup (including cancelling open forwards) without dropping the connection.
    - nkurz 10y ago
      It doesn't hurt to mash <ENTER> a few times Do you happen to be an older North Carolinian? I don't think I've heard anyone use "mash" in this sense since being a bewildered Northerner in an NC elementary school in the 70's when a teacher asked me to "mash the lights". Apparently some light switches once used buttons, and "mash" was (and possibly still is) a regionalism for "press". Is it used elsewhere too? Personally I'd use "mash" to describe preparing potatoes, and would need it for brewing beer, but I wouldn't have considered that it might be applicable to escaping from ssh. Although searching now, I see that it also seems to be a term-of-the art for rapid button pressing in video games. And I see that suggestions that it's also used in the West Indies.

by shazow 10y ago

xrattlesnake 10y ago

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.

hyh1048576 10y ago

Is chat2 dead? I entered sentence in Chinese and now I can't see anything after login or re-login. And it's so dead that the ssh process has to be killed by a signal 15. ^C and ^D won't work.

teraflop 10y ago
^C doesn't work because the SSH client is passing it through to the remote server (which is normally what you want), not because the client itself is stuck. ssh has a little-known "escape character" feature for situations like this. You can type <ENTER> ~. to tell the client itself to exit, or <ENTER> ~? for a list of other escape commands.
- jsmthrowaway 10y ago
  It doesn't hurt to mash <ENTER> a few times, either, just to tell ssh that you're serious. I used to have it not work occasionally until I started mashing -- probably because it passed the newline through and I didn't make it to ~ fast enough, so whap-whap-whap ~. is my muscle memory for killing ssh now. This is extremely useful information if you do a lot of work on remote servers, particularly when you restart networking and lock yourself out. You can get your shell back without having to kill the terminal or open another to kill ssh, which I see a lot of people do. It's too bad it's little-known. ~C is useful too so you can alter your forwarding setup (including cancelling open forwards) without dropping the connection.
  - nkurz 10y ago
    It doesn't hurt to mash <ENTER> a few times Do you happen to be an older North Carolinian? I don't think I've heard anyone use "mash" in this sense since being a bewildered Northerner in an NC elementary school in the 70's when a teacher asked me to "mash the lights". Apparently some light switches once used buttons, and "mash" was (and possibly still is) a regionalism for "press". Is it used elsewhere too? Personally I'd use "mash" to describe preparing potatoes, and would need it for brewing beer, but I wouldn't have considered that it might be applicable to escaping from ssh. Although searching now, I see that it also seems to be a term-of-the art for rapid button pressing in video games. And I see that suggestions that it's also used in the West Indies.