<?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>Ubuntu For Free &#187; Canonical</title>
	<atom:link href="http://www.forwardyouth.com/ubuntu/category/canonical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.forwardyouth.com/ubuntu</link>
	<description>A blog covering the Ubuntu Linux distro for you and your wallet.</description>
	<lastBuildDate>Thu, 04 Mar 2010 01:01:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The OpenSSL Vulnerability</title>
		<link>http://www.forwardyouth.com/ubuntu/the-openssl-vulnerability/</link>
		<comments>http://www.forwardyouth.com/ubuntu/the-openssl-vulnerability/#comments</comments>
		<pubDate>Tue, 20 May 2008 14:00:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Canonical]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[OpenSSH]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security advisor]]></category>
		<category><![CDATA[security alert]]></category>
		<category><![CDATA[ssh-copy-id]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.forwardyouth.com/ubuntu/?p=105</guid>
		<description><![CDATA[I recently established my network to use SSH connections. My three Ubuntu systems I discovered were using weak keys that had been generated using the flawed packages. If you haven&#8217;t been paying attention, Canonical issued USN-612-1 on 5/13/2008. If you&#8217;re using keys that have been generated since September 2006, it&#8217;s likely that you need to [...]]]></description>
			<content:encoded><![CDATA[<p>I recently established my network to use SSH connections. My three Ubuntu systems I discovered were using weak keys that had been generated using the flawed packages. If you haven&#8217;t been paying attention, Canonical issued <a title="CVE-2008-0166" href="http://www.ubuntu.com/usn/usn-612-1">USN-612-1</a> on 5/13/2008. If you&#8217;re using keys that have been generated since September 2006, it&#8217;s likely that you need to regenerate all keys. If you have any doubts, I encourage you to regenerate all keys. It will affect any key used that was generated on a compromised system. The biggest trouble for me was getting OpenSSL and OpenSSH-server packages to update. I used the ssh-copy-id command to make it the process easy for me.</p>
<a class="google_buzz"  
href="http://www.google.com/reader/link?url=http://www.forwardyouth.com/ubuntu/the-openssl-vulnerability/&title=The+OpenSSL+Vulnerability&srcURL=http://www.forwardyouth.com/ubuntu" target="_blank" rel="nofollow"><img
src="http://www.forwardyouth.com/ubuntu/wp-content/plugins/google-buzz-button-for-wordpress/images/google-buzz.png" alt="Google Buzz" /></a>]]></content:encoded>
			<wfw:commentRss>http://www.forwardyouth.com/ubuntu/the-openssl-vulnerability/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Kubuntu LTS Put On Hold for Hardy Heron</title>
		<link>http://www.forwardyouth.com/ubuntu/kubuntu-lts-put-on-hold-for-hardy-heron/</link>
		<comments>http://www.forwardyouth.com/ubuntu/kubuntu-lts-put-on-hold-for-hardy-heron/#comments</comments>
		<pubDate>Sun, 30 Dec 2007 20:07:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Canonical]]></category>
		<category><![CDATA[Community]]></category>
		<category><![CDATA[Hardy Heron]]></category>
		<category><![CDATA[Kubuntu]]></category>
		<category><![CDATA[LTS]]></category>
		<category><![CDATA[Launchpad]]></category>
		<category><![CDATA[LiveCD]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[VirtualBox]]></category>

		<guid isPermaLink="false">http://www.forwardyouth.com/ubuntu/kubuntu-lts-put-on-hold-for-hardy-heron/</guid>
		<description><![CDATA[There&#8217;s been a great rift with the Canonical Community as of late surrounding Kubuntu. The update from KDE 3.5 to KDE 4.0 is such a great shift that Canonical feels they&#8217;re unable to commit to Long Term Support for Kubuntu 8.04. Frankly, I don&#8217; blame them. This is a pretty good move for them as [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been a great rift with the Canonical Community as of late surrounding Kubuntu. The update from KDE 3.5 to KDE 4.0 is such a great shift that Canonical feels they&#8217;re unable to commit to Long Term Support for Kubuntu 8.04. Frankly, I don&#8217; blame them. This is a pretty good move for them as far as any business relationships and future investors.</p>
<p>I don&#8217;t think it&#8217;s a problem. However, you kind of have to wonder how it affects the users who install using Ubuntu 8.04 and then add the kubuntu-desktop package, or will it be disabled?</p>
<p>Others have noted that there&#8217;s been a lack of reports from users with their experience regarding Hardy Heron. I noticed the torrent activity was kind of slacking. This is an excellent time for us to step up the testing on this. I suggest testing the .ISO image from a LiveCD and from some sort of virtualization application, such as VMWare or VirtualBox. If you&#8217;ve got the resources, it&#8217;s definitely appreciated for a full install and all the reports that you get from that experience.</p>
<p>I&#8217;ve encountered a few bugs that I&#8217;ve reported at <a href="http://bugs.launchpad.com">Launchpad</a>. Here I found other users reporting the same kind of problems I experienced. I wasn&#8217;t able to find the bug reports doing a simple search, instead it found them for me when I attempted to report the bugs, so go ahead and just attempt to report the bug you encounter. If it doesn&#8217;t find it for you, someone will catch it in triage. So, to re-iterate. If you haven&#8217;t tried it yet, go ahead and take the time. This is one of the easiest ways to contribute to the community.</p>
<a class="google_buzz"  
href="http://www.google.com/reader/link?url=http://www.forwardyouth.com/ubuntu/kubuntu-lts-put-on-hold-for-hardy-heron/&title=Kubuntu+LTS+Put+On+Hold+for+Hardy+Heron&srcURL=http://www.forwardyouth.com/ubuntu" target="_blank" rel="nofollow"><img
src="http://www.forwardyouth.com/ubuntu/wp-content/plugins/google-buzz-button-for-wordpress/images/google-buzz.png" alt="Google Buzz" /></a>]]></content:encoded>
			<wfw:commentRss>http://www.forwardyouth.com/ubuntu/kubuntu-lts-put-on-hold-for-hardy-heron/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Security Alert &#8211; LoCo Teams Hosting Servers Compromised</title>
		<link>http://www.forwardyouth.com/ubuntu/security-alert-loco-teams-hosting-servers-compromised/</link>
		<comments>http://www.forwardyouth.com/ubuntu/security-alert-loco-teams-hosting-servers-compromised/#comments</comments>
		<pubDate>Wed, 08 Aug 2007 14:28:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Canonical]]></category>
		<category><![CDATA[LoCo Teams]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Server]]></category>

		<guid isPermaLink="false">http://www.forwardyouth.com/ubuntu/security-alert-loco-teams-hosting-servers-compromised/</guid>
		<description><![CDATA[If you&#8217;re a part of a any Ubuntu Loco Teams, you may have noticed that they&#8217;ve been down for a period. That&#8217;s because of a security breach. I encourage you to review these instructions for securing your system after the Ubuntu LoCo team hosts have been attacked.
]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a part of a any Ubuntu Loco Teams, you may have noticed that they&#8217;ve been down for a period. That&#8217;s because of a <a href="https://lists.ubuntu.com/archives/loco-contacts/2007-August/001506.html">security breach</a>. I encourage you to review these <a href="http://www.wiggy.net/debian/developer-securing/">instructions for securing your system</a> after the Ubuntu LoCo team hosts have been attacked.</p>
<a class="google_buzz"  
href="http://www.google.com/reader/link?url=http://www.forwardyouth.com/ubuntu/security-alert-loco-teams-hosting-servers-compromised/&title=Security+Alert+&#8211;+LoCo+Teams+Hosting+Servers+Compromised&srcURL=http://www.forwardyouth.com/ubuntu" target="_blank" rel="nofollow"><img
src="http://www.forwardyouth.com/ubuntu/wp-content/plugins/google-buzz-button-for-wordpress/images/google-buzz.png" alt="Google Buzz" /></a>]]></content:encoded>
			<wfw:commentRss>http://www.forwardyouth.com/ubuntu/security-alert-loco-teams-hosting-servers-compromised/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
