Got a weird one here now.. Some of my users are telling me they can't log on because the system won't accept their passwords.. I just changed the minimum length to 4 from 6 in case they were using shorter passwords. Plus, after the
5 times of trying it asks if they want to send a sysOp inquiry, and it just drops carrier whether you choose yes or no.. Anyone else having issues like this with A42??

--- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Got a weird one here now.. Some of my users are telling me they can't log

I've got a memory like a hole in a bucket but there were issues with
users passwords after the upgrade. I can't remember what this fix is.
Only thing I can think of doing is a password reset?

One of the Mystic experts will be able to give you a better answer. Sorry
for my useless reply!

--- MagickaBBS v0.12alpha (Linux/armv7l)
* Origin: Fusion ~ MagickaBBS (21:4/132.1)

On 22 Jan 2019, Bucko said the following...

Got a weird one here now.. Some of my users are telling me they can't
log on because the system won't accept their passwords.. I just changed the minimum length to 4 from 6 in case they were using shorter
passwords. Plus, after the 5 times of trying it asks if they want to
send a sysOp inquiry, and it just drops carrier whether you choose yes
or no.. Anyone else having issues like this with A42??

If they did anything longer than 15 characters before A42 then tell em
shorten their passwords back down to 15 and try to login. Was a common issue for me since my pwd where 20-25 in length sometimes. Maybe the same for some of your users?

Cheers!

|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 A42 2018/12/30 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

Got a weird one here now.. Some of my users are telling me they can't
log on because the system won't accept their passwords.. I just changed the minimum length to 4 from 6 in case they were using shorter
passwords. Plus, after the 5 times of trying it asks if they want to
send a sysOp inquiry, and it just drops carrier whether you choose yes
or no.. Anyone else having issues like this with A42??

What does the node log say?

Did you upgrade your prompts/default.txt when you upgraded? I am assuming
you upgraded to the new version rather than installed a brand new A42?

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

On 23 Jan 2019, g00r00 said the following...

What does the node log say?

Did you upgrade your prompts/default.txt when you upgraded? I am
assuming you upgraded to the new version rather than installed a brand
new A42?

Upgraded the above files, no issues with that, As for the node log, it just says Bad Password 5 times and shutting down... Nothing else... I know that's not much of a help but if you want me to do anything testing wise please just ask.. Thanks.. I did change the minimum password length down to 4 from 6 in case they had passwords that were small.

--- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Just an add on.. I just was reading the whatsnew.txt again, I see a comment about those who downloaded A40 pre-12/16 may have password issues. I may have used an old file like that. So I ran upgrade password and it says current
data file version is v1.12 A40 and the revision is also A40 not A42 if it is supposed to say that.. Maybe that gives a bit more info?!?!

--- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Upgraded the above files, no issues with that, As for the node log, it just says Bad Password 5 times and shutting down... Nothing else... I
know that's not much of a help but if you want me to do anything testing wise please just ask.. Thanks.. I did change the minimum password length down to 4 from 6 in case they had passwords that were small.

Okay so if it says shutting down to me that implies that its closing properly.

What I am concerned about first is that it sounded like there was some issue sending feedback or resetting the password. I would like to get to the bottom of that first and then move onto what might be the password issue.

If answering yes to the feedback does nothing it may be because you don't
have the "Send feedback to" option in the configuration set. Its defaulted
to "Sysop Name Here" I think, so if that hasn't been set it will just do nothing. That is the first thing I would look into.

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

Just an add on.. I just was reading the whatsnew.txt again, I see a comment about those who downloaded A40 pre-12/16 may have password
issues. I may have used an old file like that. So I ran upgrade password and it says current data file version is v1.12 A40 and the revision is also A40 not A42 if it is supposed to say that.. Maybe that gives a bit more info?!?!

Yes depending on when you upgraded (if you were testing a pre-alpha version) you would have needed to rerun the upgrade using the A39 users.dat backup.

The reason this happened is because I was an idiot and I had the upgrade program upgrading the user database but then I forgot to have it copy the upgraded file into the Mystic data directory. It was fixed after a couple of days though, but those affected by it had to reupgrade from an A39 backup.

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

On 24 Jan 2019, g00r00 said the following...

Yes depending on when you upgraded (if you were testing a pre-alpha version) you would have needed to rerun the upgrade using the A39 users.dat backup.

The reason this happened is because I was an idiot and I had the upgrade program upgrading the user database but then I forgot to have it copy the upgraded file into the Mystic data directory. It was fixed after a
couple of days though, but those affected by it had to reupgrade from an A39 backup.

So I am assuming it saying A40 is ok?? If so next part, I solved the password problem, I had a feeling the users in question were using short passwords,
so I dropped the minimum down to 2 and at least 1 is able to log on again, so
I am assuming that his password was less then 6 characters.. Now second part,
I still get the hang up immediately after answering yes to send a password inquiry to the sysOp, I checked the config and had my handle as the Feedback
to option but have changed it now to my Real name, and it still isn't
working.. I know it's probably something not setup on my end.. Any other ideas?? Thank you very much for all the help.

--- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 01/24/19, Bucko said the following...

characters.. Now second part, I still get the hang up immediately after answering yes to send a password inquiry to the sysOp, I checked the

Howdy, I havent upgraded yet (havent had the chance)...

But a trap might be, if that is posting to a message base and that message
base has too high a security level for the effective user.

IE: An inbound connection (user cannot login), probably has a security level
of "zero" - so if the message base requires a minimum of 10, then will fail that logic, and the next step is disconnect. So check your ACLs...

Just a thought :)

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

characters.. Now second part, I still get the hang up immediately aft answering yes to send a password inquiry to the sysOp, I checked the

Howdy, I havent upgraded yet (havent had the chance)...

But a trap might be, if that is posting to a message base and that
message base has too high a security level for the effective user.

Yep this could be it too, great catch! I've seen people do this in the past many times, but it completely slipped my mind to ask about the E-mail security levels!

Hopefully this is the issue!

On this note I am going to add a log entry into the node log whenever a user attempts to post somewhere but doesn't have access. That way if this happens in the future there will at least be a log entry to point us in the right direction.

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

On 25 Jan 2019, deon said the following...

On 01/24/19, Bucko said the following...

characters.. Now second part, I still get the hang up immediately aft answering yes to send a password inquiry to the sysOp, I checked the

Howdy, I havent upgraded yet (havent had the chance)...

But a trap might be, if that is posting to a message base and that
message base has too high a security level for the effective user.

IE: An inbound connection (user cannot login), probably has a security level of "zero" - so if the message base requires a minimum of 10, then will fail that logic, and the next step is disconnect. So check your ACLs...

Just a thought :)

hmmm you may have a point there.. gonna try that out ..

--- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)