I have been noticing an issue with 3.17 Synchronet builds for Windows lately. When one user is logged on via SSH, but another SSH connection comes in with an error (say, the many bots that come in with "SSH Read failure" or "SSH Write failure"), the original user gets booted.

What's worse, this also happens when the offending bot is in ip.can.

When the existing, legitimately logged-in session gets booted, the error "Node x !ERROR -1 receiving on Cryptlib session" is thrown.

I've been seeing a MASSIVE increase in SSH bot attempts recently, so I don't know if this issue in Synchronet is new or if it is just something that I didn't notice until now. (Though I must say, I exclusively use SSH to connect to my BBS and have logged in over 2000 times in sometimes very lengthy
sessions over the last couple years; my first disconnect due to this issue was only last week.)

Is this indeed an issue for development or is there perhaps something I did wrong? I only just started playing around with the latest builds, and though I thought I got all the config changes or new/changed files, it's very possible (likely?) I'm the one who missed something.

-J

---
þ Synchronet þ Basement Theory BBS þ basement.synchro.net

Re: SSH Error Kicks All Off
By: Josh Ramsey to All on Thu Apr 13 2017 11:40 pm

I have been noticing an issue with 3.17 Synchronet builds for Windows lately. When one user is logged on via SSH, but another SSH connection comes in with an error (say, the many bots that come in with "SSH Read failure" or "SSH Write failure"), the original user gets booted.

What's worse, this also happens when the offending bot is in ip.can.

When the existing, legitimately logged-in session gets booted, the error "Node x !ERROR -1 receiving on Cryptlib session" is thrown.

I've been seeing a MASSIVE increase in SSH bot attempts recently, so I don't know if this issue in Synchronet is new or if it is just something that I didn't notice until now. (Though I must say, I exclusively use SSH to connect to my BBS and have logged in over 2000 times in sometimes very lengthy
sessions over the last couple years; my first disconnect due to this issue was only last week.)

Is this indeed an issue for development or is there perhaps something I did wrong? I only just started playing around with the latest builds, and though I thought I got all the config changes or new/changed files, it's very possible (likely?) I'm the one who missed something.

Thanks for the problem report. I (or Deuce, hopefully) will try to reproduce and fix if there is in fact an issue.

digital man

Synchronet "Real Fact" #38:
Synchronet first supported Windows NT-based operating systems w/v3.00b (2000). Norco, CA WX: 61.2øF, 40.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net