On 10/23/17, bcw142 pondered and said...

On 10/23/17, apam said the following...

One thing I know is many BBSes store passwords in plain text, I think mystic does, but I am not certain of that. It just means sysops of ot BBSes know your passwords, (which doesn't matter if you use different passwords, but if they're the same..)

Yes, Mystic stores all passwords in upper case plain text. If you look at users.dat with a hexeditor you can read them easily, of course as sysop you can read passwords anyway from the user editor. I suspect G00r00
will be encrypting that with cryptlib being used for ssh already, more
of the matter of the time to do it.

00006600 0E 00 00 00 00 00 00 00 05 67 75 65 73 74 77 6E .........guestwn 00006610 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00006620 00 00 00 00 00 00 00 07 6A 20 73 6D 69 74 68 00 ........j smith. 00006630 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 ................ 00006640 00 00 00 00 00 00 05 47 55 45 53 54 00 00 00 00 .......GUEST....

Hi g00r00

Fairly sure this is on your TO-DO but for upcoming releases of Mystic would
you look to encrypt the password data in Mystic please?

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | New Zealand | agency.bbs.geek.nz (21:1/101)

On 10/24/17, Avon said the following...

Hi g00r00

Fairly sure this is on your TO-DO but for upcoming releases of Mystic would you look to encrypt the password data in Mystic please?

Back when I was running Synchronet I asked Digital Man about the same issue. His response was that the passwords had to be stored in plaintext (or at
least retrievable) for compatibility with some kind of other software - can't recall what it was.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

Hi g00r00

Fairly sure this is on your TO-DO but for upcoming releases of Mystic would you look to encrypt the password data in Mystic please?

I had this already in Mystic 2 demo, and its ready for Mystic 1... the problem was when I wanted to do it in 1.10 people didn't like the idea of not being able to retrieve their passwords.

Before I can do it I need to get the "stuck node" issue introduced in A35 fixed, because once you convert your user database you won't be able to go back to previous alphas. I haven't heard any information on what the user was doing on those nodes that get stuck so I can't fix it.

The system it uses is a variable iteration PBKDF w/ SHA 512.

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

On 10/24/17, g00r00 pondered and said...

I had this already in Mystic 2 demo, and its ready for Mystic 1... the problem was when I wanted to do it in 1.10 people didn't like the idea
of not being able to retrieve their passwords.

Yep that rings a bell now that you mention it.

Before I can do it I need to get the "stuck node" issue introduced in A35 fixed, because once you convert your user database you won't be able to
go back to previous alphas. I haven't heard any information on what the user was doing on those nodes that get stuck so I can't fix it.

I'll need to wade back through the echomail pile and see if I can reacquaint myself with the issues raised. Stuck as in node had locked up?

Best, Paul

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

Avon said....

Before I can do it I need to get the "stuck node" issue introduced in

A35

fixed, because once you convert your user database you won't be able to go back to previous alphas. I haven't heard any information on what the user was doing on those nodes that get stuck so I can't fix it.

I'll need to wade back through the echomail pile and see if I can reacquaint myself with the issues raised. Stuck as in node had locked up?

This wouldn't be the issue Dan was talking about would it? The one that turned out to be file locking due to his backup program?

It was where more than one user would log into node 1 at a time.

Andrew

--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 10/24/17, g00r00 said the following...

Before I can do it I need to get the "stuck node" issue introduced in A35 fixed, because once you convert your user database you won't be able to
go back to previous alphas. I haven't heard any information on what the user was doing on those nodes that get stuck so I can't fix it.

Hey g00r00,

I think it happens when somebody drops carrier while running a door game through dosemu. Nothing is shown in the logs reguarding the disconnect, all that is shown is:

------------------- Node 1 (Mystic v1.12 A35)
2017.10.24 19:09:21 Connect from 71.199.6.161 (c-71-199-6-161.hsd1.ut.comcast.n$
2017.10.24 19:09:22 Immortal logged in
2017.10.24 19:10:01 Executed Door: /home/bbs/mystic/cron/doors.sh JUNKYARD 1


I can cause it to happen here by:

Log in and run a dosemu door game.
Disconnect while the game is running.
Look at htop, the mystic process is running but its only using 1% cpu, dosemu is running as well and is using 45%.
Either wait for dosemu to exit on it's own or kill it with the kill command. Dosemu exits and then the mystic process immediately jumps to 100% cpu usage.

The mystic process has to then be killed with the kill -9 command, regular
kill won't work.

Immortal

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 10/25/17, apam pondered and said...

Before I can do it I need to get the "stuck node" issue introduced

A35

fixed, because once you convert your user database you won't be abl go back to previous alphas. I haven't heard any information on wha user was doing on those nodes that get stuck so I can't fix it.

I'll need to wade back through the echomail pile and see if I can reacqu myself with the issues raised. Stuck as in node had locked up?

This wouldn't be the issue Dan was talking about would it? The one that turned out to be file locking due to his backup program?

It was where more than one user would log into node 1 at a time.

I think it may be - thanks! I'll dig back. Dan does this ring bells with you? Wasn't it unrelated to Mystic in the end but instead a case of file
permissions gone awry?

Best, Paul

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

Log in and run a dosemu door game.
Disconnect while the game is running.
Look at htop, the mystic process is running but its only using 1% cpu, dosemu is running as well and is using 45%.
Either wait for dosemu to exit on it's own or kill it with the kill command. Dosemu exits and then the mystic process immediately jumps to 100% cpu usage.

This is awesome thank you very much I'll look into it.

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

On 10/26/17, Avon said the following...

This wouldn't be the issue Dan was talking about would it? The one th turned out to be file locking due to his backup program?

It was where more than one user would log into node 1 at a time.

I think it may be - thanks! I'll dig back. Dan does this ring bells with you? Wasn't it unrelated to Mystic in the end but instead a case of file permissions gone awry?

It was the backup program that I was using. It would lock the files in a
queue for upload, and while they were in the cue, any time Mystic tried to access the files, it would create a '(conflicted)' version of the file.

For example, 'chat1.dat, chat1(conflicted).dat, chat1(conflicted 2).dat',
etc. The log files were also doing this. At one point, I had over 3000 mutil.log files, or variants thereof...

After reworking my backup process, I haven't had any issues.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

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

On 10/26/17, Black Panther pondered and said...

It was where more than one user would log into node 1 at a time.

I think it may be - thanks! I'll dig back. Dan does this ring bells w you? Wasn't it unrelated to Mystic in the end but instead a case of f permissions gone awry?

It was the backup program that I was using. It would lock the files in a queue for upload, and while they were in the cue, any time Mystic tried

Thanks Dan... so asides the multiple files, was this causing a node lock up
for you as well?

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

On 10/27/17, Avon said the following...

Thanks Dan... so asides the multiple files, was this causing a node lock up for you as well?

The nodes weren't locking up, but with the files being locked, everyone was logging in to node 1. There was one instance where there were three of us logged in, and all showing node 1. That caused issues with dropfiles and logs all over the place...


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

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

On 10/26/17, Black Panther pondered and said...

Thanks Dan... so asides the multiple files, was this causing a node l up for you as well?

The nodes weren't locking up, but with the files being locked, everyone was logging in to node 1. There was one instance where there were three
of us logged in, and all showing node 1. That caused issues with
dropfiles and logs all over the place...

OK. I'm not sure if this is what g00r00 was referring to as the issue mentioned. But thanks for the clarification. :)

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