Snychronet Consideration

ThunderRush · 2013-05-23 13:14:48

Not sure if this is the right subforum, but hey, I'll give it a shot.

So, after I bought my new Server and out down a BBS, I had to think about some security considerations. Problem is - I do not want to let my users use telnet. SSH would be prefered.

My ususal SSH Server runs on a different port, and the BBS runs on the normal one. How could I streamline the process - i.e. no user authentication for SSH, directly into the BBS system? Does anyone already have experience with Synchronet, how could I do that?

qinohe · 2013-05-23 14:05:56

I don't have experience with BBS, I looked at it for a minute!
Use keys create a group sshusers make your users a member.
Share the key with your users.
Or is this not what you mean?

ThunderRush · 2013-05-25 12:31:29

Not really, since Synchronet opens a port for SSHing, but I do not have direct control over the config, as it seems.

qinohe · 2013-05-25 13:21:02

Huh, is that your own server with BBS on it or not?

edit; Well I didn't add this at first, and I think you read it
Because on the site it says;

Question:
What inbound ports do I need to open in my firewall?
Answer:
Depends on which Synchronet servers and services you wish to make available to Internet clients and which ports you have configured those servers and services to listen on.
The default Synchronet installation enables servers and services on the following ports: Protocol TCP UDP Comments
Telnet 23 - For Telnet logins (highly recommended)
SSH 22 - For SecureShell logins (recommended)

And I take for granted you have access to the config files!
Why wouldn't you have access to the config files?, if it's your server!

Last edited by qinohe (2013-05-25 16:28:36)

Arch Linux

#1 2013-05-23 13:14:48

Snychronet Consideration

#2 2013-05-23 14:05:56

Re: Snychronet Consideration

#3 2013-05-25 12:31:29

Re: Snychronet Consideration

#4 2013-05-25 13:21:02

Re: Snychronet Consideration

Board footer