TZUTC: -0600
MSGID: 4713.mystic@1:154/700 2b9be09b
PID: Synchronet 3.20a-Linux master/2e47ac987 Nov 14 202 GCC 14.2.1
TID: SBBSecho 3.22-Linux master/2e47ac987 Nov 14 2024 01:26 GCC 14.2.1
BBSID: PHARCYDE
CHRS: ASCII 1
NOTE: slrn/pre1.0.4-9 (Linux)
Hello Ivan,

On Thu, Nov 14 2024 06:48:22 -0600, you wrote:

> Well, not completely, I want to restrict s255 accounts from logging on
> remotely only, they shall still be able to log on locally. Tried to edit
> the prelogin menu, hoping there could be a way to tell the difference,
> but no luck.

I'm not sure it is currently possible.

If you explain your situation a bit better, I may be able to suggest some kind
of workaround.

Above, you say "accounts". Do you plan on adding more than one full sysop
accounts? If this is the case, you can use s250 for message and file area
sysops, rather than giving them full sysop access.

Or are you just a security junkie, and afraid that someone might hack the
sysop account's password /and/ the sysop access password?

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 90/1 104/119 105/81 106/201 120/616 123/10 128/187 129/215
SEEN-BY: 129/305 153/757 7715 154/10 30 50 700 218/700 840 220/90
SEEN-BY: 221/1 6 360 226/18 30 44 50 227/114 229/110 111 114 206 275
SEEN-BY: 229/300 307 310 317 400 426 428 470 550 664 700 266/512 280/464
SEEN-BY: 282/1038 291/111 292/854 301/1 320/219 322/757 335/364 341/66
SEEN-BY: 341/234 342/200 396/45 460/58 633/280 712/848 770/1 902/26
SEEN-BY: 2320/105 3634/12 5075/35
PATH: 154/700 10 221/6 229/664 426