Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index f0465a445f25a51031add9819acf435f711fc6b0..01e425ad658a75887f1ba6007832f017b264f25e 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,49 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
+               <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
+                <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
+               <description>&lt;p&gt;At my nearby maker space,
+&lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
+was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
+on Windows and MacOS X than Linux, because the software involved had
+to be manually compiled and set up on Linux while premade packages
+worked out of the box on Windows and MacOS X.  I found this annoying,
+as the software involved,
+&lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
+and should be trivial to get up and running on Linux if someone took
+the time to package it for the relevant distributions.  I even found
+&lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
+Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
+never resulted in the software showing up in Debian.  So a few days
+ago I offered my help to try to improve the situation.&lt;/p&gt;
+
+&lt;p&gt;Now I am very happy to see that all the packages required by a
+working Cura in Debian are uploaded into Debian and waiting in the NEW
+queue for the ftpmasters to have a look.  You can track the progress
+on
+&lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
+status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
+now to get slots in &lt;a href=&quot;ftp-master.debian.org/new.html&quot;&gt;the NEW
+queue&lt;/a&gt; while we work up updating the packages to the latest
+upstream version.&lt;/p&gt;
+
+&lt;p&gt;On a related note, two competitors for Cura, which I found harder
+to use and was unable to configure correctly for Ultimaker 2+ in the
+short time I spent on it, are already in Debian.  If you are looking
+for 3D printer &quot;slicers&quot; and want something already available in
+Debian, check out
+&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
+&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
+The latter is a fork of the former.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Mangler du en skrue, eller har du en skrue løs?</title>
                <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</link>
        <item>
                <title>Mangler du en skrue, eller har du en skrue løs?</title>
                <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</link>


@@ -500,99 +543,5 @@ mailing list).&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
-               <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
-                <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;em&gt;This is a copy of
-&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
-email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
-there if you would like to discuss this topic.  The background is that
-we are making a free software archive system based on the Norwegian
-&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
-5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
-
-&lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
-stored in Noark 5.
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
-timestamps&lt;/a&gt; can be used to verify that some information
-(document/file/checksum/metadata) have not been changed since a
-specific time in the past.  This is useful to verify the integrity of
-the documents in the archive.&lt;/p&gt;
-
-&lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
-stored as dokument variants (ie dokumentobjekt referered to from
-dokumentbeskrivelse) with the filename set to the hash it is
-stamping?&lt;/p&gt;
-
-&lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
-a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
-same attributes as the stamped dokumentobjekt except these
-attributes:&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;format -&gt; &quot;RFC3161&quot;
-&lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
-&lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
-&lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
-
-&lt;/ul&gt;
-
-&lt;p&gt;This assume a service following
-&lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
-used, which specifiy the given MIME type for replies and the .tsr file
-ending for the content of such trusted timestamp.  As far as I can
-tell from the Noark 5 specifications, it is OK to have several
-variants/renderings of a dokument attached to a given
-dokumentbeskrivelse objekt.  It might be stretching it a bit to make
-some of these variants represent crypto-signatures useful for
-verifying the document integrity instead of representing the dokument
-itself.&lt;/p&gt;
-
-&lt;p&gt;Using the source of the service in formatDetaljer allow several
-timestamping services to be used.  This is useful to spread the risk
-of key compromise over several organisations.  It would only be a
-problem to trust the timestamps if all of the organisations are
-compromised.&lt;/p&gt;
-
-&lt;p&gt;The following oneliner on Linux can be used to generate the tsr
-file.  $input is the path to the file to checksum, and $sha256 is the
-SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
-above).&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
-  | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
-      --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;To verify the timestamp, you first need to download the public key
-of the trusted timestamp service, for example using this command:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-wget -O ca-cert.txt \
-  https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;Note, the public key should be stored alongside the timestamps in
-the archive to make sure it is also available 100 years from now.  It
-is probably a good idea to standardise how and were to store such
-public keys, to make it easier to find for those trying to verify
-documents 100 or 1000 years from now. :)&lt;/p&gt;
-
-&lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-openssl ts -verify -data $inputfile -in $sha256.tsr \
-  -CAfile ca-cert.txt -text
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
-the Noark 5 specification?&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>