Encrypted save-file fix

Encrypted save-files are partly broken in the latest Wary/Racy/Slacko.

I did a first shutdown in Racy and created a save-file with light encryption. I then opened it, and found that nothing had been saved in it.

I have extended /usr/sbin/filemnt so that it now mounts encrypted .2fs files (save-files). That's one useful outcome.

I examined /usr/sbin/shutdownconfig, and found that it was not exporting variable CRYPTO in file /tmp/shutdownconfig_results, needed by /etc/rc.d/rc.shutdown. Consequently, the encrypted save-file was not getting mounted at first shutdown, so the session was not saved. Fixed.

---

Comments

Encrypted save file


Re repair encrypted
Username: BarryK
"Not that I know of.

Encrypted save file
Username: 8-bit
"Is a patch available as to the changes you made to get the encrypted save file to populate itself when initially made? There have been a few posts of problems loading an encrypted save file in Slacko and Wary. I had also tried to create one and on a reboot, and after giving my password, I was told the file was loaded but it being empty evidently causes problems with the boot sequence.

Re encrypted save file
Username: BarryK
"8-bit, That is what the first post in this thread has announced, a fix for nothing in the save file at first shutdown.

Encrypted dialog doesn't fit
Username: John Nagle
"On a related note, the "First Shutdown - Encryption" giant dialog box doesn't fit on a 640 x 480 screen with the bottom bar. The buttons are not visible. I had to guess at what ENTER did.

Tags: woof