blog/archive/2018/10/10.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from October 2018</title>
   5                 <description>Entries from October 2018</description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Web browser integration of VLC with Bittorrent support</title>
  11                 <link>http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</guid>
  13                 <pubDate>Sun, 21 Oct 2018 09:50:00 +0200</pubDate>
  14                 <description>&lt;p&gt;Bittorrent is as far as I know, currently the most efficient way to
  15 distribute content on the Internet.  It is used all by all sorts of
  16 content providers, from national TV stations like
  17 &lt;a href=&quot;https://www.nrk.no/&quot;&gt;NRK&lt;/a&gt;, Linux distributors like
  18 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; and
  19 &lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, and of course the
  20 &lt;a href=&quot;https://archive.org/&quot;&gt;Internet archive&lt;/A&gt;.
  21
  22 &lt;p&gt;Almost a month ago
  23 &lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;a new
  24 package adding Bittorrent support to VLC&lt;/a&gt; became available in
  25 Debian testing and unstable.  To test it, simply install it like
  26 this:&lt;/p&gt;
  27
  28 &lt;p&gt;&lt;pre&gt;
  29 apt install vlc-plugin-bittorrent
  30 &lt;/pre&gt;&lt;/p&gt;
  31
  32 &lt;p&gt;Since the plugin was made available for the first time in Debian,
  33 several improvements have been made to it.  In version 2.2-4, now
  34 available in both testing and unstable, a desktop file is provided to
  35 teach browsers to start VLC when the user click on torrent files or
  36 magnet links.  The last part is thanks to me finally understanding
  37 what the strange x-scheme-handler style MIME types in desktop files
  38 are used for.  By adding x-scheme-handler/magnet to the MimeType entry
  39 in the desktop file, at least the browsers Firefox and Chromium will
  40 suggest to start VLC when selecting a magnet URI on a web page.  The
  41 end result is that now, with the plugin installed in Buster and Sid,
  42 one can visit any
  43 &lt;a href=&quot;https://archive.org/details/CopyingIsNotTheft1080p&quot;&gt;Internet
  44 Archive page with movies&lt;/a&gt; using a web browser and click on the
  45 torrent link to start streaming the movie.&lt;/p&gt;
  46
  47 &lt;p&gt;Note, there is still some misfeatures in the plugin.  One is the
  48 fact that it will hang and
  49 &lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/13&quot;&gt;block VLC
  50 from exiting until the torrent streaming starts&lt;/a&gt;.  Another is the
  51 fact that it
  52 &lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/9&quot;&gt;will pick
  53 and play a random file in a multi file torrent&lt;/a&gt;.  This is not
  54 always the video file you want.  Combined with the first it can be a
  55 bit hard to get the video streaming going.  But when it work, it seem
  56 to do a good job.&lt;/p&gt;
  57
  58 &lt;p&gt;For the Debian packaging, I would love to find a good way to test
  59 if the plugin work with VLC using autopkgtest.  I tried, but do not
  60 know enough of the inner workings of VLC to get it working.  For now
  61 the autopkgtest script is only checking if the .so file was
  62 successfully loaded by VLC.  If you have any suggestions, please
  63 submit a patch to the Debian bug tracking system.&lt;/p&gt;
  64
  65 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  66 activities, please send Bitcoin donations to my address
  67 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  68 </description>
  69         </item>
  70
  71         <item>
  72                 <title>Release 0.2 of free software archive system Nikita announced</title>
  73                 <link>http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</link>
  74                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</guid>
  75                 <pubDate>Thu, 18 Oct 2018 14:40:00 +0200</pubDate>
  76                 <description>&lt;p&gt;This morning, the new release of the
  77 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
  78 Noark 5 core project&lt;/a&gt; was
  79 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html&quot;&gt;announced
  80 on the project mailing list&lt;/a&gt;.  The free software solution is an
  81 implementation of the Norwegian archive standard Noark 5 used by
  82 government offices in Norway.  These were the changes in version 0.2
  83 since version 0.1.1 (from NEWS.md):
  84
  85 &lt;ul&gt;
  86   &lt;li&gt;Fix typos in REL names&lt;/li&gt;
  87   &lt;li&gt;Tidy up error message reporting&lt;/li&gt;
  88   &lt;li&gt;Fix issue where we used Integer.valueOf(), not Integer.getInteger()&lt;/li&gt;
  89   &lt;li&gt;Change some String handling to StringBuffer&lt;/li&gt;
  90   &lt;li&gt;Fix error reporting&lt;/li&gt;
  91   &lt;li&gt;Code tidy-up&lt;/li&gt;
  92   &lt;li&gt;Fix issue using static non-synchronized SimpleDateFormat to avoid
  93       race conditions&lt;/li&gt;
  94   &lt;li&gt;Fix problem where deserialisers were treating integers as strings&lt;/li&gt;
  95   &lt;li&gt;Update methods to make them null-safe&lt;/li&gt;
  96   &lt;li&gt;Fix many issues reported by coverity&lt;/li&gt;
  97   &lt;li&gt;Improve equals(), compareTo() and hash() in domain model&lt;/li&gt;
  98   &lt;li&gt;Improvements to the domain model for metadata classes&lt;/li&gt;
  99   &lt;li&gt;Fix CORS issues when downloading document&lt;/li&gt;
 100   &lt;li&gt;Implementation of case-handling with registryEntry and document upload&lt;/li&gt;
 101   &lt;li&gt;Better support in Javascript for OPTIONS&lt;/li&gt;
 102   &lt;li&gt;Adding concept description of mail integration&lt;/li&gt;
 103   &lt;li&gt;Improve setting of default values for GET on ny-journalpost&lt;/li&gt;
 104   &lt;li&gt;Better handling of required values during deserialisation &lt;/li&gt;
 105   &lt;li&gt;Changed tilknyttetDato (M620) from date to dateTime&lt;/li&gt;
 106   &lt;li&gt;Corrected some opprettetDato (M600) (de)serialisation errors.&lt;/li&gt;
 107   &lt;li&gt;Improve parse error reporting.&lt;/li&gt;
 108   &lt;li&gt;Started on OData search and filtering.&lt;/li&gt;
 109   &lt;li&gt;Added Contributor Covenant Code of Conduct to project.&lt;/li&gt;
 110   &lt;li&gt;Moved repository and project from Github to Gitlab.&lt;/li&gt;
 111   &lt;li&gt;Restructured repository, moved code into src/ and web/.&lt;/li&gt;
 112   &lt;li&gt;Updated code to use Spring Boot version 2.&lt;/li&gt;
 113   &lt;li&gt;Added support for OAuth2 authentication.&lt;/li&gt;
 114   &lt;li&gt;Fixed several bugs discovered by Coverity.&lt;/li&gt;
 115   &lt;li&gt;Corrected handling of date/datetime fields.&lt;/li&gt;
 116   &lt;li&gt;Improved error reporting when rejecting during deserializatoin.&lt;/li&gt;
 117   &lt;li&gt;Adjusted default values provided for ny-arkivdel, ny-mappe,
 118    ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.&lt;/li&gt;
 119   &lt;li&gt;Several fixes for korrespondansepart*.&lt;/li&gt;
 120   &lt;li&gt;Updated web GUI:
 121      &lt;ul&gt;
 122        &lt;li&gt;Now handle both file upload and download.&lt;/li&gt;
 123        &lt;li&gt;Uses new OAuth2 authentication for login.&lt;/li&gt;
 124        &lt;li&gt;Forms now fetches default values from API using GET.&lt;/li&gt;
 125        &lt;li&gt;Added RFC 822 (email), TIFF and JPEG to list of possible file formats.&lt;/li&gt;
 126      &lt;/ul&gt;&lt;/li&gt;
 127 &lt;/ul&gt;
 128
 129 &lt;p&gt;The changes and improvements are extensive.  Running diffstat on
 130 the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
 131 108666 insertions(+), 54066 deletions(-).&lt;/p&gt;
 132
 133 &lt;p&gt;If free and open standardized archiving API sound interesting to
 134 you, please contact us on IRC
 135 (&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
 136 irc.freenode.net&lt;/a&gt;) or email
 137 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
 138 mailing list&lt;/a&gt;).&lt;/p&gt;
 139
 140 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 141 activities, please send Bitcoin donations to my address
 142 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 143 </description>
 144         </item>
 145
 146         <item>
 147                 <title>Fetching trusted timestamps using the rfc3161ng python module</title>
 148                 <link>http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</link>
 149                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</guid>
 150                 <pubDate>Mon, 8 Oct 2018 12:30:00 +0200</pubDate>
 151                 <description>&lt;p&gt;I have  earlier covered the basics of trusted timestamping using the
 152 &#39;openssl ts&#39; client.  See blog post for
 153 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;2014&lt;/a&gt;,
 154 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html&quot;&gt;2016&lt;/a&gt;
 155 and
 156 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html&quot;&gt;2017&lt;/a&gt;
 157 for those stories.  But some times I want to integrate the timestamping
 158 in other code, and recently I needed to integrate it into Python.
 159 After searching a bit, I found
 160 &lt;a href=&quot;https://dev.entrouvert.org/projects/python-rfc3161&quot;&gt;the
 161 rfc3161 library&lt;/a&gt; which seemed like a good fit, but I soon
 162 discovered it only worked for python version 2, and I needed something
 163 that work with python version 3.  Luckily I next came across
 164 &lt;a href=&quot;https://github.com/trbs/rfc3161ng/&quot;&gt;the rfc3161ng library&lt;/a&gt;,
 165 a fork of the original rfc3161 library.  Not only is it working with
 166 python 3, it have fixed a few of the bugs in the original library, and
 167 it has an active maintainer.  I decided to wrap it up and make it
 168 &lt;a href=&quot;https://tracker.debian.org/pkg/python-rfc3161ng&quot;&gt;available in
 169 Debian&lt;/a&gt;, and a few days ago it entered Debian unstable and testing.&lt;/p&gt;
 170
 171 &lt;p&gt;Using the library is fairly straight forward.  The only slightly
 172 problematic step is to fetch the required certificates to verify the
 173 timestamp.  For some services it is straight forward, while for others
 174 I have not yet figured out how to do it.  Here is a small standalone
 175 code example based on of the integration tests in the library code:&lt;/p&gt;
 176
 177 &lt;pre&gt;
 178 #!/usr/bin/python3
 179
 180 &quot;&quot;&quot;
 181
 182 Python 3 script demonstrating how to use the rfc3161ng module to
 183 get trusted timestamps.
 184
 185 The license of this code is the same as the license of the rfc3161ng
 186 library, ie MIT/BSD.
 187
 188 &quot;&quot;&quot;
 189
 190 import os
 191 import pyasn1.codec.der
 192 import rfc3161ng
 193 import subprocess
 194 import tempfile
 195 import urllib.request
 196
 197 def store(f, data):
 198     f.write(data)
 199     f.flush()
 200     f.seek(0)
 201
 202 def fetch(url, f=None):
 203     response = urllib.request.urlopen(url)
 204     data = response.read()
 205     if f:
 206         store(f, data)
 207     return data
 208
 209 def main():
 210     with tempfile.NamedTemporaryFile() as cert_f,\
 211          tempfile.NamedTemporaryFile() as ca_f,\
 212          tempfile.NamedTemporaryFile() as msg_f,\
 213          tempfile.NamedTemporaryFile() as tsr_f:
 214
 215         # First fetch certificates used by service
 216         certificate_data = fetch(&#39;https://freetsa.org/files/tsa.crt&#39;, cert_f)
 217         ca_data_data = fetch(&#39;https://freetsa.org/files/cacert.pem&#39;, ca_f)
 218
 219         # Then timestamp the message
 220         timestamper = \
 221             rfc3161ng.RemoteTimestamper(&#39;http://freetsa.org/tsr&#39;,
 222                                         certificate=certificate_data)
 223         data = b&quot;Python forever!\n&quot;
 224         tsr = timestamper(data=data, return_tsr=True)
 225
 226         # Finally, convert message and response to something &#39;openssl ts&#39; can verify
 227         store(msg_f, data)
 228         store(tsr_f, pyasn1.codec.der.encoder.encode(tsr))
 229         args = [&quot;openssl&quot;, &quot;ts&quot;, &quot;-verify&quot;,
 230                 &quot;-data&quot;, msg_f.name,
 231                 &quot;-in&quot;, tsr_f.name,
 232                 &quot;-CAfile&quot;, ca_f.name,
 233                 &quot;-untrusted&quot;, cert_f.name]
 234         subprocess.check_call(args)
 235
 236 if &#39;__main__&#39; == __name__:
 237    main()
 238 &lt;/pre&gt;
 239
 240 &lt;p&gt;The code fetches the required certificates, store them as temporary
 241 files, timestamp a simple message, store the message and timestamp to
 242 disk and ask &#39;openssl ts&#39; to verify the timestamp.  A timestamp is
 243 around 1.5 kiB in size, and should be fairly easy to store for future
 244 use.&lt;/p&gt;
 245
 246 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 247 activities, please send Bitcoin donations to my address
 248 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 249 </description>
 250         </item>
 251
 252         <item>
 253                 <title>Automatic Google Drive sync using grive in Debian</title>
 254                 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
 255                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
 256                 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
 257                 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian.  To try to
 258 rescue the remains, I helped set up automatic sync with Google Drive.
 259 I did not find any sensible Debian package handling this
 260 automatically, so I rebuild the grive2 source from
 261 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
 262 task and added a autostart desktop entry and a small shell script to
 263 run in the background while the user is logged in to do the sync.
 264 Here is a sketch of the setup for future reference.&lt;/p&gt;
 265
 266 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
 267 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user.  Next, I
 268 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
 269 to start the sync when the user log in:&lt;/p&gt;
 270
 271 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 272 [Desktop Entry]
 273 Name=Google drive autosync
 274 Type=Application
 275 Exec=/home/user/bin/grive-sync
 276 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 277
 278 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
 279 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
 280
 281 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 282 #!/bin/sh
 283 set -e
 284 cd ~/
 285 cleanup() {
 286     if [ &quot;$syncpid&quot; ] ; then
 287         kill $syncpid
 288     fi
 289 }
 290 trap cleanup EXIT INT QUIT
 291 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
 292 syncpdi=$!
 293 while true; do
 294     if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
 295         echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
 296         exit 1
 297     fi
 298     if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
 299         /usr/lib/grive/grive-sync.sh sync googledrive
 300     fi
 301     sleep 300
 302 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
 303 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 304
 305 &lt;p&gt;Feel free to use the setup if you want.  It can be assumed to be
 306 GNU GPL v2 licensed (or any later version, at your leisure), but I
 307 doubt this code is possible to claim copyright on.&lt;/p&gt;
 308
 309 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 310 activities, please send Bitcoin donations to my address
 311 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 312 </description>
 313         </item>
 314
 315         </channel>
 316 </rss>