Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 15829  |
|  Nicholas Boel to Ivan Kovalenko  |
|  Re: Log on restrictions  |
|  13 Nov 24 06:16:58  |
 TZUTC: -0600 MSGID: 4711.mystic@1:154/700 2b99e121 REPLY: 2:5057/53 6733a71b PID: Synchronet 3.20a-Linux master/76fbfb15e Nov 10 202 GCC 14.2.1 TID: SBBSecho 3.21-Linux master/76fbfb15e Nov 10 2024 16:48 GCC 14.2.1 BBSID: PHARCYDE CHRS: UTF-8 4 Hello Ivan, On Tue, Nov 12 2024 12:58:00 -0600, you wrote: > Trying to figure out (if this is ever possible) how to configure > Mystic to allow a sysop (s255) account to log on only via ./mystic - > l , i.e. locally. Browsed the manual, whatsnew and wiki but still > got no clue. While I'm not completely sure on the answer you're looking for.. It's possible this has never been addressed before, because: Why would you want to restrict access to your sysop account - the /only/ account that is able to do anything administrative (of course, if you don't allow sysop access to any other accounts)? Would another possibility be to use "Anonymous Login" or something to where you don't see the sysop's statistics mixed in with the rest of the users? Regards, Nick ... Take my advice, I don't use it anyway. --- SBBSecho 3.21-Linux * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700) SEEN-BY: 90/1 103/705 104/119 105/81 106/201 120/616 123/10 124/5016 SEEN-BY: 128/187 129/215 305 153/757 7715 154/10 30 50 700 203/0 218/700 SEEN-BY: 220/90 221/0 6 226/18 30 44 50 227/114 229/110 111 114 206 SEEN-BY: 229/275 300 307 310 317 400 426 428 470 550 664 700 240/1120 SEEN-BY: 240/5832 266/512 280/464 5003 5006 282/1038 291/111 292/854 SEEN-BY: 292/8125 301/1 320/219 322/757 341/66 234 342/200 396/45 SEEN-BY: 423/120 460/58 256 1124 467/888 633/280 712/848 770/1 902/26 SEEN-BY: 2320/105 3634/12 5020/400 8912 5054/30 5075/35 PATH: 154/700 10 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]