I am just about to upload another pre-alphs release to the web server, it should be there in about 10 or 15 minutes.

This update completes Mystic-DOS by adding the ability to run doors from the shell, the ability to snoop other users, and some touch ups in other places.

I consider Mystic-DOS to be complete now so I will probably be leaving it alone unless there are bugs or suggestions.

There is also a new SysOp menu command to snoop a user on another node as well.

AutoHatch has been added to MUTIL but more to come with the event system and hatching via utilities.

There have been some other changes in the backend not worth trying to
explain, but as always if someone notices something or has suggestions let me know.

I am considering a feature lock sometime soon to prepare for a 1.12 stable release, but I am undecided. I'd still like to get a theme revamp in 1.12,
so I have been on the fence.

Also, for those of you using the current "index reader" I would start to look into using the new index reader as I am going to make the cut over sometime
in the near future, probably for A43. So the old one will go away.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 10 Feb 2019, g00r00 said the following...

Also, for those of you using the current "index reader" I would start to look into using the new index reader as I am going to make the cut over sometime in the near future, probably for A43. So the old one will go away.

Already made the change, why when you added extra line's in the last
pre-alpha was oh boy. =D .. But I do have it working for area changes and
index reading etc, thank you for suck a great feature!

Cheers!

|15:|07: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08> |07:|15: |15:|07: |02telnet://|10twinklebbs.net |07:|15:

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

* An ongoing debate between g00r00 and All rages on ...

I am considering a feature lock sometime soon to prepare for a 1.12
stable release, but I am undecided. I'd still like to get a theme
revamp in 1.12, so I have been on the fence.

Works for me !


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet|ssh://cmech.dynip.com |
| |
| vvvvvv Email: fido4cmechSPAM(at)lusfiberBLOCK.net |
| { O O } Home page: http://cmech.dynip.com/homepage/ |
| __m___oo___m__ |
`--| | | |-- -------------------------------------------------'

... The only thing ever lost by politeness is a seat on a crowded bus.
--- GoldED+/W32-MSVC v1.1.5-g20180902 +Mystic 1.12 pa43/W32 2019/02/08 23:45:53
* Origin: FSXNet - Positronium: telnet://cmech.dynip.com (21:2/117)

On 10 Feb 2019 at 02:53p, g00r00 pondered and said...

I am just about to upload another pre-alphs release to the web server, it should be there in about 10 or 15 minutes.

Got it and updated 1/100 and 1/101 just now. Looks very nice indeed :)

This update completes Mystic-DOS by adding the ability to run doors from the shell, the ability to snoop other users, and some touch ups in other places.
I consider Mystic-DOS to be complete now so I will probably be leaving
it alone unless there are bugs or suggestions.

I have been playing with it tonight, love it :) I can see how this will make folks lives easier when providing access to a system they can use these tools?

[snip]

Mystic-DOS Supported Commands
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

ANSI BYE CD CHAT CLS
CONFIG COPY DATE DEL DIR
DISKINFO DOOR EDIT EXIT HELP
FIND KICK MKDIR MOVE MPL
MSG PYTHON RECEIVE RECYCLE REN
RMDIR SEND SNOOP TIME TYPE
UNZIP VER VIEW WHO ZIP

Type HELP or ? [Command] for help on a specific command

[snip]

Question - can a sysop set specific ACS against each command so someone with access to this menu can use some but not all commands or is it a case of all
or nothing? Just curious.

AutoHatch has been added to MUTIL but more to come with the event system and hatching via utilities.

Going to play with this tomorrow. :) Thank you very much for adding this it will make automating some regular hatching of files much easier once I have
set it up.

I am considering a feature lock sometime soon to prepare for a 1.12
stable release, but I am undecided. I'd still like to get a theme
revamp in 1.12, so I have been on the fence.

Mans gotta do what a mans gotta do.. or so they say.

Also, for those of you using the current "index reader" I would start to look into using the new index reader as I am going to make the cut over sometime in the near future, probably for A43. So the old one will go away.

Yeah it's a good idea. I will force this at Agency tomorrow.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Question - can a sysop set specific ACS against each command so someone with access to this menu can use some but not all commands or is it a
case of all or nothing? Just curious.

Its all or nothing, because they have access to your disk drives so everyone must have s255 to use it. It is the only thing in Mystic that has that sort of baked in security level requirement that I can think of.

The non-disk functions should be available as menu commands if you want to make them available to users and wrap a security level around them. Is there a certain way you'd like to be able to use the DOS shell? Like what would you give other users the ability to do?

I could attach configurable security to them if enough people thought it'd be useful, but there would have to be configurable access for certain disk directories and so on too.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 11 Feb 2019 at 09:11a, g00r00 pondered and said...

Its all or nothing, because they have access to your disk drives so everyone must have s255 to use it. It is the only thing in Mystic that has that sort of baked in security level requirement that I can think of.

Gotcha...

Is there a certain way you'd like to be able to use the DOS shell? Like what would you give other users the ability to do?

No nothing comes to mind it was more of a general question when I saw some of the commands I thought yep they are powerful so was unsure if it was an all/nothing kind of thing. And it is, and that's fine.

I could attach configurable security to them if enough people thought
it'd be useful, but there would have to be configurable access for
certain disk directories and so on too.

I think there's validity in setting something up to allow access only to the dir and sub dirs Mystic is running in vs the whole HDD. My 2 cents.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I think there's validity in setting something up to allow access only to the dir and sub dirs Mystic is running in vs the whole HDD. My 2 cents.

I had this idea too, but one issue with that is that if we make it a setting, then the s255 user would have the access to just go in and turn it off! So that is why I just decided not to do anything unless anyone had more feedback.

We'd have to have some way of protecting that particular setting.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 12 Feb 2019 at 12:23p, g00r00 pondered and said...

I think there's validity in setting something up to allow access only the dir and sub dirs Mystic is running in vs the whole HDD. My 2 cent

I had this idea too, but one issue with that is that if we make it a setting, then the s255 user would have the access to just go in and turn it off! So that is why I just decided not to do anything unless anyone had more feedback.

Yep it's not easy is it? probably best to leave as is I guess. I suppose you could set a switch that was only available to turn on/off for someone logged
in locally at the physical box or via SSH using mystic -cfg but if they tried to the same via a session using a MIS server it would not be an option?

That's all I can think.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Yep it's not easy is it? probably best to leave as is I guess. I suppose you could set a switch that was only available to turn on/off for
someone logged in locally at the physical box or via SSH using mystic
-cfg but if they tried to the same via a session using a MIS server it would not be an option?

That would be ideal, but that can only work on Windows unfortunetly. I am
not sure I really have a reliable way to determine if a connection is local.

In other words, in Windows I can always tell but in Unix-based systems, it relies on the local user logging in with -l which I think they often do not.

If I ever end up merging MIS and MYSTIC to the same binary I am going to change it to require the Sysop to always type "mystic local" to login locally while just typing "mystic" will bring up a help screen. I think then it would make sense since I'll always know when its local.

(I've actually already done this merge as a "proof of concept" ... it was one of the things I did during my downtime between A39 and A40)

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 12 Feb 2019, g00r00 said the following...

(I've actually already done this merge as a "proof of concept" ... it
was one of the things I did during my downtime between A39 and A40)

you sneaky hehe

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic
|08[|15bbs|09.|15dreamlandbbs|09.|15org|08]

--- Mystic BBS v1.12 A43 2019/02/06 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 12 Feb 2019, g00r00 said the following...

I had this idea too, but one issue with that is that if we make it a setting, then the s255 user would have the access to just go in and turn it off! So that is why I just decided not to do anything unless anyone had more feedback.

The only thing I could really think of on this is having an s250 co-sysop
user that you want to have some access to this stuff, but not all of it.

We'd have to have some way of protecting that particular setting.

Hmmm... A configuration file, like an ini or cfg with security settings for
the different commands maybe?

Fireball

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: Fireball Express!!! Mystic Edition (21:4/145)

Hmmm... A configuration file, like an ini or cfg with security settings for the different commands maybe?

Maybe, but just like Mystic has an ANSI editor, it also has a text editor so the users could just edit the .ini file to change the settings. We could take away the text editor, but if I had to guess some of the things you'd want to give a Co-SysOp with s250 access to would be the ANSI and text editors.

I like the idea someone (Avon?) had about only allowing any Mystic-DOS settings to be changed from a local login, so that is one potential solution.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 13 Feb 2019 at 06:30p, g00r00 pondered and said...

I like the idea someone (Avon?) had about only allowing any Mystic-DOS settings to be changed from a local login, so that is one potential solution.

Yep twas me... I figure it's one way of knowing what's what.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 13 Feb 2019, g00r00 said the following...

Maybe, but just like Mystic has an ANSI editor, it also has a text
editor so the users could just edit the .ini file to change the
settings. We could take away the text editor, but if I had to guess
some of the things you'd want to give a Co-SysOp with s250 access to
would be the ANSI and text editors.

Dang! Foiled by the internal tools! lol!

I like the idea someone (Avon?) had about only allowing any Mystic-DOS settings to be changed from a local login, so that is one potential solution.

That's also an option. I kind of like it since I doubt anyone's willing to
give real console level access to anyone, but you never know. There's really
no way to make anything completely dumby proof, juts put enough obstacles in the way to make it difficult to mess it up. :)

Fireball

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: Fireball Express!!! Mystic Edition (21:4/145)