microcore 5.0.2 - is there a bug in the protect mode?

[netnomad]

hi roberts,

microcore 5.0.2 without encrypted mydata restores flawless my settings.
for my test for booting in protected mode i use a really simple password...

at the boot prompt i entered following password:
1234567890

in /etc/sysconfig/bfe following password is stored:
123456789
that means the last digit is not stored

after a reboot with the boot code protect, i have to offer the 10-digit password
1234567890
that mydata.tgz.bfe is correctly decrypted.

if i want to encrypt mydata.tgz.bfe on the command line, i have to give following password:
"1234567890"
to decrypt the mydata.tgz.bfe to mydata.tgz.

i can observe the same behavior with a real complicated password... the last digit is not stored in /etc/sysconfig/bfe, but is needed for the decryption and on the cli i have to offer the password in quotation-marks.

thank you for your help.

[netnomad]

hi roberts,

in microcore 5.0.2 the password entry cannot be corrected:
backspace and backspace-cursor doesn't work to correct any misspelled password.
this password correction works fine in 4.7.7.

thank you for your help and commitment.

[roberts]

I can see and fix the chopping of the last password character entered.
But the screen handling that appears to work in 4.7.7 and does not in 5.x is at a much lower level than provided by the script. So enter carefully.