<?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>Securism Blog &#187; ubuntu</title>
	<atom:link href="http://blog.securism.com/tag/ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.securism.com</link>
	<description>Simple Security.</description>
	<lastBuildDate>Fri, 23 Jul 2010 18:17:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Gnome Do Microblogging Plugin Authenticates Over Clear Text</title>
		<link>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/</link>
		<comments>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/#comments</comments>
		<pubDate>Fri, 30 Jan 2009 21:52:04 +0000</pubDate>
		<dc:creator>Ben Hagen</dc:creator>
				<category><![CDATA[Attacks]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blog.securism.com/?p=178</guid>
		<description><![CDATA[I love the Gnome productivity tool Gnome Do. Its great! What&#8217;s not so great is the fact that the installation default Twitter plugin &#8220;Microblogging (Twitter)&#8221; version 1.0 authenticates to Twitter over clear text. In general, its a great plugin&#8230; easy to post updates and wonderful balloon popups when friends post their&#8217;s&#8230; but this is a [...]]]></description>
			<content:encoded><![CDATA[<p>I love the Gnome productivity tool <a href="http://do.davebsd.com/">Gnome Do</a>. Its great! What&#8217;s not so great is the fact that the installation default Twitter plugin &#8220;<a href="http://do.davebsd.com/wiki/index.php?title=Microblog_Plugin">Microblogging (Twitter)</a>&#8221; version 1.0 authenticates to Twitter over clear text. In general, its a great plugin&#8230; easy to post updates and wonderful balloon popups when friends post their&#8217;s&#8230; but this is a killer problem.</p>
<p>I&#8217;ve filed a bug report with the plugins group <a href="https://bugs.launchpad.net/do-plugins/+bug/323364">here</a>.</p>
<p>With the ubiquity of wireless networks and the ease of promiscuously monitoring wireless networks, it is no longer acceptable to authenticate over clear text. Twitter shouldn&#8217;t allow authentications over none SSL channels, and applications shouldn&#8217;t support them even if non-SSL is supported. I discovered this while a friend was toying around with Kismet at a local cafe. I typically connect to an OpenSSL VPN whenever I use public networks, but due to the nature of the plugin it connects before I have a reasonable chance to enable the VPN&#8230; hence my friend captured my password. Fun.</p>
<p>I would also like to take this oppurtunity to remove any liability from myself for anything posted to my Twitter account in the future <img src='http://blog.securism.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOW-TO: Cutting edge wireless drivers in Ubuntu</title>
		<link>http://blog.securism.com/2009/01/how-to-cutting-edge-wireless-drivers-in-ubuntu/</link>
		<comments>http://blog.securism.com/2009/01/how-to-cutting-edge-wireless-drivers-in-ubuntu/#comments</comments>
		<pubDate>Wed, 28 Jan 2009 23:53:09 +0000</pubDate>
		<dc:creator>Ben Hagen</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[source]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[wireless drivers]]></category>

		<guid isPermaLink="false">http://blog.securism.com/?p=104</guid>
		<description><![CDATA[MADWIFI has been the wireless driver of choice for wireless hacking for quite a while, but recently a lot of development time has been moved to the official kernel wireless subsystem drivers. They are slowly gaining and surpassing MADWIFI&#8217;s functionality, and are generally more supported and stable. One downside to these drivers is that recompiling [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://madwifi.org/">MADWIFI</a> has been the wireless driver of choice for wireless hacking for quite a while, but recently a lot of development time has been moved to the official kernel wireless subsystem drivers. They are slowly gaining and surpassing MADWIFI&#8217;s functionality, and are generally more supported and stable. One downside to these drivers is that recompiling the kernel is time and labor intensive and waiting for a distro&#8217;s kernel update can put you behind the curve in recent driver functionality.</p>
<p>The <a href="http://linuxwireless.org/en/users/Download">COMPAT-WIRELESS</a> project pre-packages the latest wireless code as loadable kernel drivers on a (near) daily basis. This is a convenient way to download pre-patched and archived source&#8230; but in order to get the most recent changes (as they are committed) you  have to pull the source directly from the kernel.org <a href="http://www.google.com/url?sa=t&#038;source=web&#038;ct=res&#038;cd=1&#038;url=http%3A%2F%2Fgit-scm.com%2F&#038;ei=X9V8SbqaK9K1kAXYvY2mAQ&#038;usg=AFQjCNHBOAWIJWLQ6wmj_GErAgGzWCkTbA&#038;sig2=EiesuEOOnf1tY1cQqEsfoA">GIT</a> tree. <a href="http://en.wikipedia.org/wiki/Git_%28software%29">GIT is a code versioning system</a> similar to CVS, SVN, Bazaar, etc. Below is a simple example of how to do this and compile / install the code. I&#8217;m writing this from an Ubuntu installation, but the same concepts should work on other distros. This isn&#8217;t an especially difficult process, but it isn&#8217;t necessarily obvious either.</p>
<p>There are a few prerequisites for the below instructions to work correctly:</p>
<ul>
<li>
<p class="line862">Kernel greater than 2.6.21</p>
</li>
<li>
<p class="line862">Kernel headers (&#8220;apt-get install linux-headers-generic&#8221; in Ubuntu)</p>
</li>
<li>
<p class="line862">Build tools (&#8220;apt-get install build-essential&#8221; in Ubuntu)</p>
</li>
</ul>
<p>1. Make a new directory and clone the source trees:</p>
<pre style="padding-left: 30px;">mkdir wireless-testing
cd wireless-testing
git clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
git clone git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/compat-wireless-2.6.git</pre>
<p>2. Make the packages</p>
<pre style="padding-left: 30px;">cd compat-wireless-2.6
export GIT_TREE=../wireless-testing
scripts/admin-update.sh
make</pre>
<p>3. Install</p>
<pre style="padding-left: 30px;">cd compat-wireless-2.6
sudo make install</pre>
<p>4. Update and repeat steps 2-3 when you want the latest and greatest</p>
<pre style="padding-left: 30px;">cd wireless-testing
git-pull
cd ../compat-wireless-2.6
git-pull</pre>
<p>After step 3 you can try reloading the modules dynamically by running &#8220;make unload&#8221; and &#8220;make load&#8221; but this probably won&#8217;t work if you&#8217;re currently using your wireless drivers. Your best bet is to reboot your machine. You can confirm that you&#8217;re running the new(er) drivers by listing your kernel modules and look for the mac80211 module.</p>
<pre style="padding-left: 30px;">lsmod | grep mac80211
modinfo mac80211</pre>
<p>If there are problems you can uninstall the drivers by running &#8220;make uninstall&#8221; from the compat-wireless-2.6 directory. Hope this is helpful!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.securism.com/2009/01/how-to-cutting-edge-wireless-drivers-in-ubuntu/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
