System Administation: Maximizing System Security, Part 1
Package ftp Location COPS ftp.cert.org:/pub/tools/cops Courtney ftp.best.com:/pub/lat Crack ftp.cert.org:/pub/tools/crack Gabriel ftp.best.com:/pub/lat Merlin ciac.llnl.gov:/pub/ciac/sectools/unix/merlin Netscape ftp.netscape.com:/netscape/unix npasswd ee.utah.edu:/admin/passwd/npasswd passwd+ ee.utah.edu:/admin/passwd/passwd+ Perl prep.ai.mit.edu:/pub/gnu Satan ftp.win.tue.nl:/pub/security shadow sunsite.unc.edu:/pub/Linux/system/Admin sudo sunsite.unc.edu:/pub/Linux/system/Admin swatch sierra.stanford.edu:/pub/sources TCP Wrappers ftp.win.tue.nl:/pub/security/tcp_wrapper Tripwire coast.cs.purdue.edu:/pub/COAST/Tripwire
Passwords are the primary way of securing user accounts on Linux systems. However, the protection offered by passwords is only as good as the passwords themselves. If a hacker decides to attack the accounts on your system, bad passwords are almost as bad as no passwords at all.
There are several things you can do to ensure that the password facility is providing the best protection it is capable of:
Make sure all active accounts have passwords and that system accounts not intended for user logins (e.g. bin) are disabled (do this by placing an asterisk in the password field for that account).
Secure the encoded versions of the system's passwords by using a shadow password file.
Educate users about keeping passwords secret, selecting hard-to-crack passwords, changing passwords as necessary, using different passwords at different sites, and similar security practices. Institute password aging and/or new password obscurity checking if appropriate.
The first item is self-explanatory; we look at the others in detail.
Shadow password files are designed to correct the security hole resulting from the normal password file being world-readable. Everyone needs to be able to view the contents of /etc/passwd so that things like file ownership displays properly (UIDs are translated into usernames). However, since the file is readable, anyone can make a copy of it. This means someone with legitimate or illegitimate access to an ordinary user account can copy it and attempt to crack the passwords of more powerful accounts at his leisure.
A shadow password file facility removes the encoded passwords from the normal password file and places them in another file, conventionally /etc/shadow, which can be read only by root. The shadow package provides shadow password file capabilities for a variety of UNIX systems including Linux. It is included in some Linux distributions by default. It includes replacements for the login, passwd, and su commands as well as many utilities for creating and manipulating the shadow password file and account entries within it.
Building the shadow package is quite straightforward. If you've retrieved a version that has been ported to Linux, you'll generally only have to modify the config.h file. I recommend the following settings (culled from various points within that file):
/* Use shadow password file. */ #define SHADOWPWD /* Use up to 16 char. passwords. */ #define DOUBLESIZE /* Enable password aging checks. */ #define AGING /* Log events to syslog facility. */ #define USE_SYSLOG /* Support for remote logins. */ #define RLOGIN #define UT_HOST /* Data file for most recent login time records */ #define LASTFILE "/var/adm/lastlog"
Once the package is built and installed, the pwconv command may be used to create an initial /etc/shadow file. It creates the files /etc/npasswd and /etc/nshadow. The former is an altered version of the original password file in which the password field in each entry has been replaced by an x; the latter is the corresponding shadow password file. In order to activate them, you must rename them by hand:
# cd /etc # mv passwd passwd.prev # cp npasswd passwd # cp nshadow shadow
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)




41 min 12 sec ago
1 hour 15 min ago
2 hours 13 min ago
3 hours 4 min ago
7 hours 5 min ago
10 hours 53 min ago
11 hours 1 min ago
13 hours 15 min ago
15 hours 45 min ago
1 day 1 hour ago