• SSH (was: Seg's Fault)

    From Nightfox@VERT/DIGDIST to Jon Justvig on Monday, May 19, 2014 13:07:15
    I experienced my SBBS crashing the last few days after noticing a SSH login attempt. I saw they were trying to login as root, I freaked and took out the SSH port from my forwarding since it didn't get much use anyway. But yeah, when there was a SSH attempt my system would crash. I'm running the 3.16 Linux version of SBBS.

    BBS user accounts are separate from the system user accounts, so unless your BBS has a user with the name root, I wouldn't be worried about that. Even if your BBS did have a user named root, that's still separate from your system root account, and BBSes typically don't have a way to let someone drop to your system shell anyway (unless you configure some kind of doorway to do so).

    In general I think it's good to use (or at least enable) secure protocols like SSH to prevent people from monitoring you and your activity, although I still tend to use telnet or RLogin since that's what most BBSes are configured for.
    I doubt people are very interested in monitoring BBS activity though. I have SSH enabled on my BBS in case there are users who want to use it - And occasionally I have seen some users logged in via SSH.

    Nightfox

    ---
    þ Synchronet þ Digital Distortion BBS - digitaldistortionbbs.com
  • From Jon Justvig@VERT/STEPPING to Nightfox on Tuesday, May 20, 2014 21:56:00
    Nightfox wrote to Jon Justvig <=-

    BBS user accounts are separate from the system user accounts, so unless your BBS has a user with the name root, I wouldn't be worried about
    that. Even if your BBS did have a user named root, that's still
    separate from your system root account, and BBSes typically don't have
    a way to let someone drop to your system shell anyway (unless you configure some kind of doorway to do so).

    I see your point and I should know that by now. For the most part, the system would crash anytime a SSH connection was established. I guess I freaked out since it would crash the board and I wasn't used to it going to the command prompt (on my end) and thought it was seen by a user connecting by SSH. I don't know much about SSH and that's what I thought it was doing. But yeah, wheew, I might open up port 22 again for SSH at a later point.

    In general I think it's good to use (or at least enable) secure
    protocols like SSH to prevent people from monitoring you and your activity, although I still tend to use telnet or RLogin since that's
    what most BBSes are configured for. I doubt people are very interested
    in monitoring BBS activity though. I have SSH enabled on my BBS in
    case there are users who want to use it - And occasionally I have seen some users logged in via SSH.

    That's cool. I'm glad you have users using the SSH port and connecting to your board that way. I should have it opened too. I just need to wait it out and fix the problem that was causing the system to crash (drop to the command line) or perhaps it's a coding problem. I'm unsure at this point. I've been involved with getting my message network going so I haven't had time to pursue the SSH port issue as of late.

    Sincerely,
    Jon Justvig

    ... Gone crazy, be back later, please leave message.
    --- MultiMail/Win32 v0.49
    þ Synchronet þ My Brand-New BBS