<?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>Geekdom</title>
	<atom:link href="http://geekdom.wesmo.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://geekdom.wesmo.com</link>
	<description>Geeks of the World Unite!</description>
	<lastBuildDate>Tue, 17 Aug 2010 20:37:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Squid + NTLM authentication failing in a Windows 2008 Domain Environment</title>
		<link>http://geekdom.wesmo.com/2010/08/17/squid-ntlm-authentication-failing-in-a-windows-2008-domain-environment/</link>
		<comments>http://geekdom.wesmo.com/2010/08/17/squid-ntlm-authentication-failing-in-a-windows-2008-domain-environment/#comments</comments>
		<pubDate>Tue, 17 Aug 2010 20:37:22 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[ntlm authentication]]></category>
		<category><![CDATA[samba]]></category>
		<category><![CDATA[squid]]></category>
		<category><![CDATA[winbind]]></category>

		<guid isPermaLink="false">http://geekdom.wesmo.com/?p=176</guid>
		<description><![CDATA[Even the latest versions of Samba via yum updates has troubles talking to Windows 2008 Domain Controllers.  A partial solution was found here. Upon an upgrade to the AD environment, winbind starts throwing errors like the one below: Aug 16 16:20:38 ourhost winbindd[2459]: rpc_api_pipe: Remote machine OURDOMAINCONTROLLER.ourdomain.com pipe \NETLOGON fnum 0x800areturned critical error. Error was [...]]]></description>
			<content:encoded><![CDATA[<p>Even the latest versions of Samba via yum updates has troubles talking to Windows 2008 Domain Controllers.  A partial solution was found <a href="http://lanestechblog.blogspot.com/2010/06/ntstatuspipedisconnected-with-winbind.html">here</a>.</p>
<p>Upon an upgrade to the AD environment, winbind starts throwing errors like the one below:</p>
<pre>Aug 16 16:20:38 ourhost winbindd[2459]:   rpc_api_pipe: Remote machine OURDOMAINCONTROLLER.ourdomain.com pipe \NETLOGON fnum 0x800areturned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
</pre>
<p>After the upgrade to Samba / winbind, squid started throwing the following authentication errors:</p>
<pre>Aug 16 16:39:58 ourhost (ntlm_auth):   Login for user [ourdomain\[username]@[DESKTOPHOST] failed due to [winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/lib/samba/winbindd_privileged are set correctly.]
</pre>
<p>In the end, it turns out that the latest Samba installation resolves this problem:</p>
<ul>
<li>/etc/init.d/squid stop</li>
<li>/etc/init.d/winbind stop</li>
<li>cp /etc/samba/smb.conf /tmp/smb.conf</li>
<li>yum erase samba samba-common</li>
<li>yum install samba3x samba3x-client –disablerepo=rpmforge</li>
<li>cp /tmp/smb.conf /etc/samba/smb.conf</li>
<li>setfacl -m u:squid:rx /var/lib/samba/winbindd_privileged</li>
<li>kinit Administrator@OURDOMAIN.COM</li>
<li>net ads join -U Administrator</li>
<li>/etc/init.d/winbind start</li>
<li>wbinfo -u (to test to make sure you see user names)</li>
<li>/etc/init.d/squid start</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://geekdom.wesmo.com/2010/08/17/squid-ntlm-authentication-failing-in-a-windows-2008-domain-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Generating self signed SSL certificates</title>
		<link>http://geekdom.wesmo.com/2010/08/14/generating-self-signed-ssl-certificates/</link>
		<comments>http://geekdom.wesmo.com/2010/08/14/generating-self-signed-ssl-certificates/#comments</comments>
		<pubDate>Sat, 14 Aug 2010 14:44:01 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[certificates]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[self signed]]></category>

		<guid isPermaLink="false">http://geekdom.wesmo.com/?p=165</guid>
		<description><![CDATA[Creating a self signed certificate is relatively easy. Once the certificate of authority has been established, generating certificates off of it is rather straight forward. However, the commands can get lost over time since one is not generating certificates every day. To simplify matters, a quick script handles all of the necessary steps to generate [...]]]></description>
			<content:encoded><![CDATA[<p>Creating a self signed certificate is relatively easy.  Once the certificate of authority has been established, generating certificates off of it is rather straight forward.  However, the commands can get lost over time since one is not generating certificates every day.  To simplify matters, a quick script handles all of the necessary steps to generate the certificate.</p>
<pre>#!/bin/sh
#
#  MakePEM                                              Author: Rich West
#                                                       Rich.West@wesmo.com
#
# A simple script to generate a self signed certificate that does not require
# a passphrase in order to use it.
################################################################################

##
# Make sure we are started as we should be.
##
if [ "X"$1 == "X" ] || [ "X"$2 == "X" ] || [ "X"$3 == "X" ]; then
        echo "Usage: $0 &lt;serial number&gt; &lt;days&gt; &lt;certificate_file.pem&gt;"
        echo
        exit;
fi

##
# Set our defaults
##
ssldir=/usr/bin
conf=/etc/ssl/openssl.cnf
certs_dir=/etc/ssl/certs
serial=$1
days=$2
cert=$3

##
# Generate the certificate.
##
$ssldir/openssl req -new -x509 -days $days -config $conf \
-out $certs_dir/$cert -keyout $certs_dir/$cert \
-set_serial $serial
##
# Sign the certificate
##
$ssldir/openssl gendh &gt;&gt; $certs_dir/$cert

##
# We need randomness
##
$ssldir/openssl gendh -rand \
`test -c /dev/urandom &amp;&amp; echo /dev/urandom` 1024 &gt;&gt; $certs_dir/$cert

##
# For sanity sake, display the contents of the generated and signed certificate.
##
echo
echo "Your new certificate is as follows:"
$ssldir/openssl x509 -subject -dates -fingerprint -noout \
-in $certs_dir/$cert

##
# Make it only readable by the owner.
##
chmod 600 $certs_dir/$cert</pre>
]]></content:encoded>
			<wfw:commentRss>http://geekdom.wesmo.com/2010/08/14/generating-self-signed-ssl-certificates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Renew Self-Signed SSL Certificate on Linux</title>
		<link>http://geekdom.wesmo.com/2010/08/14/renew-self-signed-ssl-certificate-on-linux/</link>
		<comments>http://geekdom.wesmo.com/2010/08/14/renew-self-signed-ssl-certificate-on-linux/#comments</comments>
		<pubDate>Sat, 14 Aug 2010 14:34:26 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[certificates]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[renew]]></category>
		<category><![CDATA[self signed]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://geekdom.wesmo.com/?p=163</guid>
		<description><![CDATA[If you are receiving a similar email to the one below, it can be a bit misleading if you are using self-signed certificates. The warning below really only applies to purchased certificates, not ones that have been home grown. If you are using self signed certificates, there is no option to renew it. You just [...]]]></description>
			<content:encoded><![CDATA[<p>If you are receiving a similar email to the one below, it can be a bit misleading if you are using self-signed certificates.  The warning below really only applies to purchased certificates, not ones that have been home grown.</p>
<p>If you are using self signed certificates, there is no option to renew it.  You just can&#8217;t (you&#8217;re the certificate authority anyhow), so you must generate a completely new certificate.</p>
<pre>################# SSL Certificate Warning ################

  Certificate for hostname 'your.host.name', in file:
     /etc/ssl/certs/https_www.pem

  The certificate needs to be renewed; this can be done
  using the 'genkey' program.

  Browsers will not be able to correctly connect to this
  web site using SSL until the certificate is renewed.

 ##########################################################
                                  Generated by certwatch(1)</pre>
]]></content:encoded>
			<wfw:commentRss>http://geekdom.wesmo.com/2010/08/14/renew-self-signed-ssl-certificate-on-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows 7 and Squid via NTLM authentication via Samba</title>
		<link>http://geekdom.wesmo.com/2010/07/16/windows-7-and-squid-via-ntlm-authentication-via-samba/</link>
		<comments>http://geekdom.wesmo.com/2010/07/16/windows-7-and-squid-via-ntlm-authentication-via-samba/#comments</comments>
		<pubDate>Sat, 17 Jul 2010 01:42:04 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[ntml]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[proxy server]]></category>
		<category><![CDATA[samba]]></category>
		<category><![CDATA[squid]]></category>
		<category><![CDATA[wpad]]></category>
		<category><![CDATA[wpad.dat]]></category>

		<guid isPermaLink="false">http://geekdom.wesmo.com/?p=161</guid>
		<description><![CDATA[Getting Windows 7 to talk to a squid proxy server which uses ntml authentication via samba can be a little tricky. Control Panel -&#62; System and Security -&#62; Administrative Tools -&#62; Local Security Policy -&#62; Local Policy -&#62; Security Options Find &#8220;Network security: LAN Manager authentication level &#8221; and set it to: Send LM &#38; NTLM responses Find [...]]]></description>
			<content:encoded><![CDATA[<p>Getting Windows 7 to talk to a squid proxy server which uses ntml authentication via samba can be a little tricky.</p>
<p>Control Panel -&gt; System and Security -&gt; Administrative Tools -&gt; Local Security Policy -&gt; Local Policy -&gt; Security Options</p>
<p>Find &#8220;Network security: LAN Manager authentication level &#8221; and set it to: Send LM &amp; NTLM responses<br />
Find &#8220;Minimum session security for NTLM SSP&#8221; and set it to: Disable Require 128-bit encryption</p>
]]></content:encoded>
			<wfw:commentRss>http://geekdom.wesmo.com/2010/07/16/windows-7-and-squid-via-ntlm-authentication-via-samba/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iPhone SMS Archiving</title>
		<link>http://geekdom.wesmo.com/2010/01/22/iphone-sms-archiving/</link>
		<comments>http://geekdom.wesmo.com/2010/01/22/iphone-sms-archiving/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 02:33:53 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[archiving]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[view]]></category>

		<guid isPermaLink="false">http://geekdom.wesmo.com/?p=151</guid>
		<description><![CDATA[The iPhone has some amazing features, and, sadly, it is lacking in some key ones.  Jailbreaking is always an option, but, really, shouldn&#8217;t this amazing phone do the most simplistic of tasks without having to go around the entire system? For example, the iPhone has limited vibration functions.  Compared to a Blackberry in this regard, [...]]]></description>
			<content:encoded><![CDATA[<p>The iPhone has some amazing features, and, sadly, it is lacking in some key ones.  Jailbreaking is always an option, but, really, shouldn&#8217;t this amazing phone do the most simplistic of tasks without having to go around the entire system?</p>
<p>For example, the iPhone has limited vibration functions.  Compared to a Blackberry in this regard, where the typical IT professional needs to be discrete in meetings but still needs to know the difference between an email (one vibration), a blackberry message (two quick vibrations), or an SMS message (three quick vibrations) in order to judge the urgency.  The iPhone just does a short vibrate.. once.</p>
<p>With that aside, the phone is still amazing.  Fix the alert options, and it could be a real contender in the office environment.</p>
<p>SMS message conversations blow the doors off of any other phone.  But how does one back these up? Low-and-behold, iTunes syncs these up behind the scenes, but it doesn&#8217;t provide an interface to them. Say you want to preserve them, but don&#8217;t want them piling up on the phone.</p>
<p>A small script in perl on a linux box will happily take that file and format it for you.  However, it does not have a way to determine who each party is.  It will display all conversations to/from a particular person.  Re-run it for preserved conversations with others.</p>
<p><a href="/wp-content/uploads/2010/01/sms_cleaner.pl.txt">sms_cleaner.pl</a></p>
]]></content:encoded>
			<wfw:commentRss>http://geekdom.wesmo.com/2010/01/22/iphone-sms-archiving/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
