<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://lopsa.org">
<channel>
 <title>League of Professional System Administrators - Operating System</title>
 <link>http://lopsa.org/taxonomy/term/47/0</link>
 <description>Operating System Security</description>
 <language>en</language>
<item>
 <title>Solaris in.telnetd</title>
 <link>http://lopsa.org/node/1188</link>
 <description>&lt;p&gt;
By now, I&#039;m sure everyone with a Sun system has heard about the widely disseminated vulnerability in Solaris 10&#039;s telnetd code.  My experiences in managing that issue from early announcement to patch might serve as a warning/aide to others who are looking at security models.
&lt;/p&gt;
&lt;p&gt;
Several lessons were learned as a result of the experience.  Some were things that worked well, some were things that I feel would hopefully be improved.
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; In the event of a zero day disclosure, the vendor is likely to be among the last to admit to the issue.  Sun did not issue an alert until they had something more than &amp;quot;shut down telnetd&amp;quot;  Alternative means of learning of security vulnerabilities are a must.
&lt;/ul&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1188&quot; dc:identifier=&quot;http://lopsa.org/node/1188&quot; dc:title=&quot;Solaris in.telnetd&quot; trackback:ping=&quot;http://lopsa.org/trackback/1188&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <pubDate>Tue, 13 Feb 2007 14:09:27 -0800</pubDate>
 <author>alcourt</author>
</item>
<item>
 <title>NMAP</title>
 <link>http://lopsa.org/node/980</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Fast enumeration of network services
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://insecure.org/nmap&quot;&gt;insecure.org/nmap&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Sun, 2007-01-14 10:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Active
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Nmap is a powerful tool for discovering hosts on a network and enumerating what service they are offering. This can be used to find vulnerable systems, to locate rogue services on your network or simply for a first step in troubleshooting.&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/980&quot; dc:identifier=&quot;http://lopsa.org/node/980&quot; dc:title=&quot;NMAP&quot; trackback:ping=&quot;http://lopsa.org/trackback/980&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/140">Communications</category>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/21">Networking</category>
 <category domain="http://lopsa.org/taxonomy/term/24">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/119">Protocols</category>
 <category domain="http://lopsa.org/taxonomy/term/44">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/114">TCP</category>
 <category domain="http://lopsa.org/taxonomy/term/23">UDP</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <category domain="http://lopsa.org/taxonomy/term/137">User Security</category>
 <category domain="http://lopsa.org/taxonomy/term/134">Visualization</category>
 <category domain="http://lopsa.org/taxonomy/term/27">Windows</category>
 <pubDate>Sun, 14 Jan 2007 09:50:04 -0800</pubDate>
 <author>dklein</author>
</item>
<item>
 <title>sudosh</title>
 <link>http://lopsa.org/sudosh</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Sudosh records all keystrokes and output and can play back the session as just like a VCR.
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://sourceforge.net/projects/sudosh/&quot;&gt;sourceforge.net/projects/sudosh/&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Mon, 2004-09-20 19:12
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Stable
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;sudosh is used with sudo(8) to exec the user&#039;s shell specified in /etc/passwd as root.  sudosh makes use of the built-in script(5) command to log session data to syslog.&lt;/p&gt;
&lt;p&gt;Companies that have a team of system administrators and a large number of servers face a difficult problem:  root access.&lt;/p&gt;
&lt;p&gt;The most common solution is to distribute the root password to the system administrators and contain them in a wheel group.  With the recent requirements of Sarbanes and Oxley this becomes quickly impossible because the root password must be changed every 3 months.&lt;/p&gt;
&lt;p&gt;The other option is to use sudo.  Sudo works great.  It&#039;s actually too good.  This is why I created sudosh.  Sudo doesn&#039;t allow you to do shell type things that system administrators are used to.  The following example is a real command that is used during an AIX data migration:&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/sudosh&quot; dc:identifier=&quot;http://lopsa.org/sudosh&quot; dc:title=&quot;sudosh&quot; trackback:ping=&quot;http://lopsa.org/trackback/904&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/143">Security</category>
 <pubDate>Wed, 15 Nov 2006 21:15:38 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Parts of security</title>
 <link>http://lopsa.org/node/870</link>
 <description>&lt;p&gt;So I&#039;ve been working on an internal security review and discovering that the bulk of the issues I run into stem from the fact that the users don&#039;t seem to understand the need for an audit trail.&lt;/p&gt;
&lt;p&gt;To me, security consists of confidentiality, authenticity, and the auditability.  It&#039;s easy to explain the need for the first two, or at least, people don&#039;t need me to explain why they are a part of security.  I get the normal &quot;But we have a firewall, why do we need security?&quot;, but that&#039;s minor.  But when it comes to issues that center around preserving an audit trail, I get blank stares and a complete lack of understanding as if they just don&#039;t understand at all what I&#039;m talking about or why a security review would be remotely concerned with maintaining a record of who did what on a system.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/870&quot; dc:identifier=&quot;http://lopsa.org/node/870&quot; dc:title=&quot;Parts of security&quot; trackback:ping=&quot;http://lopsa.org/trackback/870&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <pubDate>Fri, 03 Nov 2006 16:52:48 -0800</pubDate>
 <author>alcourt</author>
</item>
<item>
 <title>SSL Intro for techs; mini OpenSSL CA</title>
 <link>http://lopsa.org/SSLIntro</link>
 <description>&lt;h1&gt;
Sysadmin&#039;s Basic Guide to SSL Certificates and Authorities
&lt;/h1&gt;
&lt;p&gt;
Intended audience: system administrators who know roughly what SSL/TLS is and can use SSH and OpenPGP products (such as GnuPG) and who now want to know more and perhaps issue local certificates.  You should know what public-key cryptography is, but are not expected to be able to follow any math (no equations herein) -- this is about using the stuff, not understanding the underlaying principles.  You understand that &amp;quot;encrypt&amp;quot; is scrambling and &amp;quot;decrypt&amp;quot; is descrambling.
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/SSLIntro&quot; dc:identifier=&quot;http://lopsa.org/SSLIntro&quot; dc:title=&quot;SSL Intro for techs; mini OpenSSL CA&quot; trackback:ping=&quot;http://lopsa.org/trackback/858&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <pubDate>Sat, 28 Oct 2006 17:44:06 -0700</pubDate>
 <author>syscomet</author>
</item>
<item>
 <title>rsyslog</title>
 <link>http://lopsa.org/tool_rsyslog</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Rsyslog is an enhanced multi-threaded syslogd supporting, among others, MySQL, syslog/tcp, RFC 3195, permitted sender lists, fil
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://www.rsyslog.com&quot;&gt;www.rsyslog.com&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Fri, 2005-09-23 20:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Active
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Rsyslog is an enhanced multi-threaded syslogd supporting, among others, MySQL, syslog/tcp, RFC 3195, permitted sender lists, filtering on any message part, and fine grain output format control. It is quite compatible to stock sysklogd and can be used as a drop-in replacement. Its advanced features make it suitable for enterprise-class, encryption protected syslog relay chains while at the same time being very easy to setup for the novice user. An optional web interface - &lt;a href=&quot;http://www.phplogcon.com/&quot;&gt;phpLogCon&lt;/a&gt; - can be used to visualize all data online.&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/tool_rsyslog&quot; dc:identifier=&quot;http://lopsa.org/tool_rsyslog&quot; dc:title=&quot;rsyslog&quot; trackback:ping=&quot;http://lopsa.org/trackback/754&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <category domain="http://lopsa.org/taxonomy/term/140">Communications</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/24">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/150">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/44">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/143">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Sun, 27 Aug 2006 20:47:42 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Log Analysis</title>
 <link>http://lopsa.org/LogAnalysis</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Web page referencing log analysis tools
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://loganalysis.org&quot;&gt;loganalysis.org&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Fri, 2003-07-25 21:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;&quot;Log Analysis is one of the great overlooked aspects of operational computer security. Many organizations spend hundreds of thousands of dollars on intrusion detection systems (IDS) deployments - but still ignore their firewall logs. Why? Because the tools and knowledge to make use of that data are often not there, or the tools that exist are too inconvenient. You should expect that to change. Right now, IDS vendors are up against the wall with the volumes of data they produce; the next wave in security is to try to usefully correlate and process the contents of multiple logs.&quot;&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/LogAnalysis&quot; dc:identifier=&quot;http://lopsa.org/LogAnalysis&quot; dc:title=&quot;Log Analysis&quot; trackback:ping=&quot;http://lopsa.org/trackback/714&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/151">Log Data</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/44">Security</category>
 <pubDate>Tue, 25 Jul 2006 09:29:44 -0700</pubDate>
 <author>doug</author>
</item>
</channel>
</rss>
