Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 15,233 of 16,010    |
|    g00r00 to Tim Woodland    |
|    Re: Not a valid PKT    |
|    17 Jan 23 22:52:38    |
      TID: Mystic BBS 1.12 A49       MSGID: 1:129/215 5b0a2f75       REPLY: <4bc20e2e-5533-41c9-8042-6858f8c26443n@googlegroups.com> 07a2d412       TZUTC: -0500        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)       SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10       SEEN-BY: 123/120 131 129/215 305 153/7715 154/10 30 40 50 700 218/700       SEEN-BY: 218/840 220/70 90 221/6 226/17 18 30 70 100 227/114 201 229/110       SEEN-BY: 229/111 112 113 114 206 275 307 310 317 400 424 426 428 452       SEEN-BY: 229/470 550 664 700 250/5 8 266/512 267/800 280/464 282/1038       SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200       SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12       PATH: 129/215 154/10 770/1 317/3 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca