<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>This is a .com</title>
	<atom:link href="http://www.thisisa.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thisisa.com</link>
	<description>This is a blog</description>
	<lastBuildDate>Mon, 23 Apr 2012 21:52:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Ubuntu 12.04 Precise: ldap with a server that supports openssl not gnutls ?</title>
		<link>http://www.thisisa.com/2012/04/21/ubuntu-12-04-precise-ldap-with-a-server-that-supports-openssl-not-gnutls/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ubuntu-12-04-precise-ldap-with-a-server-that-supports-openssl-not-gnutls</link>
		<comments>http://www.thisisa.com/2012/04/21/ubuntu-12-04-precise-ldap-with-a-server-that-supports-openssl-not-gnutls/#comments</comments>
		<pubDate>Sat, 21 Apr 2012 07:00:21 +0000</pubDate>
		<dc:creator>thisisa</dc:creator>
				<category><![CDATA[LDAP]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[ldap]]></category>
		<category><![CDATA[libldap]]></category>
		<category><![CDATA[openssl]]></category>
		<category><![CDATA[precise]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://www.thisisa.com/?p=25</guid>
		<description><![CDATA[If you need to use ldap but your server does not support gnutls and instead it would like to use ssl. Use the following ppa https://launchpad.net/~tmortensen/+archive/ppa Full Install Instructions Add the ppa and update apt apt-get install python-software-properties add-apt-repository ppa:tmortensen/ppa apt-get update Install libldap and nslcd apt-get install ldap-utils nslcd Setup your config files and <a href='http://www.thisisa.com/2012/04/21/ubuntu-12-04-precise-ldap-with-a-server-that-supports-openssl-not-gnutls/' class='excerpt-more'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>If you need to use ldap but your server does not support gnutls and instead it would like to use ssl.</p>
<p>Use the following ppa</p>
<p>https://launchpad.net/~tmortensen/+archive/ppa</p>
<h4>Full Install Instructions</h4>
<h5>Add the ppa and update apt</h5>
<pre>apt-get install python-software-properties
add-apt-repository ppa:tmortensen/ppa
apt-get update</pre>
<p>Install libldap and nslcd</p>
<pre>apt-get install ldap-utils nslcd</pre>
<p>Setup your config files and you should be set.</p>
<p>/etc/nslcd.conf</p>
<p>/etc/ldap/ldap.conf</p>
<p>For nsswitch change the passwd,group,shadow lines from compat to<br />
/etc/nsswitch.conf</p>
<pre>passwd:         files ldap
group:          files ldap
shadow:         files ldap</pre>
<p>By default when a user logs in without a home directory you will get an error. To have pam auto create homes on first login.</p>
<p>Edit these two files and add the following line to each:<br />
/etc/pam.d/common-seesion<br />
/etc/pam.d/common-session-noninteractive</p>
<pre>session required pam_mkhomedir.so skel=/etc/skel umask=0022</pre>
<p>&nbsp;</p>
<p>You can restrict access by group using ssh.<br />
/etc/ssh/sshd_config</p>
<pre>AllowGroups LDAPGroupName localaccount</pre>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thisisa.com/2012/04/21/ubuntu-12-04-precise-ldap-with-a-server-that-supports-openssl-not-gnutls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>remote syslog via rsyslogs relp module</title>
		<link>http://www.thisisa.com/2012/03/05/remote-syslog-via-rsyslogs-relp-module/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=remote-syslog-via-rsyslogs-relp-module</link>
		<comments>http://www.thisisa.com/2012/03/05/remote-syslog-via-rsyslogs-relp-module/#comments</comments>
		<pubDate>Mon, 05 Mar 2012 07:48:21 +0000</pubDate>
		<dc:creator>thisisa</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Syslog]]></category>
		<category><![CDATA[relp]]></category>
		<category><![CDATA[rsyslog]]></category>

		<guid isPermaLink="false">http://www.thisisa.com/?p=11</guid>
		<description><![CDATA[This is a config for rsyslogd with RELP I am setting up rsyslog to send all of its logs to a remote log collection server where I will store them on disk. Later I will talk about how I have used logstash to pull in these files once on the system. I won&#8217;t bother posting <a href='http://www.thisisa.com/2012/03/05/remote-syslog-via-rsyslogs-relp-module/' class='excerpt-more'>[...]</a>]]></description>
			<content:encoded><![CDATA[<h1>This is a config for rsyslogd with RELP</h1>
<p>I am setting up rsyslog to send all of its logs to a remote log collection server where I will store them on disk.</p>
<p>Later I will talk about how I have used logstash to pull in these files once on the system.</p>
<p>I won&#8217;t bother posting the default lines almost all rsyslog config files will have.</p>
<p>I setup some basic udp collectors for legacy devices</p>
<address style="text-align: left; padding-left: 30px;">$ModLoad imudp<br />
$UDPServerAddress 0.0.0.0<br />
$UDPServerRun 514</address>
<p>Then load the relp module to provide more reliable tcp logging.  I am going to have mine communicate on tcp port 1088</p>
<p style="padding-left: 30px;">$ModLoad imrelp<br />
$InputRELPServerRun 1088</p>
<p>The other two custom options I have set are for preserving fqdn because I need the full name to differentiate devices in different cities.</p>
<p style="padding-left: 30px;">$PreserveFQDN on</p>
<p>I also tun off the message reduction to allow the systems I plan to implements better count messages.</p>
<p style="padding-left: 30px;">$RepeatedMsgReduction off</p>
<p>Now on the client side all I have to do is include the relp module again and forward all messages via *.*</p>
<p style="padding-left: 30px;">$ModLoad omrelp<br />
*.* :omrelp:remotesyslog.example.org:1088;RSYSLOG_ForwardFormat</p>
<p>I am also using the RSYSLOG_ForwardFormat to preserve the severity and priority when the message is sent.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thisisa.com/2012/03/05/remote-syslog-via-rsyslogs-relp-module/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

