<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: New signing key in openSUSE:11.3:Contrib</title>
	<atom:link href="http://news.opensuse.org/2010/11/24/new-signing-key-in-opensuse-11-3-contrib/feed/" rel="self" type="application/rss+xml" />
	<link>http://news.opensuse.org/2010/11/24/new-signing-key-in-opensuse-11-3-contrib/</link>
	<description>The latest news from the openSUSE project</description>
	<lastBuildDate>Sat, 18 May 2013 23:31:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Lars Müller</title>
		<link>http://news.opensuse.org/2010/11/24/new-signing-key-in-opensuse-11-3-contrib/comment-page-1/#comment-20668</link>
		<dc:creator>Lars Müller</dc:creator>
		<pubDate>Sun, 28 Nov 2010 15:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=5575#comment-20668</guid>
		<description><![CDATA[Which other repositories do you have in mind?

Only contrib or even more?

In your position I would file a new feature request at https://features.opensuse.org/]]></description>
		<content:encoded><![CDATA[<p>Which other repositories do you have in mind?</p>
<p>Only contrib or even more?</p>
<p>In your position I would file a new feature request at <a href="https://features.opensuse.org/" rel="nofollow">https://features.opensuse.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Ellenberger</title>
		<link>http://news.opensuse.org/2010/11/24/new-signing-key-in-opensuse-11-3-contrib/comment-page-1/#comment-20534</link>
		<dc:creator>Frank Ellenberger</dc:creator>
		<pubDate>Fri, 26 Nov 2010 19:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=5575#comment-20534</guid>
		<description><![CDATA[It would be nice, to have the keys at least on some key servers like keys.gnupg.net. Always searching opensuse.org is annoying.]]></description>
		<content:encoded><![CDATA[<p>It would be nice, to have the keys at least on some key servers like keys.gnupg.net. Always searching opensuse.org is annoying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pistazienfresser</title>
		<link>http://news.opensuse.org/2010/11/24/new-signing-key-in-opensuse-11-3-contrib/comment-page-1/#comment-20516</link>
		<dc:creator>pistazienfresser</dc:creator>
		<pubDate>Fri, 26 Nov 2010 12:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=5575#comment-20516</guid>
		<description><![CDATA[Thanks a lot for the information.

By the way:
Would it be possible to have a package in the oss (main) repository that installs all signing keys for the other repositories of the community (including non-oss and other non-main repositories connected with openSUSE)?
I guess it would be advantageous if not to many signing keys were presented to a normal/not very ambitious user. In my opinion the current status may inheritance the danger of spoiling the user. I doubt that all users are really checking the integrity/validity of every signing key if they add a new repository.

Regards pistazienfresser]]></description>
		<content:encoded><![CDATA[<p>Thanks a lot for the information.</p>
<p>By the way:<br />
Would it be possible to have a package in the oss (main) repository that installs all signing keys for the other repositories of the community (including non-oss and other non-main repositories connected with openSUSE)?<br />
I guess it would be advantageous if not to many signing keys were presented to a normal/not very ambitious user. In my opinion the current status may inheritance the danger of spoiling the user. I doubt that all users are really checking the integrity/validity of every signing key if they add a new repository.</p>
<p>Regards pistazienfresser</p>
]]></content:encoded>
	</item>
</channel>
</rss>
