Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So here is the deal. I was trying to figure out what my thumb drive had set for the partition type so I needed to run cfdisk. Anyway cfdisk is located in /sbin on my system. So I ran the command /sbin/cfdisk and it worked and allowed me to pull up the thumb drive and even work with and save partitions. Well that did not concern me too much since I am supposed to have access to that device anyway but it got me thinking if I could do it with the root partition drive and low and behold it does and I am also allowed to run anything in /sbin? From what I remember are users not supposed to be able to execute code here? The permissions for this directory are drwxr_xr_x which allows all users to be able to execute code here. This is how the directories are setup by default when building a system. Or is having normal user access to the programs in sbin not a problem?
Hmmm never mind it seams that /sbin was not created for security reasons but just as a way to seperate binaries for managing the system and normal user programs.
Quote:
We recommend that users have read and execute permission for everything
in /sbin except, perhaps, certain setuid and setgid programs. The
division between /bin and /sbin was not created for security reasons or
to prevent users from seeing the operating system, but to provide a
good partition between binaries that everyone uses and ones that are
primarily used for administration tasks. There is no inherent security
advantage in making /sbin off-limits for users.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.