source: postlfs/security/security.xml@ e1d7dec

10.0 10.1 11.0 11.1 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk upgradedb v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/test-20220226
Last change on this file since e1d7dec was e1d7dec, checked in by Larry Lawrence <larry@…>, 19 years ago

update libungif intro

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1073 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 1.1 KB
Line 
1<chapter id="postlfs-security">
2<?dbhtml filename="security.html" dir="postlfs"?>
3<title>Security</title>
4
5<para>Security takes many forms in a computing environment. This chapter
6gives examples of three different types of security; access, prevention
7and detection. Access for users is usually handled by
8<command>login</command> or an application designed to handle the login
9function. In this chapter, we show how to enhance
10<command>login</command> by setting policies with
11<application><acronym>PAM</acronym></application> modules. Access via networks
12can also be secured by policies set by
13<application>iptables</application>. Prevention of breaches, like
14trojans, are assisted by applications like <application>gnupg</application>,
15specifically the ability to confirm signed packages, which prevents
16modification of the tarball after the packager creates it. Finally, we touch on
17detection with a package that stores "signatures" and then regenerates those
18"signatures" and compares for files that have been changed.</para>
19
20&shadow;
21&Linux_PAM;
22&iptables;
23&postlfs-security-fw;
24&gnupg;
25&tripwire;
26&postlfs-security-syslog;
27
28</chapter>
Note: See TracBrowser for help on using the repository browser.