<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>5.1.If something goes wrong</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="Linux-PAM_SAG.html" title="The Linux-PAM System Administrators' Guide"><link rel="up" href="sag-security-issues.html" title="Chapter5.Security issues"><link rel="prev" href="sag-security-issues.html" title="Chapter5.Security issues"><link rel="next" href="sag-security-issues-other.html" title="5.2.Avoid having a weak `other' configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.1.If something goes wrong</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sag-security-issues.html">Prev</a></td><th width="60%" align="center">Chapter5.Security issues</th><td width="20%" align="right"><a accesskey="n" href="sag-security-issues-other.html">Next</a></td></tr></table><hr></div><div class="section" title="5.1.If something goes wrong"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sag-security-issues-wrong"></a>5.1.If something goes wrong</h2></div></div></div><p>
<span class="emphasis"><em>Linux-PAM</em></span> has the potential
to seriously change the security of your system. You can
choose to have no security or absolute security (no access
permitted). In general, <span class="emphasis"><em>Linux-PAM</em></span>
errs towards the latter. Any number of configuration errors
can disable access to your system partially, or completely.
</p><p>
The most dramatic problem that is likely to be encountered when
configuring <span class="emphasis"><em>Linux-PAM</em></span> is that of
<span class="emphasis"><em>deleting</em></span> the configuration file(s):
<code class="filename">/etc/pam.d/*</code> and/or
<code class="filename">/etc/pam.conf</code>. This will lock you out of
your own system!
</p><p>
To recover, your best bet is to restore the system from a
backup or boot the system into a rescue system and correct
things from there.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sag-security-issues.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="sag-security-issues.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="sag-security-issues-other.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter5.Security issues</td><td width="20%" align="center"><a accesskey="h" href="Linux-PAM_SAG.html">Home</a></td><td width="40%" align="right" valign="top">5.2.Avoid having a weak `other' configuration</td></tr></table></div></body></html>
y~or5J ={Eeu磝Qk ᯘG{?+]ן?wM3X^歌>{7پK>on\jy R g/=fOroNVv~Y+ NGuÝHWyw[eQʨSb> >}Gmx[o[<{Ϯ_qF vM IENDB`
