That's totally fine. I am hopefully leaving work early today so may get them in place in the coming hours.. then it's just a waiting game I
guess.

Yep, sounds great. I just finished work and I am now off until Jan 2nd. I couldn't be more excited to get a vacation.

On the box that the crash happened I am running four instances of MIS
now.

That is awesome! I can't thank you enough for how much Mystic gets pushed because of your setup, and how patient you are when a hard to get serious bug pops up!

The memory dump log should (hopefully) estimate an actual line of code or location where the error happens which will obviously be a great way to pinpoint issues! It will also trap memory leaks too.

--- Mystic BBS v1.12 A37 2017/12/21 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/22/17, g00r00 pondered and said...

That's totally fine. I am hopefully leaving work early today so may g them in place in the coming hours.. then it's just a waiting game I guess.

Yep, sounds great. I just finished work and I am now off until Jan 2nd.
I couldn't be more excited to get a vacation.

You and me both. I'm off until (almost embarrassed to say this) 25 Jan as
it's our summer over here so this is the main holiday season. I'm hopeful to
be able to spend a bit more time on BBS during this period. My wife probably thinks I already spend too much time on it as it is! :)

On the box that the crash happened I am running four instances of MIS now.

That is awesome! I can't thank you enough for how much Mystic gets
pushed because of your setup, and how patient you are when a hard to get serious bug pops up!

The memory dump log should (hopefully) estimate an actual line of code or location where the error happens which will obviously be a great way to pinpoint issues! It will also trap memory leaks too.

Oh you're most welcome. I enjoy it and it's fun to collaborate on this
project with you (and the rest of the gang too :))

Well as I write this it's 1.28pm on a Sat here and I am soon to mow some
lawns in the hot sun. I did push things today and set about hatching 2 x
files (ANSI art packs) to the FSX_ARTS echo this morning. Both files were 30 megabytes plus and this was set in motion around 8.20am this morning. By the time it seems all nodes had been polled and/or binkP pulled the files it was after 1pm when MUTIL next tried to run *but* hit the waiting for busy nodes issue.

So I found an echomail\in full of packets I could run the import and toss process on when I checked just now. I did not run fidopoll killbusy before doing this, and it seems did not need to. curious.

I had shut the server down and copied all logs and .mem files to a temp directory before doing so. I also checked the semaphore directory and could not find any echomail.in waiting etc. just the mis.bsy semaphore.

I had a quick look in echomail\out\fidonet and could not see any *.bsy files before running the overdue toss.

So I have ziped up all logging along with the extra mutil toss for good
measure into a file for you.

The key this in this instance was nodes were busy for a long time receiving large files via BinkP or Fidopoll.. but other than that I'm not sure why the MUTIL session seemingly fired OK after a massive file distribution had
finished (check me on that) and then said nodes were busy?

Anywhoo hopefully this may help squash something :)

Best, P

--- Mystic BBS v1.12 A37 2017/12/21 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I had shut the server down and copied all logs and .mem files to a temp directory before doing so. I also checked the semaphore directory and could not find any echomail.in waiting etc. just the mis.bsy semaphore.

I had a quick look in echomail\out\fidonet and could not see any *.bsy files before running the overdue toss.

MUTIL at 01:06:53 through 01:07:54 reported it couldn't gain the locks for nodes to process mail. At first glance I am assuming this was your concern? In your MIS.log it shows you had active connections during that period of time via BINKP.

There are no leaked BSY files, no crashes, no errors... Just MUTIL saying it can't process mail but that is intended behavior when BINKP nodes are exchanging packets, else things might get corrupted.

I'll take a better look later when I have some more time.

--- Mystic BBS v1.12 A37 2017/12/21 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello Avon!

23 Dec 17 13:37, you wrote to g00r00:

My wife probably thinks I already spend too much time on it as it is!
:)

Yes she does!

So go and do these jobs for her (In no order):

Make her a cuppa
mow the lawns
paint the rest of the house
move that pile of dirt over there
shift that rock
trim the tree out the back
make a new garden bed
laydown some more mulch
get the weed wacker out
clean the car





Vorlon


--- GoldED+/LNX 1.1.5-b20161221
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (21:1/195)

I've updated the prealpha with some little changes just in case anyone is interested.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

On 12/20/18, g00r00 pondered and said...

I've updated the prealpha with some little changes just in case anyone is interested.

If I was not at work right now I'd be on to it :) But instead I have to wait
8 hours - sigh :)

--- Mystic BBS v1.12 A40 2018/12/16 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I've updated the prealpha with some little changes just in case anyone is interested.

Thanks for your continued work on Mystic!

|08---
|08-|04Ktulu
|07SysOp |08@ |12Insane Asylum BBS

--- Mystic BBS v1.12 A39 2018/04/14 (Windows/64)
* Origin: Insane Asylum (21:2/122)

On 12/21/18, Avon said the following...

On 12/20/18, g00r00 pondered and said...

I've updated the prealpha with some little changes just in case anyon interested.

If I was not at work right now I'd be on to it :) But instead I have to wait 8 hours - sigh :)

Gotta love my work able to access my devices remotely and do some small
things. I have not done the upgrade due to how many changes I would have to
do at the moment.

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

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

On 12/20/18, g00r00 pondered and said...

I've updated the prealpha with some little changes just in case anyone is interested.

[snip]

+ Message Base editor now has a /A command to select all bases.

+ File Base editor now has a /A command to select all bases.

+ File Base editor now has a /G Global Editor similar to the Message Base
editor

[snip]

Those additions will save folks a lot of time, especially the last one - thanks!

--- Mystic BBS v1.12 A40 2018/12/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

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

I've updated the prealpha with some little changes just in case
anyone is interested.

[snip]
+ Message Base editor now has a /A command to select all bases.
+ File Base editor now has a /A command to select all bases.
+ File Base editor now has a /G Global Editor similar to the Message
Base editor
[snip]
Those additions will save folks a lot of time, especially the last one
- thanks!

Merci beaucoup my friend, oustanding!


.- 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__ |
`--| | | |-- -------------------------------------------------'

... Catastrophy: Cat punctuation written on your skin
--- GoldED+/W32-MSVC v1.1.5-g20180902 + MIS v1.12 A40 2018/12/20 12:32:55
* Origin: FSXNet - Positronium: telnet://cmech.dynip.com (21:2/117)

On 12/21/18, Avon said the following...

+ Message Base editor now has a /A command to select all bases.

+ File Base editor now has a /A command to select all bases.

Those could come in handy.

+ File Base editor now has a /G Global Editor similar to the Message
Base editor

Woohoo! I've been waiting for that one! :)


---

Black Panther(RCS)
a.k.a. Dan Richter
Sysop - Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
The sparrows are flying again....

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

+ Message Base editor now has a /A command to select all bases.

+ File Base editor now has a /A command to select all bases.

+ File Base editor now has a /G Global Editor similar to the Message
Base editor

Those additions will save folks a lot of time, especially the last one -

Yes, I've been meaning to add that in for a long time. I'd like to do a similar version for users and possibly echomail nodes as well.

But as of now I am focused on a new larger feature that I think you will
really love :) I don't want to say too much more until I see it starting to work but I will need your help testing!

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

On 12/21/18, g00r00 pondered and said...

Yes, I've been meaning to add that in for a long time. I'd like to do a similar version for users and possibly echomail nodes as well.

Both would be welcome and I think the latter more so than the former at this stage (he says wearing a HUB operators hat).

But as of now I am focused on a new larger feature that I think you will really love :) I don't want to say too much more until I see it
starting to work but I will need your help testing!

I have a pretty good hunch I know what that may be, and thanks!

--- Mystic BBS v1.12 A40 2018/12/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

But as of now I am focused on a new larger feature that I think you w really love :) I don't want to say too much more until I see it starting to work but I will need your help testing!

I have a pretty good hunch I know what that may be, and thanks!

Well, I finished it today after a good 10 hour programming session. I am
about to upload it when I log off.

If it wasn't the thing you hoped for let me know what that is maybe I can do that next :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

On 12/21/18, g00r00 pondered and said...

Well, I finished it today after a good 10 hour programming session. I am about to upload it when I log off.

[snip]

+ Echomail nodes now have an "Encryption Key" option. When this option is
set to a non-blank value, Mystic will encrypt all of the contents of
Netmail messages to this node with an AES-256 encryption. This completes
a fully encrypted echomail solution as both transport and private messages
are secured.

This is done in a way that is completely transparent to unsupporting
systems, meaning that you can still route netmail through systems and they
will not harm the encrypted netmails! The encryption also hides the
message subject, so when combined with Area/Filefix passwords will no
longer be readable. You must have Cryptlib installed for this to work.

[snip]

That's totally cool - thanks! I'm going to try and play with this tonight and will also move to update NET 1 HUB so I can better test the other encryption features you have added in recent pre-alphas between test nodes and a
working HUB.

Warning...brain started to wander off down dimly lit pathways...

You might think I'm a tad nutty but could the feature be extended to echomail posts in some form? So a post could be encrypted and decrypted in a conference in such a way that only certain echonodes could encode/decode it. I'm not
good at mentally thinking this through at the early hour I type this. But I thinking about how you can use PGP to encode a message to more than one party in one go using public/private keys etc. Dunno.. I was just fishing for a way to have 'one to many' 'many to many' discussions such as echomail does but
with content that is sent encrypted like a PGP email might be.

[thinking some more]

even if that worked you still end up with perhaps decoded echomail for a message board that can be viewed by all users given access to the message
base on a specific node in the network.

Perhaps the encode/decode could be keyed to the individual BBS user account,
so taking the idea of keys for echonode down another level. I guess then you can have a user X who can encode/decode posts in echomail area Y that in turn can only be encoded/decoded between certain nodes who also share the correct keys..

I'll stop now.. head hurts and I'm not really thinking that straight about a topic I know only bits of. But the main thrust of it would be how to use on
the fly encryption to do something with echomail so that those who had agreed encryption key access to read/post could do so but those who did not would just see encoded rubbish... so PGP emails for echomail - I think?!

Others may well care to help shine a light on how crazy my idea is :)

--- Mystic BBS v1.12 A40 2018/12/22 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

That's totally cool - thanks! I'm going to try and play with this
tonight and will also move to update NET 1 HUB so I can better test the other encryption features you have added in recent pre-alphas between
test nodes and a working HUB.

Make sure you have the absolute latest release. At the last minute I decided to make a change (after I made that post here) so I ended up working a few
more hours to get that worked out. If you read the WHATSNEW you can see what
I added as the entry has been changed a bit from what you posted here.

You might think I'm a tad nutty but could the feature be extended to echomail posts in some form? So a post could be encrypted and decrypted
in a conference in such a way that only certain echonodes could encode/decode it. I'm not good at mentally thinking this through at the early hour I type this. But I thinking about how you can use PGP to
encode a message to more than one party in one go using public/private keys etc. Dunno.. I was just fishing for a way to have 'one to many'

Echomail is intended to be public, Netmail is private as you know, so I worked along those lines. But yes, we could make echomail messages that could only be decoded by BBSes that have the password. I am open to hearing more about it bu I am not sold on it yet! There are some negative aspects to doing what I
think you are proposing.

even if that worked you still end up with perhaps decoded echomail for a message board that can be viewed by all users given access to the message base on a specific node in the network.

Yes, that is how it would work. If you want to make it per-user, then they should probably just use PGP or something that is designed to do that already. I know that it'd be inconvenient for a user to cut and paste the message content out of the BBS terminal though.

Perhaps the encode/decode could be keyed to the individual BBS user account, so taking the idea of keys for echonode down another level. I guess then you can have a user X who can encode/decode posts in echomail area Y that in turn can only be encoded/decoded between certain nodes
who also share the correct keys..

There is an overhead to doing high end encryption and hashing to consider, too. How do we know who should have access to the encrypted mail unless we try to decrypt it and see if it works? We can't exactly store the private key with the data to know if the user has the key...

So to do that, we introduce an overhead where every message has to be decrypted on the fly for every user each time they view it. Let me paint the picture:

We'd create a "key database" for each user where they would just input a list o keys, and when an encrypted echomail message is encountered, Mystic would have to try to decrypt it with every single key in their store in order to determine if any of them are legit. So say you have 30 private keys in your key store, Mystic may have to try to decrypt a message up to 30 times each time a user reads it, and then it has to take the decrypted data and run it through and authenticity system so it can tell if the key was the correct one and the data hasn't been tampered with (Mystic does all of this already with Netmail).

Mystic is using high end encryption and hashing in most places, and these come at a cost and you can see how that quickly can get out of hand when a user has lot of keys. PGP works because the processing isn't done by the server but by the client but in this case it'd be Mystic doing it.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

I've updated the prealpha with some little changes just in case anyon interested.

[snip]

+ Message Base editor now has a /A command to select all bases.

+ File Base editor now has a /A command to select all bases.

+ File Base editor now has a /G Global Editor similar to the Message
Base editor

I am very happy to see these changes. This is much appreciated.

Thanks,

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Bottomless Abyss BBS þ bbs.bottomlessabyss.net (21:1/172)

On 23 Dec 2018, Avon said the following...

That's totally cool - thanks! I'm going to try and play with this
tonight and will also move to update NET 1 HUB so I can better test the other encryption features you have added in recent pre-alphas between
test nodes and a working HUB.

If you need another guinea pig to test with, count me in! :)

--- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
* Origin: Omicron Theta * Southaven MS * winserver.org:2300 (21:2/135)

On 27 Dec 2018, Warp 4 pondered and said...

If you need another guinea pig to test with, count me in! :)

OK will do. Thanks!


ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

--- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)