<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>gpg on Silicone&#39;s web</title>
		<link>https://silicone.homelinux.org/tags/gpg/</link>
		<description>Recent content in gpg on Silicone&#39;s web</description>
		<generator>Hugo</generator>
		<language>fr</language>
		
		
		
		
			<lastBuildDate>Sun, 27 Nov 2011 23:00:30 +0100</lastBuildDate>
		
			<atom:link href="https://silicone.homelinux.org/tags/gpg/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>OpenPGP key migration</title>
				<link>https://silicone.homelinux.org/2010/07/19/openpgp-key-migration/</link>
				<pubDate>Mon, 19 Jul 2010 01:53:40 +0100</pubDate>
				<guid>https://silicone.homelinux.org/2010/07/19/openpgp-key-migration/</guid>
				<description>&lt;p&gt;I’ve generated a new OpenPGP key, and I’m now using this new key.&lt;/p&gt;&#xA;&lt;p&gt;See &lt;a href=&#34;http://silicone.homelinux.org/repository/migration.asc&#34;&gt;my migration message&lt;/a&gt; for details.&lt;/p&gt;&#xA;&lt;p&gt;Anyway if you are using my repository and get the following error:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;W: GPG error: &lt;a href=&#34;http://silicone.homelinux.org&#34;&gt;http://silicone.homelinux.org&lt;/a&gt; unstable Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 8B306538D00E52B6&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;All you have to do is to get the new key and import it to apt again.&lt;br&gt;&#xA;The key is stored as before in &lt;a href=&#34;http://silicone.homelinux.org/repository/siliconerepositorykey.asc&#34;&gt;siliconerepositorykey.asc&lt;/a&gt; and you can import it with:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;sudo apt-key add siliconerepositorykey.asc&#xA;&lt;/code&gt;&lt;/pre&gt;</description>
			</item>
			<item>
				<title>Signed Personal Debian Repository</title>
				<link>https://silicone.homelinux.org/2009/02/27/signed-personal-debian-repository/</link>
				<pubDate>Fri, 27 Feb 2009 08:36:48 +0100</pubDate>
				<guid>https://silicone.homelinux.org/2009/02/27/signed-personal-debian-repository/</guid>
				<description>&lt;p&gt;Hi all,&lt;/p&gt;&#xA;&lt;p&gt;That was long, but &lt;a href=&#34;http://silicone.homelinux.org/repository/&#34; title=&#34;debian repository&#34;&gt;here&lt;/a&gt; is my signed debian repository !&lt;/p&gt;&#xA;&lt;p&gt;Investigations:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.isotton.com/software/debian/docs/repository-howto/&#34; title=&#34;Debian Repository HOWTO&#34;&gt;Debian Repository HOWTO&lt;/a&gt; mostly describes trivial repository setup.&lt;br&gt;&#xA;After some trial it appeared to me that trivial repositories cannot be signed (well at least will not be verified by atp)&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://packages.qa.debian.org/m/mini-dinstall.html&#34;&gt;mini-dinstall&lt;/a&gt; does basically only trivial repository to.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;This article about &lt;a href=&#34;http://dthconnex.com/debian_repository.htm&#34; title=&#34;Unofficial Debian repository &#34;&gt;Unofficial Debian repository&lt;/a&gt; describe a setup with &lt;a href=&#34;http://packages.debian.org/sid/debarchiver&#34;&gt;debarchiver&lt;/a&gt; however this has special user, cronjob… it seamed quite complex to me&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Basically what I wanted was like a trivial repository but secured, and the solution was on the &lt;a href=&#34;http://wiki.debian.org/HowToSetupADebianRepository&#34; title=&#34;HowToSetupADebianRepository&#34;&gt;debian wiki&lt;/a&gt;, it first confirm that trivial repository are not compatible with apt-secure. And it give the solution:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Even with an “official archive”, you can create a much simpler archive than the real official one. This is explained in &lt;a href=&#34;http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_small_public_package_archive&#34;&gt;Debian Reference (lenny)&lt;/a&gt; using apt-ftparchive in apt-utils and dupload. All uploaded packages are located in a directory and no database server is needed. This may be good enough for people hosting a few packages.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Well this was good enough for me, also I’m currently not using dupload but I put the commands suggested as postupload in a script.&lt;br&gt;&#xA;The update script, apt-ftparchive configuration and pgp public keys are on the root of the &lt;a href=&#34;http://silicone.homelinux.org/repository/&#34; title=&#34;debian repository&#34;&gt;repository&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;to use it:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;#add in source.list&#xA;deb http://silicone.homelinux.org/repository/ unstable main&#xA;deb-src http://silicone.homelinux.org/repository/ unstable main&#xA;&#xA;#for gpg signature verification get siliconerepositorykey.asc&#xA;# sudo apt-key add siliconerepositorykey.asc&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The actual content of the repository is currently just one program: a hacked xrootconsole with ANSI color support, but this will be the subject of a next post 😉&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
