SlackwareThis Forum is for the discussion of Slackware Linux.
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.
PAM adds more options/features to authentication, not more security. If you only have basic needs then Slackware's 'shadow' password suite should be more than sufficient.
Though SElinux has it's place, it can be more trouble than it's worth as it's very involved and difficult to create a robust policy from what I've read.
Unless you have a very detailed understanding of them and a lot of time to get the policies right for your system's needs, you're probably just as likely to introduce security vulnerabilities with those two, as you are to fix them,
xinetd I'm not sure what you're referring to? In what way is it more secure than slackware's inetd/tcpd setup?
As security updates are released to Slackware mirrors you will receive an e-mail notification from the Slackware security team.
To easily update your Slackware system with the latest security patches I recommend that you use the slackpkg program that ships with Slackware. Slackware is legendary for security and stability. As security issues arise patches to correct the problems are quickly released.
Traditional unix like shadow is great
but some distro provide more options for example AppArmor with novell SLES and SELinux with redhat and derivatives and debian and derivatives ..etc.
Again :-) how can slackware achieve ==> robust , very stable ....etc :-)
but some distro provide more options for example AppArmor with novell SLES and SELinux with redhat and derivatives and debian and derivatives ..etc.
Sounds good. Nice name. May develop into something useful. Those were my conclusions from netsearching about AppArmor; after reviewing its config (on ubuntu) I uninstalled it as being more trouble (slowing boot a little, adding to general bloat) than its benefits were worth.
If you have enough expertise and resources to fully understand it and add to the configuration it might be a valuable tool ...
EDIT: security is a process rather than an install-time task and part of that process is fully understanding the system. Slackware's simplicity should aid, whereas a more tailored, complex system would make it harder ... ?
You can compare all you want with other distro but Slackware is secure. Remove any services that you don't need or may cause a problem with your use of the system. PAM and other forms can provide holes if not implemented properly thus providing a false sense. If you setup with proper security for your system via firewall, chkrootkit an even Tripwire then the system will be secure to level of the user(s) abilities. You as the admin must provide some system sense when implementing any distribution. If your servicing other OS then that will present other problems that must be addressed. Let's not compare apples to oranges.
If you follow good security practices, stay up to date, configur minimal access and permissions, secure options for each program etc, then slackware can be quite secure.
xinetd does not add additional security, it adds additional options that can help with security in certain contexts.
PAM can be quite useful, and would in some context be required. It is not needed to secure a system however, and by itself does not add to security.
For unbeatable MAC/RBAC security, in the vein of SELinux, you may want to look at RSBAC. It is a smaller project, and requires a custom kernel, but I have found it to work far better with slackware, and be compatible with the philosphy.
Basically, anything you want to control or limit access to and how is possible, limited only by your imagination. Worth a look.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.