The best way to keep your Ubuntu 22.04 system and files completely secure in the case of theft is to enable full disk encryption. This way, if your device is stolen or someone is sitting at your desk and trying to boot into your PC, they will need to know your password in order to mount any partitions. Even if they access the hard drive content through other means, all files would be encrypted and no one could read their contents.
Firewalld is the default high-level firewall manager on the Red Hat family of distributions. One of its peculiarities is that it defines a series of so called firewall zones: each zone can be considered like a different level of trust and can be configured to allow traffic through a specific set of ports. While Firewalld comes with some predefined zones which can be easily examined and modified, sometimes we may want to create our custom zones from scratch.
Are you tired of having to provide your administrator password when you use
sudo? In this tutorial you will learn how to configure
sudo without the password on Ubuntu 22.04 Jammy Jellyfish Linux. This means that the
sudo command will not prompt you to enter password hence rendering your
sudo command completely without a password.
Although it is conventional to log into the root account on some Linux systems, by default Ubuntu 22.04 does not allow us to log into root and instead expects us to achieve root permissions through use of
sudo. However, it is still possible to set a root password and subsequently log directly into root. In this tutorial, you will see how to set a password for the root account on Ubuntu 22.04 Jammy Jellyfish.
Setting up a VPN is a great way for a server to share network resources with a client. Configuring one, however, can seem a little intimidating to some users. In this tutorial, we’ll show you how to setup a VPN using OpenVPN on Ubuntu 22.04 Jammy Jellyfish, while managing to avoid advanced configuration and technical jargon along the way.
You may receive a
There are no enabled repos error message when trying to install system updates on a fresh Red Hat Linux install. This occurs when you have not enabled your RHEL subscription. In this tutorial, we will take you through the step by step instructions to register your RHEL subscription, enable the package manager, and finally install updates and remedy the error message for good.
firewalld is the default firewall on Red Hat Enterprise Linux, and it’s enabled by default, but it’s possible to Redhat disable firewall, and you’ll also see how to check firewall status in Linux. Normally, there should not be a need to disable the firewall, but it may be quite handy for testing purposes or other scenarios.
Until recently, Kali Linux used the root account by default and now you need to set Kali root password manually. In the latest versions of Kali, root login is disabled, forcing you to login to the GUI as your normal user account. The reasoning behind this change should be obvious, but if you’re a Kali user, you probably know your way around a Linux system by now, and there’s not much risk in letting you use the root account to login.
If you have forgotten the password to your Ubuntu Linux server account, you do not necessarily have to go back to square one and reinstall the whole operating system. It is possible to recover and reset the server password, whether it be the root user account or a normal user, even without the old password. In this tutorial, we will take you through the step by step instructions of recovering a forgotten root or normal account password on an Ubuntu server.
Ubuntu’s keyring is a feature that collects all of your passwords in a secure application (gnome-keyring) and will use these stored passwords to automatically log you in to various services. All of your stored passwords inside of the keyring are protected by a single master password. The keyring gets “unlocked” when you first provide your system password at sign in.
After installing SSH on your Linux system, one of the most important security practices it to make sure that the service is only enabled for intended accounts. If you have one or more accounts which do not need SSH access, then the service should be disabled for those accounts. This is to prevent one being exploited, or maybe you just do not want that particular user to be using SSH to access the server.