Remove Passord Requirement for Login / Wake Up

Is there a way I can remove the requirement for a password for everything except Terminal commands, installations, etc.? I live alone and don't take the laptop anywhere. So, it is completely superfluous. even if I can reduce the number of characters to 4, I'll be happier!

As anyone could use a bootable USB to wipe and fresh install this laptop, I'm really not concerned about anyone stealing it - plus, it's a million years old already! :sweat_smile: and it can't run Windows 11 :joy:
TIA

I recommend this; and it is what I do myself.
The problem with password removal is not security, but system. It is a process and when that process gets removed, the system gets balky.
This is why even Autologin causes issues.

But using a 4 digit PIN is quick to enter and easy to use while keeping that process in place.
One issue may be that when you change your password, the PAM authorization is set to require a lengthy password, even if it is not set at point of install. We can change that.
To change the password length requirement, please see this post:

To change your password, in terminal run:

passwd

Then enter the current password. Next, following the prompt, enter the new password (4 digit PIN).

As an aside, I ensure that numlock is enabled at startup for faster PIN entering.

2 Likes

@Aravisian , thank you so much - as always - for offering a speedy and easy to understand solution!

1 Like

@0Picass0, additionally to the above solution by Aravisian.
If you ever need to do a new install, a 1 character password is accepted.

I use a 1 character password for various distro's as VM's.
As far as I know, this is only achievable at point of install.

1 Like

@Freeway , that's interesting. I don't remember having a choice when I installed Zorin, except to not require a password on login - which I chose, but it has been ignored. It forced me to use a long password, unlike Mint where I could make any length. If I ever do a fresh install I'll remember to look out for it. Thanks!

Additionally to what have been said above, you can set "automatic login" in the settings --> Users section
You won't need your password when booting your laptop but it will still be required for sudo terminal commands and other actions. I've not had any issues with this setting so far.

There is a choice, you have to put details in the boxes required by the installer.
Otherwise you can't continue the install.

@BrewCoffeeAddict, I chose "automatic login" when I installed Zorin...

I've followed your advice and unlocked the settings, and changed it to automatic login. Thanks. :crossed_fingers:

1 Like

I just rebooted and had to login again! I have checked the user settings and it is still toggled to automatic login!

It isn't a massive issue but it is annoying, I prefer a low-light environment, the keyboard isn't backlit, so I often hit the wrong key... In Mint I just have a 4 digit password, and that's perfect!

I suggest you take note of @Aravisian advice re Autologin. We tend to see issues reported here on the forum when that is used. So in the long run it can be more haste less speed

Thanks @zabadabadoo , for the extra advice. As I wasn't able to follow Aravisian's instructions, so I guess I'm stuck. I'll turn auto login back off - it isn't working anyway!

The developers should look into changing this - we shouldn't be forced into making a complex password if we don't need one, and it should be left up to the user's choice. One reason for choosing Linux is freedom of choice, and if I don't need it in Mint, I sure as heck don't need it in Zorin.

What makes you think you are?

I assume you are on Core (Gnome). I don't know if that is any different re password restrictions, it shouldn't be.

What do you mean by that i.e. what did you do, and what did you see?

1 Like

When I ran the command I got an untitled document 1 - gedit pop up (blank), and in the Terminal:
HP-Pavilion-TS-15-Notebook-PC:~$ sudo gedit
[sudo] password for ruth:

(gedit:4901): dconf-WARNING **: 14:19:15.092: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

(gedit:4901): dconf-WARNING **: 14:19:15.123: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)

@Aravisian - I'm afraid I've misunderstood something important.

You can use sudo gedit to access the file in root, but must specify the path to the file as well:

sudo gedit /etc/pam.d/common-password

The GUI method is to first use terminal to elevate to root

sudo -i

Then launch Nautilus File Manager after entering your password successfully

nautilus

Now, click on "Other locations" in the left pane, then "Computer" in the right pane... pane... pain... anyway...
You are now at root.
Double click on the etc folder, then pam.d and right click on common-password and select open with to select gedit to open that file with.

@zabadabadoo , I'm sorry - I pasted what I saw into the post that Aravisian directed me to. I'm using Zorin 17.1 Education (I'm a teacher and wanted to check it out).

I'll report back with what I saw, but I have a bunch of replies to attend to first. I appreciate you trying to help me out.

In hindsight, I realize I was not very clear. I took it for granted that a reader will know already to set the path when using terminal to access a file using the software command.

@Aravisian , I've just tried to follow your latest instructions, and I confess that I don't understand what I'm seeing. I don't have a left pane or right (pain) :wink: I get a bunch of warnings in the Terminal and a notepad: "Common Password" with #36 notes. I'm completely lost.

This isn't a big problem for me, just a nuisance that I guess I'll have to live with. I really, really appreciate the time and effort @Aravisian and everyone else has made to try and help me resolve the annoyance. It is really down to the developers to make this a choice for individuals to make, rather than insisting on long, complex passwords.

I'll have a browse on YouTube to see if I can find a video to follow - I don't have so many problems with those. As for this post, let's leave it at: --the newbie doesn't have the knowledge / skills to carry out the task - yet!--

Maybe, when I finally ditch WX for good, I'll decide to do a new installation of Zorin Core, rather than Education - could be the password requirements are different??? (there is always one rouge student you have to watch out for!).

Thanks again!

It takes a bit of practice to become familiar with the actions. Using your experience as a teacher as an example: Let's say you are teaching a student about grammar and syntax, but they do not know the definition of "noun". Maybe they apply what you say in the homework, but lacking the definition of the term 'noun' they miss the mark. Knowing that definition would have added so much clarity.
This is not a time to give up, but to roll up your sleeves.
That terminal picked a fight. Are you going to let it get away with that?
Using the sudo command is one part of a full instruction. The sudo software manages user and SuperUser permissions (Sudo means SuperUser do, as in "do this".)
This must be followed by the next part of the command; what do you want SuperUser to do? In this case, run the software Gedit. So we string that in to sudo gedit. Gedit also needs to know what to do, though. It needs a file to open. Otherwise it has nothing to do. In this case, that file is "common-password" and we can find it in the /etc/pam.d directories. So, we tack that on to make

sudo gedit /etc/pam.d/common-password

This is now a full command string where each part knows what to do and therefor executes it.
Once you have that up, you should be seeing your common-password file contents in your terminal.

I listed two separate methods in that post above to allow a user to choose which they prefer. For now, let's reduce confusing instructions and stick to just one: the terminal. It is good practice.

1 Like

@Aravisian , I appreciate the analogy and understand what your aim is. I have tried again and got the same result, as pasted below in the screenshot. It is still as clear as mud to me, sorry. .

I'll come back with renewed vigour tomorrow and try to understand it!