Subj : Re: Not a valid PKT
To   : Tim Woodland
From : g00r00
Date : Tue Jan 17 2023 10:52 pm

 TW> Finally, I recursively changed the owner of the Mystic directory and
 TW> files to root leaving the sysop group unchanged.  This worked, no
 TW> errors.  I now am trying to determine what the correct permission
 TW> settings for the directories and folders should be so 
 TW> that I can run Mystic as the sysop user as the owner and group so that
 TW> root is not exposed.  Is there a way to give the sysop user permissions
 TW> to the ethernet ports so Mystic can use the IP ports when running as the
 TW> sysop user?

Your files should always be owned by the user and never root.  So the chown -R user:user /mystic is the right approach to take, which it sounds like you've done.

You can set Linux to allow binding on ports less than 1024 if you want to.  Google is your friend there or maybe someone here can comment more on this method?  It probably should be a topic on the Wiki if its not.

You can also port forward port 23 to port 2323 for example and have Mystic listening on that port.

You can also run "sudo ./mis server" and Mystic will change from root user to the owner of the binaries, after it binds the ports.

To see the latter in action you can start with "sudo ./mis server" and then telnet in.  Export a message and while you're at the protocol selection prompt, look in the node's temp directory at the exported message.  It will be owned by the BBS user that owns mystic and not root, even though you started the service as root.

.... Help! I can't find the "ANY" key.

--- Mystic BBS v1.12 A49 2023/01/17 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.