Puppy Linux Discussion Forum

Note:
if you have encrypted save files that require passwords.
At booting point of loading the save.
That is going to require the save file password, before boot up continues.
So, following is not needed.

Turn off autologin and require entering a password.
Boot to the point a password is required, to continue booting to the desktop.
Why do this?
Because you like to use passwords and do not want to autologin.

This is for booting on newer versions of Puppy.

First, make sure you have the boot menu option to boot, not using the save. (pfix=ram)
If it does not work.
You can boot, not using the save, and delete from the save, the bad file.

For some reason, to get it working, had to first change the root password.
in a terminal.

passwd

change password and remember it.

Edit this file:
/bin/autologin
on line 7
Remove the -f after login
Line 7 now looks like this:

exec login $LOGINUSER

It now boots to a point that you must enter the password for root.

If this does not work.
Boot not using the save.
Open the save and navigate to /bin/
Delete the autologin file.
Now the save will boot, using the original autologin.

On very old versions of Puppy. It is done a little differently.
Read note below before doing this.

Change the root password as already shown how.

Open this file in a text editor.
/etc/inittab

remove the autologin command

make the fisrt tty1 line look like the second tty2 line.
So tty1 and tty2 will be the same.

NOTE:
If you open the /etc/inittab file and it looks similar to this:

::sysinit:/etc/rc.d/rc.sysinit
tty1::respawn:plogin
tty2::respawn:getty 38400 tty2
::ctrlaltdel:/sbin/reboot

You have the newer autologin, so use the first method, to turn off autologin.

This alternate worked!! Thanks, again. Now I just need to get xlock working. Maybe updated Puppy will help.

CaptGeorge wrote: ↑Thu Jun 17, 2021 4:04 pm

This alternate worked!! Thanks, again. Now I just need to get xlock working. Maybe updated Puppy will help.

hi @CaptGeorge
try deleting (these are hidden files so click the 'eye' symbol to show hidden files)

/root/.xlockrc
/root/.config/Xlock/xlockrootparams
/root/.config/Xlock/xlockscreenparams

and then re-setup xlock

xlock will not work, until you get a password setup.
Left click on the desktop lock icon.
It asks to make a password.
Enter what you want to use and then press enter key.
It asks to do it again, to be sure it got it correct.
After the password is set, it should work.

Right click menu. has options. when you right click on. the desktop lock icon.

Hi Phil
Only /root/.xlockrc existed. I trashed it. And, re-setup Xlock and every thing is working. Thanks!

Ok, so I made changes as described and I did get the login thing when booting.

But it required both a;

1. Login &
2. Password

So I tried to write both root and Root as logins and used the password I changed to with: passwd command in the urxvt terminal emulator. It doesn't work I get the message: "Wrong login" or similar.

UPDATE: I tried it again and now it WORKS! just typed "root" as login...

Never understand why folks come to an OS with 'root' ownership & auto-login, and then want to set it all up to behave like a normal, mainstream distro......

Mike.

To not have anyone access your files easily by booting up your computer I suppose...

I'm not sure how recent puppies do the encryption however
older puppies would use shinobar's pupsaveconfig at the time of the first creation of pupsave file.

http://shino.pos.to/linux/pupsave.html

Note that there is a password option (if desired) however most people don't use it.

___________

What does this encrypt choice encrypt?

All the files in root?

What's the point of encryption if one doesn't use a password? Can't anyone logged into the computer see the files then anyways?

Will the encryption make things slower i.e. to open up an encrypted file?

If I choose a password for the encryption, when do I have to enter it? Do I have to do it whenever opening an encrypted file?

If you have a save file, then the save file is accessed as a block device.
LUKS encryption encrypts the entire block device.
Whatever is in the block device (journals, file systems, files contained in file systems, ...) is encrypted.
That is, all the blocks in the block device are encrypted.

You can choose to encrypt the save file when it is created.
The save file is created when you shut down the first time.

All the files in root?

Files are not encrypted.
The blocks of the block device are encrypted. Typically, a block consists of 4k bytes of data.
A byte is 8 bits. A bit is a 1 or a zero (binary digit.)
All the blocks are encrypted. Blocks contain the boot record, journals, all of the file systems in the block device, file names, inodes, the data in the inodes, the files and dirs in the file system.

What's the point of encryption if one doesn't use a password?

Puppy always asks for a password when creating an encrypted save file.
Puppy always asks for a password when booting Puppy, if the save file is encrypted.

Will the encryption make things slower i.e. to open up an encrypted file?

Encryption is slower, but you probably won't notice it, unless you have a very slow computer.

password for the encryption, when do I have to enter it? Do I have to do it whenever opening an encrypted file?

You enter the password once, everytime Puppy boots. before X starts.
Individual files are not encrypted. It's the entire block device that is encrypted.