Open-source News

Firefox 95 vs. Chrome 97 Browser Performance On Linux

Phoronix - Fri, 01/07/2022 - 03:12
With starting a new year, it's an interesting time to take a fresh look at how the latest Mozilla Firefox and Google Chrome web browsers are competing on the Linux desktop...

Classic SysAdmin: Understanding Linux File Permissions

The Linux Foundation - Fri, 01/07/2022 - 03:00

This is a classic article written by Jack Wallen from the Linux.com archives. For more great SysAdmin tips and techniques check out our free intro to Linux course.

Although there are already a lot of good security features built into Linux-based systems, one very important potential vulnerability can exist when local access is granted – – that is file permission-based issues resulting from a user not assigning the correct permissions to files and directories. So based upon the need for proper permissions, I will go over the ways to assign permissions and show you some examples where modification may be necessary.

Permission Groups

Each file and directory has three user based permission groups:

  • owner – The Owner permissions apply only to the owner of the file or directory, they will not impact the actions of other users.
  • group – The Group permissions apply only to the group that has been assigned to the file or directory, they will not affect the actions of other users.
  • all users – The All Users permissions apply to all other users on the system, this is the permission group that you want to watch the most.
Permission Types

Each file or directory has three basic permission types:

  • read – The Read permission refers to a user’s capability to read the contents of the file.
  • write – The Write permissions refer to a user’s capability to write or modify a file or directory.
  • execute – The Execute permission affects a user’s capability to execute a file or view the contents of a directory.
Viewing the Permissions

You can view the permissions by checking the file or directory permissions in your favorite GUI File Manager (which I will not cover here) or by reviewing the output of the “ls -l” command while in the terminal and while working in the directory which contains the file or folder.

The permission in the command line is displayed as: _rwxrwxrwx 1 owner:group

  1. User rights/Permissions
    1. The first character that I marked with an underscore is the special permission flag that can vary.
    2. The following set of three characters (rwx) is for the owner permissions.
    3. The second set of three characters (rwx) is for the Group permissions.
    4. The third set of three characters (rwx) is for the All Users permissions.
  2. Following that grouping since the integer/number displays the number of hardlinks to the file.
  3. The last piece is the Owner and Group assignment formatted as Owner:Group.
Modifying the Permissions

When in the command line, the permissions are edited by using the command chmod. You can assign the permissions explicitly or by using a binary reference as described below.

Explicitly Defining Permissions

To explicitly define permissions you will need to reference the Permission Group and Permission Types.

The Permission Groups used are:

  • u – Owner
  • g – Group
  • o – Others
  • a – All users

The potential Assignment Operators are + (plus) and – (minus); these are used to tell the system whether to add or remove the specific permissions.

The Permission Types that are used are:

  • r – Read
  • w – Write
  • x – Execute

So for example, let’s say I have a file named file1 that currently has the permissions set to _rw_rw_rw, which means that the owner, group, and all users have read and write permission. Now we want to remove the read and write permissions from the all users group.

To make this modification you would invoke the command: chmod a-rw file1
To add the permissions above you would invoke the command: chmod a+rw file1

As you can see, if you want to grant those permissions you would change the minus character to a plus to add those permissions.

Using Binary References to Set permissions

Now that you understand the permissions groups and types this one should feel natural. To set the permission using binary references you must first understand that the input is done by entering three integers/numbers.

A sample permission string would be chmod 640 file1, which means that the owner has read and write permissions, the group has read permissions, and all other user have no rights to the file.

The first number represents the Owner permission; the second represents the Group permissions; and the last number represents the permissions for all other users. The numbers are a binary representation of the rwx string.

  • r = 4
  • w = 2
  • x = 1

You add the numbers to get the integer/number representing the permissions you wish to set. You will need to include the binary permissions for each of the three permission groups.

So to set a file to permissions on file1 to read _rwxr_____, you would enter chmod 740 file1.

Owners and Groups

I have made several references to Owners and Groups above, but have not yet told you how to assign or change the Owner and Group assigned to a file or directory.

You use the chown command to change owner and group assignments, the syntax is simple

chown owner:group filename,

so to change the owner of file1 to user1 and the group to family you would enter chown user1:family file1.

Advanced Permissions

The special permissions flag can be marked with any of the following:

  • _ – no special permissions
  • d – directory
  • l– The file or directory is a symbolic link
  • s – This indicated the setuid/setgid permissions. This is not set displayed in the special permission part of the permissions display, but is represented as a s in the read portion of the owner or group permissions.
  • t – This indicates the sticky bit permissions. This is not set displayed in the special permission part of the permissions display, but is represented as a t in the executable portion of the all users permissions
Setuid/Setgid Special Permissions

The setuid/setguid permissions are used to tell the system to run an executable as the owner with the owner’s permissions.

Be careful using setuid/setgid bits in permissions. If you incorrectly assign permissions to a file owned by root with the setuid/setgid bit set, then you can open your system to intrusion.

You can only assign the setuid/setgid bit by explicitly defining permissions. The character for the setuid/setguid bit is s.

So do set the setuid/setguid bit on file2.sh you would issue the command chmod g+s file2.sh.

Sticky Bit Special Permissions

The sticky bit can be very useful in shared environment because when it has been assigned to the permissions on a directory it sets it so only file owner can rename or delete the said file.

You can only assign the sticky bit by explicitly defining permissions. The character for the sticky bit is t.

To set the sticky bit on a directory named dir1 you would issue the command chmod +t dir1.

When Permissions Are Important

To some users of Mac- or Windows-based computers, you don’t think about permissions, but those environments don’t focus so aggressively on user-based rights on files unless you are in a corporate environment. But now you are running a Linux-based system and permission-based security is simplified and can be easily used to restrict access as you please.

So I will show you some documents and folders that you want to focus on and show you how the optimal permissions should be set.

  • home directories– The users’ home directories are important because you do not want other users to be able to view and modify the files in another user’s documents of desktop. To remedy this you will want the directory to have the drwx______ (700) permissions, so lets say we want to enforce the correct permissions on the user user1’s home directory that can be done by issuing the command chmod 700 /home/user1.
  • bootloader configuration files– If you decide to implement password to boot specific operating systems then you will want to remove read and write permissions from the configuration file from all users but root. To do you can change the permissions of the file to 700.
  • system and daemon configuration files– It is very important to restrict rights to system and daemon configuration files to restrict users from editing the contents, it may not be advisable to restrict read permissions, but restricting write permissions is a must. In these cases it may be best to modify the rights to 644.
  • firewall scripts – It may not always be necessary to block all users from reading the firewall file, but it is advisable to restrict the users from writing to the file. In this case the firewall script is run by the root user automatically on boot, so all other users need no rights, so you can assign the 700 permissions.

Other examples can be given, but this article is already very lengthy, so if you want to share other examples of needed restrictions please do so in the comments.

The post Classic SysAdmin: Understanding Linux File Permissions appeared first on Linux Foundation.

WirePlumber 0.4.6 Released For Managing PipeWire

Phoronix - Fri, 01/07/2022 - 02:11
Helping make PipeWire suitable for the Linux desktop so quickly has been WirePlumber as a more featureful alternative to PipeWire's default session manager. Out today is WirePlumber 0.4.6 as the latest step forward on that front...

Linux 5.16's Great Features Include FUTEX2, Folios, AMD Rembrandt, Intel AMX & Much More

Phoronix - Thu, 01/06/2022 - 22:02
After a quiet holiday period the Linux 5.16 kernel is set to be introduced as stable this Sunday. Here is a look at the sixteen most exciting features to find with Linux 5.16...

Intel's Linux OS Shows The Importance Of Software Optimizations, Further Optimized Xeon "Ice Lake" In 2021

Phoronix - Thu, 01/06/2022 - 21:00
As part of the various end-of-year Linux comparisons that I've made a habit of over the past 17 years, with the EOY 2021 benchmarking I was rather curious to see how Intel's Clear Linux distribution has evolved Xeon Scalable "Ice Lake" performance since that platform launched in Q2'2021. It turns out there have been some terrific optimizations squeezed out of that latest-generation Xeon Scalable platform on Intel's Clear Linux. In this article is a look at the Ubuntu and Clear Linux performance on the flagship Xeon Platinum 8380 2P reference server back around the time Ice Lake launched and then again using the latest software packages that closed out 2021.

Oracle Working On Multi-Threaded VFIO Page Pinning For ~10x Faster QEMU Initialization

Phoronix - Thu, 01/06/2022 - 18:30
For those assigning VFIO devices to guest virtual machines, the initialization/start-up process may soon be much faster with a set of patches volleyed by Oracle...

Intel AMX Support For KVM Use May Be Ready For Mainline

Phoronix - Thu, 01/06/2022 - 18:02
In preparation for Xeon Scalable "Sapphire Rapids" processors, Linux 5.16 adds support for Advanced Matrix Extensions. But that AMX bring-up is more invasive than when introducing AVX as with AMX the feature needs to be "requested" for use by user-space, among other changes. As such extra handling also needed to be introduced for the Kernel-based Virtual Machine (KVM) that hadn't made it for v5.16 but now it looks like the AMX KVM support may be ready for mainline...

Fedora 36 Looking To Move Users Away From Legacy "ifcfg" Network Scripts

Phoronix - Thu, 01/06/2022 - 17:46
Longtime Linux users will likely recall when it was commonplace to modify /etc/sysconfig/network-scripts/ifcfg-* files for managing your network connections. Fortunately, that's largely a thing of the past and Fedora 36 is looking to remove support for those legacy network configuration files from new Fedora installs...

Must-have open source cheat sheets for 2022

opensource.com - Thu, 01/06/2022 - 16:01

You can't remember every command or shortcut you need to use. We are all human. Usually, I keep notes on separate bits of paper and in notebooks. This has led to some serious dysfunction on my desk. There is some five years' worth of clutter in scribbled bits everywhere. 2021's cheat sheets will bring that clutter down a notch. From JavaScript to Linux, there's something in this list for you.


read more

Send desktop notifications and reminders from Linux terminal

opensource.com - Thu, 01/06/2022 - 16:00

Sometimes it's useful to get visual feedback from a script. For example, when a script or cron job completes, a long-running build fails, or there is an urgent problem during script execution. Desktop applications can do this with popup notifications, but it can be done from a script too! You can use script commands to send yourself desktop notifications and reminders.


read more

Pages