blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="https://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="https://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html">RAID status from LSI Megaraid controllers in Debian</a></div>
  24       <div class="date">17th April 2024</div>
  25       <div class="body"><p>I am happy to report that
  26 <ahref="https://github.com/namiltd/megactl">the megactl package</a>,
  27 useful to fetch RAID status when using the LSI Megaraid controller,
  28 now is available in Debian.  It passed NEW a few days ago, and is now
  29 <ahref="https://tracker.debian.org/pkg/megactl">available in
  30 unstable</a>, and probably showing up in testing in a weeks time.  The
  31 new version should provide Appstream hardware mapping and should
  32 integrate nicely with isenkram.</p>
  33
  34 <p>As usual, if you use Bitcoin and want to show your support of my
  35 activities, please send Bitcoin donations to my address
  36 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  37
  38 </div>
  39       <div class="tags">
  40
  41
  42         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
  43
  44
  45       </div>
  46     </div>
  47     <div class="padding"></div>
  48
  49     <div class="entry">
  50       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html">Time to move orphaned Debian packages to git</a></div>
  51       <div class="date">14th April 2024</div>
  52       <div class="body"><p>There are several packages in Debian without a associated git
  53 repository with the packaging history.  This is unfortunate and it
  54 would be nice if more of these would do so.  Quote a lot of these are
  55 without a maintainer, ie listed as maintained by the
  56 '<a href="https://qa.debian.org/developer.php?email=packages%40qa.debian.org">Debian
  57 QA Group</a>' place holder.  In fact, 438 packages have this property
  58 according to UDD (<tt>SELECT source FROM sources WHERE release = 'sid'
  59 AND (vcs_url ilike '%anonscm.debian.org%' OR vcs_browser ilike
  60 '%anonscm.debian.org%' or vcs_url IS NULL OR vcs_browser IS NULL) AND
  61 maintainer ilike '%packages@qa.debian.org%';</tt>).  Such packages can
  62 be updated without much coordination by any Debian developer, as they
  63 are considered orphaned.</p>
  64
  65 <p>To try to improve the situation and reduce the number of packages
  66 without associated git repository, I started a few days ago to search
  67 out candiates and provide them with a git repository under the
  68 'debian' collaborative Salsa project.  I started with the packages
  69 pointing to obsolete Alioth git repositories, and am now working my
  70 way across the ones completely without git references.  In addition to
  71 updating the Vcs-* debian/control fields, I try to update
  72 Standards-Version, debhelper compat level, simplify d/rules, switch to
  73 Rules-Requires-Root: no and fix lintian issues reported.  I only
  74 implement those that are trivial to fix, to avoid spending too much
  75 time on each orphaned package.  So far my experience is that it take
  76 aproximately 20 minutes to convert a package without any git
  77 references, and a lot more for packages with existing git repositories
  78 incompatible with git-buildpackages.</p>
  79
  80 <p>So far I have converted 10 packages, and I will keep going until I
  81 run out of steam.  As should be clear from the numbers, there is
  82 enough packages remaining for more people to do the same without
  83 stepping on each others toes.  I find it useful to start by searching
  84 for a git repo already on salsa, as I find that some times a git repo
  85 has already been created, but no new version is uploaded to Debian
  86 yet.  In those cases I start with the existing git repository.  I
  87 convert to the git-buildpackage+pristine-tar workflow, and ensure a
  88 debian/gbp.conf file with "pristine-tar=True" is added early, to avoid
  89 uploading a orig.tar.gz with the wrong checksum by mistake.  Did that
  90 three times in the begin before I remembered my mistake.</p>
  91
  92 <p>So, if you are a Debian Developer and got some spare time, perhaps
  93 considering migrating some orphaned packages to git?</p>
  94
  95 <p>As usual, if you use Bitcoin and want to show your support of my
  96 activities, please send Bitcoin donations to my address
  97 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  98 </div>
  99       <div class="tags">
 100
 101
 102         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 103
 104
 105       </div>
 106     </div>
 107     <div class="padding"></div>
 108
 109     <div class="entry">
 110       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html">Plain text accounting file from your bitcoin transactions</a></div>
 111       <div class="date"> 7th March 2024</div>
 112       <div class="body"><p>A while back I wrote a small script to extract the Bitcoin
 113 transactions in a wallet in the
 114 <ahref="https://plaintextaccounting.org/">ledger plain text accounting
 115 format</a>.  The last few days I spent some time to get it working
 116 better with more special cases.  In case it can be useful for others,
 117 here is a copy:</p>
 118
 119 <p><blockquote><pre>
 120 #!/usr/bin/python3
 121 #  -*- coding: utf-8 -*-
 122 #  Copyright (c) 2023-2024 Petter Reinholdtsen
 123
 124 from decimal import Decimal
 125 import json
 126 import subprocess
 127 import time
 128
 129 import numpy
 130
 131 def format_float(num):
 132     return numpy.format_float_positional(num, trim='-')
 133
 134 accounts = {
 135     u'amount' : 'Assets:BTC:main',
 136 }
 137
 138 addresses = {
 139     '<some address>' : 'Assets:bankkonto',
 140     '<some address>' : 'Assets:bankkonto',
 141 }
 142
 143 def exec_json(cmd):
 144     proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
 145     j = json.loads(proc.communicate()[0], parse_float=Decimal)
 146     return j
 147
 148 def list_txs():
 149     # get all transactions for all accounts / addresses
 150     c = 0
 151     txs = []
 152     txidfee = {}
 153     limit=100000
 154     cmd = ['bitcoin-cli', 'listtransactions', '*', str(limit)]
 155     if True:
 156         txs.extend(exec_json(cmd))
 157     else:
 158         # Useful for debugging
 159         with open('transactions.json') as f:
 160             txs.extend(json.load(f, parse_float=Decimal))
 161     #print txs
 162     for tx in sorted(txs, key=lambda a: a['time']):
 163 #        print tx['category']
 164         if 'abandoned' in tx and tx['abandoned']:
 165             continue
 166         if 'confirmations' in tx and 0 >= tx['confirmations']:
 167             continue
 168         when = time.strftime('%Y-%m-%d %H:%M', time.localtime(tx['time']))
 169         if 'message' in tx:
 170             desc = tx['message']
 171         elif 'comment' in tx:
 172             desc = tx['comment']
 173         elif 'label' in tx:
 174             desc = tx['label']
 175         else:
 176             desc = 'n/a'
 177         print("%s %s" % (when, desc))
 178         if 'address' in tx:
 179             print("  ; to bitcoin address %s" % tx['address'])
 180         else:
 181             print("  ; missing address in transaction, txid=%s" % tx['txid'])
 182         print(f"  ; amount={tx['amount']}")
 183         if 'fee'in tx:
 184             print(f"  ; fee={tx['fee']}")
 185         for f in accounts.keys():
 186             if f in tx and Decimal(0) != tx[f]:
 187                 amount = tx[f]
 188                 print("  %-20s   %s BTC" % (accounts[f], format_float(amount)))
 189         if 'fee' in tx and Decimal(0) != tx['fee']:
 190             # Make sure to list fee used in several transactions only once.
 191             if 'fee' in tx and tx['txid'] in txidfee \
 192                and tx['fee'] == txidfee[tx['txid']]:
 193                 True
 194             else:
 195                 fee = tx['fee']
 196                 print("  %-20s   %s BTC" % (accounts['amount'], format_float(fee)))
 197                 print("  %-20s   %s BTC" % ('Expences:BTC-fee', format_float(-fee)))
 198                 txidfee[tx['txid']] = tx['fee']
 199
 200         if 'address' in tx and tx['address'] in addresses:
 201             print("  %s" % addresses[tx['address']])
 202         else:
 203             if 'generate' == tx['category']:
 204                 print("  Income:BTC-mining")
 205             else:
 206                 if amount < Decimal(0):
 207                     print(f"  Assets:unknown:sent:update-script-addr-{tx['address']}")
 208                 else:
 209                     print(f"  Assets:unknown:received:update-script-addr-{tx['address']}")
 210
 211         print()
 212         c = c + 1
 213     print("# Found %d transactions" % c)
 214     if limit == c:
 215         print(f"# Warning: Limit {limit} reached, consider increasing limit.")
 216
 217 def main():
 218     list_txs()
 219
 220 main()
 221 </pre></blockquote></p>
 222
 223 <p>It is more of a proof of concept, and I do not expect it to handle
 224 all edge cases, but it worked for me, and perhaps you can find it
 225 useful too.</p>
 226
 227 <p>To get a more interesting result, it is useful to map accounts sent
 228 to or received from to accounting accounts, using the
 229 <tt>addresses</tt> hash.  As these will be very context dependent, I
 230 leave out my list to allow each user to fill out their own list of
 231 accounts.  Out of the box, 'ledger reg BTC:main' should be able to
 232 show the amount of BTCs present in the wallet at any given time in the
 233 past.  For other and more valuable analysis, a account plan need to be
 234 set up in the <tt>addresses</tt> hash.  Here is an example
 235 transaction:</p>
 236
 237 <p><blockquote><pre>
 238 2024-03-07 17:00 Donated to good cause
 239     Assets:BTC:main                           -0.1 BTC
 240     Assets:BTC:main                       -0.00001 BTC
 241     Expences:BTC-fee                       0.00001 BTC
 242     Expences:donations                         0.1 BTC
 243 </pre></blockquote></p>
 244
 245 <p>It need a running Bitcoin Core daemon running, as it connect to it
 246 using <tt>bitcoin-cli listtransactions * 100000</tt> to extract the
 247 transactions listed in the Wallet.</p>
 248
 249 <p>As usual, if you use Bitcoin and want to show your support of my
 250 activities, please send Bitcoin donations to my address
 251 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 252 </div>
 253       <div class="tags">
 254
 255
 256         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 257
 258
 259       </div>
 260     </div>
 261     <div class="padding"></div>
 262
 263     <div class="entry">
 264       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html">RAID status from LSI Megaraid controllers using free software</a></div>
 265       <div class="date"> 3rd March 2024</div>
 266       <div class="body"><p>The last few days I have revisited RAID setup using the LSI
 267 Megaraid controller.  These are a family of controllers called PERC by
 268 Dell, and is present in several old PowerEdge servers, and I recently
 269 got my hands on one of these.  I had forgotten how to handle this RAID
 270 controller in Debian, so I had to take a peek in the
 271 <a href="https://wiki.debian.org/LinuxRaidForAdmins">Debian wiki page
 272 "Linux and Hardware RAID: an administrator's summary"</a> to remember
 273 what kind of software is available to configure and monitor the disks
 274 and controller.  I prefer Free Software alternatives to proprietary
 275 tools, as the later tend to fall into disarray once the manufacturer
 276 loose interest, and often do not work with newer Linux Distributions.
 277 Sadly there is no free software tool to configure the RAID setup, only
 278 to monitor it. RAID can provide improved reliability and resilience in
 279 a storage solution, but only if it is being regularly checked and any
 280 broken disks are being replaced in time.  I thus want to ensure some
 281 automatic monitoring is available.</p>
 282
 283 <p>In the discovery process, I came across a old free software tool to
 284 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
 285 surprise is not present in debian.  To help change that I created a
 286 <a href="https://bugs.debian.org/1065322">request for packaging of the
 287 megactl package</a>, and tried to track down a usable version.
 288 <a href="https://sourceforge.net/p/megactl/">The original project
 289 site</a> is on Sourceforge, but as far as I can tell that project has
 290 been dead for more than 15 years.  I managed to find a
 291 <a href="https://github.com/hmage/megactl">more recent fork on
 292 github</a> from user hmage, but it is unclear to me if this is still
 293 being maintained.  It has not seen much improvements since 2016.  A
 294 <a href="https://github.com/namiltd/megactl">more up to date
 295 edition</a> is a git fork from the original github fork by user
 296 namiltd, and this newer fork seem a lot more promising.  The owner of
 297 this github repository has replied to change proposals within hours,
 298 and had already added some improvements and support for more hardware.
 299 Sadly he is reluctant to commit to maintaining the tool and stated in
 300 <a href="https://github.com/namiltd/megactl/pull/1">my first pull
 301 request</A> that he think a new release should be made based on the
 302 git repository owned by hmage.  I perfectly understand this
 303 reluctance, as I feel the same about maintaining yet another package
 304 in Debian when I barely have time to take care of the ones I already
 305 maintain, but do not really have high hopes that hmage will have time
 306 to spend on it and hope namiltd will change his mind.</p>
 307
 308 <p>In any case, I created
 309 <a href="https://salsa.debian.org/debian/megactl">a draft package</a>
 310 based on the namiltd edition and put it under the debian group on
 311 salsa.debian.org.  If you own a Dell PowerEdge server with one of the
 312 PERC controllers, or any other RAID controller using the megaraid or
 313 megaraid_sas Linux kernel modules, you might want to check it out.  If
 314 enough people are interested, perhaps the package will make it into
 315 the Debian archive.</p>
 316
 317 <p>There are two tools provided, megactl for the megaraid Linux kernel
 318 module, and megasasctl for the megaraid_sas Linux kernel module. The
 319 simple output from the command on one of my machines look like this
 320 (yes, I know some of the disks have problems. :).</p>
 321
 322 <pre>
 323 # megasasctl
 324 a0       PERC H730 Mini           encl:1 ldrv:2  batt:good
 325 a0d0       558GiB RAID 1   1x2  optimal
 326 a0d1      3067GiB RAID 0   1x11 optimal
 327 a0e32s0     558GiB  a0d0  online   errs: media:0  other:19
 328 a0e32s1     279GiB  a0d1  online
 329 a0e32s2     279GiB  a0d1  online
 330 a0e32s3     279GiB  a0d1  online
 331 a0e32s4     279GiB  a0d1  online
 332 a0e32s5     279GiB  a0d1  online
 333 a0e32s6     279GiB  a0d1  online
 334 a0e32s8     558GiB  a0d0  online   errs: media:0  other:17
 335 a0e32s9     279GiB  a0d1  online
 336 a0e32s10    279GiB  a0d1  online
 337 a0e32s11    279GiB  a0d1  online
 338 a0e32s12    279GiB  a0d1  online
 339 a0e32s13    279GiB  a0d1  online
 340
 341 #
 342 </pre>
 343
 344 <p>In addition to displaying a simple status report, it can also test
 345 individual drives and print the various event logs.  Perhaps you too
 346 find it useful?</p>
 347
 348 <p>In the packaging process I provided some patches upstream to
 349 improve installation and ensure
 350 <ahref="https://github.com/namiltd/megactl/pull/2">a Appstream
 351 metainfo file is provided</a> to list all supported HW, to allow
 352 <a href="https://tracker.debian.org/isenkram">isenkram</a> to propose
 353 the package on all servers with a relevant PCI card.</p>
 354
 355 <p>As usual, if you use Bitcoin and want to show your support of my
 356 activities, please send Bitcoin donations to my address
 357 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 358
 359 </div>
 360       <div class="tags">
 361
 362
 363         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
 364
 365
 366       </div>
 367     </div>
 368     <div class="padding"></div>
 369
 370     <div class="entry">
 371       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html">Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</a></div>
 372       <div class="date">27th February 2024</div>
 373       <div class="body"><p>Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
 374 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
 375 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
 376 2024-03-12.  Seminaret finner sted ved Oslo byarkiv.  Vi håper å få
 377 til videostrømming via Internett av presentasjoner og paneldiskusjon.
 378 Oppdatert program og lenker til påmeldingsskjema er
 379 <a href="https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html">tilgjengelig
 380 fra Nikita-prosjektet</a>.  Arrangementet er gratis.
 381
 382 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 383 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 384 til min adresse
 385 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
 386 betaling med bitcoin er ikke anonymt. :)</p>
 387 </div>
 388       <div class="tags">
 389
 390
 391         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 392
 393
 394       </div>
 395     </div>
 396     <div class="padding"></div>
 397
 398     <div class="entry">
 399       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html">Welcome out of prison, Mickey, hope you find some freedom!</a></div>
 400       <div class="date"> 1st January 2024</div>
 401       <div class="body"><p align="center"><img src="https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg"/></p>
 402
 403 <p>Today, the animation figure Mickey Mouse finally was released from
 404 the corporate copyright prison, as the 1928 movie
 405 <a href="https://en.wikipedia.org/wiki/Steamboat_Willie">Steamboat
 406 Willie</a> entered the public domain in USA.  This movie was the first
 407 public appearance of Mickey Mouse.  Sadly the figure is still on
 408 probation, thanks to trademark laws and a the Disney corporations
 409 powerful pack of lawyers, as described in the 2017 article
 410 in <a href="https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/">"How
 411 Mickey Mouse Evades the Public Domain"</a> from Priceonomics.  On the
 412 positive side, the primary driver for repeated extentions of the
 413 duration of copyright has been Disney thanks to Mickey Mouse and the
 414 2028 movie, and as it now in the public domain I hope it will cause
 415 less urge to extend the already unreasonable long copyright
 416 duration.</p>
 417
 418 <p>The first book I published, the 2004 book <a
 419 href="https://free-culture.cc/">"Free Culture" by Lawrence Lessig</a>,
 420 published 2015 in
 421 <a href="https://people.skolelinux.org/pere/publisher/#frikultur">English,
 422 French and Norwegian Bokmål</a>, touch on the story of Disney pushed
 423 for extending the copyright duration in USA.  It is a great book
 424 explaining problems with the current copyright regime and why we need
 425 Creative Commons movement, and I strongly recommend everyone to read
 426 it.</p>
 427
 428 <p>This movie (with
 429 <a href="https://www.imdb.com/title/tt0019422/">IMDB ID tt0019422</a>)
 430 is now available from the Internet Archive.  Two copies have been
 431 uploaded so far, one uploaded
 432 <a href="https://archive.org/details/SteamboatWillie">2015-11-04</a>
 433 (<a href="https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent">torrent</a>)
 434 and the other
 435 <a href="https://archive.org/details/steamboat-willie-mickey">2023-01-01</a>
 436 (<a href="https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent">torrent</a>) - see
 437 <a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC
 438 bittorrent plugin</a> for streaming the video using the torrent link.
 439 I am very happy to see
 440 <a href="https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html">the
 441 number of public domain movies</a> increasing.  I look forward to
 442 when those are the majority.  Perhaps it will reduce the urge of the
 443 copyright industry to control its customers.</p>
 444
 445 <p>A more
 446 <a href="https://publicdomainreview.org/features/entering-the-public-domain/2024/">comprehensive
 447 list of works entering the public domain in 2024</a> is available from
 448 the Public Domain Review.</p>
 449
 450 <p>As usual, if you use Bitcoin and want to show your support of my
 451 activities, please send Bitcoin donations to my address
 452 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 453 </div>
 454       <div class="tags">
 455
 456
 457         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
 458
 459
 460       </div>
 461     </div>
 462     <div class="padding"></div>
 463
 464     <div class="entry">
 465       <div class="title"><a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC bittorrent plugin still going strong, new upload 2.14-4</a></div>
 466       <div class="date">31st December 2023</div>
 467       <div class="body"><p>The other day I uploaded a new version of
 468 <a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
 469 bittorrent plugin</a> to Debian, version 2.14-4, to fix a few
 470 packaging issues.  This plugin extend VLC allowing it to stream videos
 471 directly from a bittorrent source using both torrent files and magnet
 472 links, as easy as using a HTTP or local file source.  I believe such
 473 protocol support is a vital feature in VLC, allowing efficient
 474 streaming from sources such at the 11 million movies in
 475 <a href="https://archive.org/">the Internet Archive</a>.  Bittorrent is
 476 one of the most efficient content distribution protocols on the
 477 Internet, without centralised control, and should be used more.</p>
 478
 479 <p>The new version is now both in Debian Unstable and Testing, as well
 480 as Ubuntu.  While looking after the package, I decided to ask the VLC
 481 upstream community if there was any hope to get Bittorrent support
 482 into the official VLC program, and was very happy to learn that
 483 someone is already working on it.  I hope we can see some fruits of
 484 that labour next year, but do not hold my breath.  In the mean time we
 485 can use the plugin, which is already
 486 <a href="https://qa.debian.org/popcon.php?package=vlc-plugin-bittorrent">installed
 487 by 0.23 percent of the Debian population</a> according to
 488 popularity-contest.  It could use a new upstream release, and I hope
 489 the upstream developer soon find time to polish it even more.</p>
 490
 491 <p>It is worth noting that the plugin store the downloaded files in
 492 <tt>~/Downloads/vlc-bittorrent/</tt>, which can quickly fill up the
 493 user home directory during use.  Users of the plugin should keep an
 494 eye with disk usage when streaming a bittorrent source.</p>
 495
 496 <p>As usual, if you use Bitcoin and want to show your support of my
 497 activities, please send Bitcoin donations to my address
 498 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 499 </div>
 500       <div class="tags">
 501
 502
 503         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 504
 505
 506       </div>
 507     </div>
 508     <div class="padding"></div>
 509
 510     <div class="entry">
 511       <div class="title"><a href="https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html">«Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra depotet» i tidsskriftet Aksess</a></div>
 512       <div class="date">15th November 2023</div>
 513       <div class="body"><p>For noen uker siden skrev en kamerat og meg
 514 <a href="https://www.aksess-tidsskrift.no/fordypning/175530">en
 515 artikkel om tegnsett</a> i
 516 <a href="https://www.aksess-tidsskrift.no/">arkivtidsskriftet
 517 Aksess</a> både på web og i papirutgave nr. 3 2023.  Her er det som
 518 nettopp ble publisert.</p>
 519
 520 <blockquote>
 521
 522 <p><strong>Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra
 523 depotet</strong></p>
 524
 525 <p>av Thomas Sødring og Petter Reinholdtsen</p>
 526
 527 <p>De færreste av oss tenker over hva som skjer dypere i datamaskinen
 528 mens vi sitter der og skriver noe på tastaturet. Når du trykker på
 529 tasten «Å», så vises bokstaven Å. Men noen ganger blir det
 530 feil. Hvorfor det – og hva er viktig å være klar over i
 531 arkivsammenheng?</p>
 532
 533 <p>Dersom bokstaver tolkes forskjellig mellom systemer, blir det fort
 534 rot, dette kalles mojibake blant kjennere, etter det japanske
 535 uttrykket for tegnomforming. Det er en lang historie her som tidvis
 536 har vært preget av rot.  Noen husker kanskje tilbake til en tid der
 537 bokstavene æ, ø og å ofte var ødelagt i e-poster – et klassisk
 538 eksempel på tegnsettproblemstilling.</p>
 539
 540 <p id="tegnsett_access_nå_og_før"><strong>«Nå» og «før»</strong></p>
 541
 542 <p>Tid er et skjult problem for depot fordi vi danner dokumentasjon i
 543 en kontekst som er preget av å være «nå».  Vår forståelse av verden og
 544 bruken av teknologi er utgangspunktet for denne konteksten. Tenk selv
 545 hvordan verden har utviklet seg de siste 20 årene, hva samfunnet er
 546 opptatt av, og hvordan vi bruker teknologi i hverdagen. Tid er et
 547 skjult problem fordi når vi trekker dokumentasjon ut av systemer og
 548 deponerer for langtidsbevaring, er konteksten til materialet «nå», men
 549 verden går videre. Ettersom teknologien og måten vi bruker den på,
 550 utvikler seg, blir «nå» til «før», og dokumentasjonen befinner seg
 551 snart i en «før»-kontekst.</p>
 552
 553 <p>Dette med «før» og «nå» i forhold til dokumentasjonens kontekst er
 554 noe vi er veldig lite bevisste på, men det er en problemstilling
 555 depotarkivene eier og forvalter.  En av disse utfordringene er hvorfor
 556 «Ø» ikke nødvendigvis er det samme som «Ø», og hvorfor det i det hele
 557 tatt gir mening å si noe sånt. Vi snakker her om noe som heter
 558 tegnsett, som er en avtalt måte å representere bokstaver, tall og
 559 andre symboler på slik at vi på en feilfri måte kan utveksle tekst
 560 mellom datasystemer.</p>
 561
 562 <p>Tegnsettproblemstillingen er satt sammen av fire fasetter;
 563 repertoar, representasjon, koding og uttegning.</p>
 564
 565 <p id="tegnsett_access_repertoarer"><strong>Repertoarer</strong></p>
 566
 567 <p>Repertoar er en samling med tegn og symboler som kan
 568 representeres. Tenk norsk alfabet eller japanske piktogrammer, men
 569 også matematiske og elektroniske symboler. Bokstaven «stor a» kan være
 570 en oppføring i et slikt repertoar. For å kunne brukes i en datamaskin
 571 trenger hver oppføring i et slikt repertoar en representasjon, hvilket
 572 i datamaskinsammenheng betyr at det tilordnes et tall. Tallet kan
 573 lagres på ulike vis i en eller flere kodingsformater. For eksempel kan
 574 en skrive tallet ti som både 10, X og A, i henholdsvis
 575 titallssystemet, romertallssystemet og sekstentallssystemet.</p>
 576
 577 <p>Hvis en skal kunne lese inn filer og vite hvilket tall og hvilken
 578 representasjon og instans i et repertoar det er snakk om, så må en
 579 vite hvordan tallet er kodet. Sist, men ikke minst, for å kunne bruke
 580 symbolet til noe må det kunne være kjent hvordan det skal se ut eller
 581 tegnes på ark. Det finnes utallige skrifttyper med norske bokstaver,
 582 alle litt forskjellige, og skal en kunne tegne en stor A på skjermen,
 583 så må datamaskinen vite hva den skal tegne. Skrifttyper inneholder
 584 informasjon om hvordan ulike tall skal tegnes. De inneholder ikke
 585 alltid alle symbolene som er brukt i en tekst, hvilket gjør at ikke
 586 alle forståtte tegn vil kunne vises på skjerm eller ark.</p>
 587
 588 <p>Hver av disse fasettene må være avklart for å kunne ta vare på og vise
 589 frem tekst med en datamaskin. Kombinasjon av repertoar, representasjon
 590 og koding er det en kaller et tegnsett. Kombinasjonen av
 591 representasjon og uttegning kalles en skrifttype. De fleste
 592 skrifttyper har også informasjon om repertoar, men det finnes
 593 skrifttyper som kun kobler mellom tallkode og uttegning, uten å
 594 fortelle noe om hvordan tallkodene egentlig skal tolkes.</p>
 595
 596 <p id="tegnsett_access_fra_ascii_til_iso_8859"><strong>Fra ASCII til ISO-8859</strong></p>
 597
 598 <p>Vi begynner historien med ASCII (American Standard Code for
 599 Information Interchange) som har en historie som spores tilbake til
 600 1963. Utgangspunktet til ASCII var at det kunne kode opp til 128
 601 forskjellige symboler i vanlig bruk i USA. De visuelle symbolene i
 602 ASCII er de små og store bokstavene (a til z og A til Z), tall (0 til
 603 9) og tegnsettingssymboler (for eksempel semikolon, komma og
 604 punktum). ASCII har også noen usynlige symboler som ble brukt for
 605 bl.a. kommunikasjon. Før ASCII var det for eksempel teleks-tegnsett
 606 med plass til bare 32 tegn og EBCDIC med plass til 256 tegn, alle med
 607 en helt annen rekkefølge på symbolene enn ASCII, men de har vært lite
 608 brukt de siste femti årene. Et eksempel på noen utvalgte symboler i
 609 repertoaret til ASCII vises i tabell 1.</p>
 610
 611 <table align="center" width="50%">
 612
 613 <caption>Tabell 1. Eksempel på utvalgte symboler hentet fra
 614 ASCII-tegnsettet. Kolonnen «Binær» viser symbolets verdi i
 615 totallssystemet (1 og 0 tall), mens kolonnen «Desimal» viser symbolets
 616 verdi i titallssystemet.</caption>
 617
 618 <tbody>
 619 <tr>
 620 <th>Grafisk</th>
 621 <th>Binær</th>
 622 <th>Desimal</th>
 623 </tr>
 624 <tr>
 625 <td>A</td>
 626 <td>1000001</td>
 627 <td align="right">65</td>
 628 </tr>
 629 <tr>
 630 <td>M</td>
 631 <td>1001101</td>
 632 <td align="right">77</td>
 633 </tr>
 634 <tr>
 635 <td>Z</td>
 636 <td>1011010</td>
 637 <td align="right">90</td>
 638 </tr>
 639 <tr>
 640 <td>a</td>
 641 <td>1100001</td>
 642 <td align="right">97</td>
 643 </tr>
 644 <tr>
 645 <td>m</td>
 646 <td>1101101</td>
 647 <td align="right">109</td>
 648 </tr>
 649 <tr>
 650 <td>z</td>
 651 <td>1111010</td>
 652 <td align="right">122</td>
 653 </tr>
 654 <tr>
 655 <td>0</td>
 656 <td>0110000</td>
 657 <td align="right">48</td>
 658 </tr>
 659 <tr>
 660 <td>9</td>
 661 <td>0111001</td>
 662 <td align="right">58</td>
 663 </tr>
 664 <tr>
 665 <td>;</td>
 666 <td>0111011</td>
 667 <td align="right">59</td>
 668 </tr>
 669 </tbody>
 670 </table>
 671
 672 <p>Det opprinnelige ASCII-tegnsettet ble også omtalt som ASCII-7 og
 673 brukte 7 bits (0 og 1) for å representere symboler. Datamaskiner er
 674 ofte konfigurert til å jobbe med enheter der bits er gruppert som 4
 675 eller 8 bits . Det lå en mulighet i å ta i bruk bit åtte. En slik
 676 endring ville gjøre det mulig for datamaskiner å øke antall symboler
 677 de kunne representere, noe som ga en økning fra 128 forskjellige
 678 symboler til 256 forskjellige symboler. Det ble åpnet for å innlemme
 679 de nordiske bokstavene sammen med ASCII, og dette ble etter hvert
 680 standardisert som ISO-8859-1. Tabell 2 viser deler av ISO-8859-1 som
 681 støtter de norske bokstavene.</p>
 682
 683 <p>Det sier seg selv at muligheten til å representere inntil 256 symboler
 684 ikke holder når vi snakker om en global verden, og det ble gjort et
 685 standardiseringsløp som tok utgangspunkt i ASCII-7 med en utvidelse
 686 til å bruke den åttende biten for ulike språkgrupper. Denne standarden
 687 heter ISO-8859 og er inndelt i opptil 16 varianter, altså fra
 688 ISO-8859-1 til ISO-8859-16.</p>
 689
 690 <table align="center" width="50%">
 691
 692 <caption>Tabell 2. Koding av de norske symbolene slik de er definert i
 693 ISO-8859-1 tegnsettet.</caption>
 694
 695 <tbody>
 696 <tr>
 697 <th>Grafisk</th>
 698 <th>Binær</th>
 699 <th>Desimal</th>
 700 </tr>
 701 <tr>
 702 <td>Æ</td>
 703 <td>11000110</td>
 704 <td align="right">198</td>
 705 </tr>
 706 <tr>
 707 <td>Ø</td>
 708 <td>11011000</td>
 709 <td align="right">216</td>
 710 </tr>
 711 <tr>
 712 <td>Å</td>
 713 <td>11000101</td>
 714 <td align="right">197</td>
 715 </tr>
 716 <tr>
 717 <td>æ</td>
 718 <td>11100110</td>
 719 <td align="right">230</td>
 720 </tr>
 721 <tr>
 722 <td>ø</td>
 723 <td>11111000</td>
 724 <td align="right">248</td>
 725 </tr>
 726 <tr>
 727 <td>å</td>
 728 <td>11100101</td>
 729 <td align="right">229</td>
 730 </tr>
 731 </tbody>
 732 </table>
 733
 734 <p>Norske tegn er definert i ISO-8859-1, som også omtales som Latin 1, de
 735 fleste samiske tegn er definert i ISO-8859-4 (Latin 4) mens tilgang
 736 til €-symbolet kom med ISO-8859-15 (Latin 9). ISO-8859-15 er en
 737 revisjon av ISO-8859-1 som fjerner noen lite brukte symboler og
 738 erstatter bokstaver som er mer brukt, og introduserer €-symbolet.  Det
 739 er viktig å merke at alle ISO-8859-variantene har overlapp med
 740 ASCII-7, noe som ga samvirke med de engelskspråklige landene som ikke
 741 trengte å gjøre noe. Det innebærer også at de første 128 verdiene i
 742 ISO-8859-variantene representerer de samme symbolene. Det er først når
 743 du kommer til tolkningen av de resterende 128 verdiene med nummer 128
 744 til 255, at det oppsto tolkningsutfordringer mellom
 745 ISO-8859-variantene.</p>
 746
 747 <p>ISO-8859-verdenen fungerte godt så lenge tegnsettet som ble brukt når
 748 innhold ble skapt, også ble brukt når innhold ble gjengitt og du ikke
 749 trengte å kombinere innhold fra forskjellige tegnsett i samme
 750 dokument.  Utfordringen med bruken av ISO-8859-variantene ble raskt
 751 tydelig i en mer globalisert verden med utveksling av tekst på tvers
 752 av landegrenser der tekstlig innhold i dokumenter, e-poster og
 753 websider kunne bli skrevet med ett tegnsett og gjengitt med et annet
 754 tegnsett.</p>
 755
 756 <table align="center" width="60%">
 757
 758 <caption>Tabell 3. Viser tolkning av verdiene som er tilegnet de
 759 norske symbolene i ISO-8859-1 i de andre ISO 8859-variatene. Merk
 760 ISO-8859-12 ikke finnes da arbeidet ble avsluttet.<sup>[<a id="tegnsett_access_footnoteref_1" href="#tegnsett_access_footnotedef_1" title="View footnote.">1</a>]</sup></caption>
 761
 762 <tbody>
 763 <tr>
 764 <th>Binærverdi</th>
 765 <th>1</th>
 766 <th>2</th>
 767 <th>3</th>
 768 <th>4</th>
 769 <th>5</th>
 770 <th>6</th>
 771 <th>7</th>
 772 <th>8</th>
 773 <th>9</th>
 774 <th>10</th>
 775 <th>11</th>
 776 <th>13</th>
 777 <th>14</th>
 778 <th>15</th>
 779 <th>16</th>
 780 </tr>
 781 <tr>
 782 <td>11000110</td>
 783 <td>Æ</td>
 784 <td>Ć</td>
 785 <td>Ĉ</td>
 786 <td>Æ</td>
 787 <td>Ц</td>
 788 <td>ئ</td>
 789 <td>Ζ</td>
 790 <td></td>
 791 <td>Æ</td>
 792 <td>Æ</td>
 793 <td>ฦ</td>
 794 <td>Ę</td>
 795 <td>Æ</td>
 796 <td>Æ</td>
 797 <td>Æ</td>
 798 </tr>
 799 <tr>
 800 <td>11011000</td>
 801 <td>Ø</td>
 802 <td>Ř</td>
 803 <td>Ĝ</td>
 804 <td>Ø</td>
 805 <td>и</td>
 806 <td>ظ</td>
 807 <td>Ψ</td>
 808 <td></td>
 809 <td>Ø</td>
 810 <td>Ø</td>
 811 <td>ุ</td>
 812 <td>Ų</td>
 813 <td>Ø</td>
 814 <td>Ø</td>
 815 <td>Ű</td>
 816 </tr>
 817 <tr>
 818 <td>11000101</td>
 819 <td>Å</td>
 820 <td>Ĺ</td>
 821 <td>Ċ</td>
 822 <td>Å</td>
 823 <td>Х</td>
 824 <td>إ</td>
 825 <td>Ε</td>
 826 <td></td>
 827 <td>Å</td>
 828 <td>Å</td>
 829 <td>ล</td>
 830 <td>Å</td>
 831 <td>Å</td>
 832 <td>Å</td>
 833 <td>Ć</td>
 834 </tr>
 835 <tr>
 836 <td>11100110</td>
 837 <td>æ</td>
 838 <td>ć</td>
 839 <td>ĉ</td>
 840 <td>æ</td>
 841 <td>ц</td>
 842 <td>ن</td>
 843 <td>ζ</td>
 844 <td>ז</td>
 845 <td>æ</td>
 846 <td>æ</td>
 847 <td>ๆ</td>
 848 <td>ę</td>
 849 <td>æ</td>
 850 <td>æ</td>
 851 <td>v</td>
 852 </tr>
 853 <tr>
 854 <td>11111000</td>
 855 <td>ø</td>
 856 <td>ř</td>
 857 <td>ĝ</td>
 858 <td>ø</td>
 859 <td>ј</td>
 860 <td></td>
 861 <td>ψ</td>
 862 <td>ר</td>
 863 <td>ø</td>
 864 <td>ø</td>
 865 <td>๘</td>
 866 <td>ų</td>
 867 <td>ø</td>
 868 <td>ø</td>
 869 <td>ű</td>
 870 </tr>
 871 <tr>
 872 <td>11100101</td>
 873 <td>å</td>
 874 <td>ĺ</td>
 875 <td>ċ</td>
 876 <td>å</td>
 877 <td>х</td>
 878 <td>م</td>
 879 <td>ε</td>
 880 <td>ו</td>
 881 <td>å</td>
 882 <td>å</td>
 883 <td>ๅ</td>
 884 <td>å</td>
 885 <td>å</td>
 886 <td>å</td>
 887 <td>ć</td>
 888 </tr>
 889 </tbody>
 890 </table>
 891
 892 <p>Denne problemstillingen er illustrert i tabell 3, der vi ser verdiene
 893 tilegnet de norske symbolene i ISO-8859-1 i kolonne «1». I de øvrige
 894 kolonnene ser vi hvilket symbol verdien får i de andre
 895 ISO-8859-variantene. Tar vi utgangspunkt i tabell 3, kan vi se at
 896 ordet lærlingspørsmål gjengitt med ISO-8859-2 (kolonne 2) blir
 897 lćrlingspřrsmĺl, mens det blir lζrlingspψrsmεl med ISO- 8859-7
 898 (kolonne 7). Med ISO-8859-2 blir «æ» til «ć», «ø» til «ř» og «å» til
 899  «ĺ». I ISO-8859-7 blir «æ» til «ζ», «ø» til «ψ», mens «å» blir «ε».</p>
 900
 901 <p>Det er egentlig ingen utfordring med dette så lenge du vet hvilket
 902 tegnsett innholdet ditt er representert med, og det ikke har skjedd
 903 omforminger som du ikke er klar over. Det er det siste som er
 904 problematisk, spesielt de datasystemene som har vært i bruk de siste
 905 20 årene, som ikke har noe innebygd funksjonalitet for å forvalte
 906 tegnsettproblematikken. Et godt eksempel på dette er
 907 Microsoft-tegnsettet Windows-1252, som ble forvekslet som 100 %
 908 kompatibel med ISO-8859-1, men hadde byttet ut plassene fra 127 til
 909 159. Historisk vil det finnes en del variasjon i hvilket tegnsett som
 910 har vært i bruk, og hvor vellykket konvertering mellom tegnsett har
 911 vært.</p>
 912
 913 <p id="tegnsett_access_unicode_som_løsning"><strong>Unicode som løsning</strong></p>
 914
 915 <p>Tegnsettforvirring ble etter hvert et irritasjonsmoment og
 916 samvirkeproblem. Ofte fikk man en e-post der æøå var erstattet av rare
 917 symboler fordi e-posten hadde vært innom et eller annet datasystem som
 918 ikke brukte samme tegnsett.</p>
 919
 920 <p>For å løse dette samvirkeproblemet for tegnsett ble det startet et
 921 arbeid og en ny standard så dagens lys etter hvert. Denne standarden
 922 fikk navnet Unicode (ISO/ IEC 10646) og skulle resultere i et tegnsett
 923 som alle skulle være enige om. Unicode er et repertoar og en
 924 representasjon, dvs. navngivning og tilordning av tallverdi til alle
 925 symboler i bruk i verden i dag.  Oppføringer i Unicode skrives gjerne
 926 U+XXXX der XXXX er tallkoden i sekstentallssystemet som oppføringen
 927 har i Unicode-katalogen. Her finner vi tegn brukt av både levende og
 928 døde språk, konstruerte språk, tekniske symboler, morsomme tegninger
 929 (såkalte emojier) og tegn ingen vet hva betyr eller skal brukes
 930 til. Et morsomt eksempel er i nettartikkelen: U+237C ⍼ RIGHT ANGLE
 931 WITH DOWNWARDS ZIGZAG ARROW, av Jonathan Chan.<sup>[<a id="tegnsett_access_footnoteref_2" href="#tegnsett_access_footnotedef_2" title="View footnote.">2</a>]</sup></p>
 932
 933 <p>Sammen med Unicode kom det tre måter å kode disse tallene på; UTF-8,
 934 UTF-16 og UTF-32. Av datatekniske årsaker er UTF-8 mye brukt, spesielt
 935 når det gjelder utveksling av tekst over Internett, mens UTF-16 er
 936 brukt en del til tekstfiler lagret på Windows. En utfordring med
 937 Unicode og UTF-variantene er at disse gir flere måter å kode samme
 938 symbol på med en kombinasjonsmekanisme. Dette kan gi utfordringer ved
 939 søk, hvis en skal søke etter et ord som har ett eller flere symboler
 940 som kan skrives på ulikt vis, så er det ikke sikkert at søkesystemet
 941 vil finne alle forekomster. For eksempel kan bokstaven U+00F8 «Latin
 942 Small Letter O with Stroke» kodes som den tradisjonelle norske tegnet
 943 ø, men også som o kombinert med skråstrek U+0338. Begge deler er
 944 gyldig bruk av Unicode, selv om det er tradisjon for å foretrekke å
 945 «normalisere» kombinasjoner som enkelttegn der det er mulig, nettopp
 946 for å forenkle søk.</p>
 947
 948 <p id="tegnsett_access_bare_unicode_fremover"><strong>Bare Unicode fremover</strong></p>
 949
 950 <p>Forvaltningens bruk av tegnsett er regulert i Forskrift om
 951 IT-standarder i offentlig forvaltning<sup>[<a id="tegnsett_access_footnoteref_3" href="#tegnsett_access_footnotedef_3" title="View footnote.">3</a>]</sup>. Her står det: «Ved all
 952 utveksling av informasjon mellom forvaltningsorganer og fra
 953 forvaltningsorgan til innbyggere og næringsliv skal tegnsettstandarden
 954 ISO/IEC 10646 representert ved UTF8 benyttes.»  Det er forskjellige
 955 bruksområder til UTF-8, UTF-16 og UTF-32, men UTF-8 er kodingen vi
 956 kjenner mest til.  Det er flere grunner at UTF-8 «vant» konkurransen
 957 til å bli den utvalgte. Den kanskje viktigste er at UTF-8 er fullt
 958 samvirkende med ASCII-7, slik at den engelskspråklige delen av verden
 959 kunne rulle ut UTF-8 uten å merke noe forskjell. En tekstfil med kun
 960 ASCII-tekst vil være identisk på disken hvis den lagres som UTF-8 og
 961 ASCII. UTF-16 og UTF-32 byr på noen optimaliseringer som gjør dem
 962 relevant for spesifikke problemområder, men for det meste vil vi aldri
 963 oppleve disse standardene på nært hold i hverdagen. Det er uansett kun
 964 bruken av UTF-8 som er lovregulert i Norge.</p>
 965
 966 <p>Det er ikke slik at hele verden bruker ISO/IEC 10646 og UTF-8. Kina
 967 har egne standarder for tegnsett, mye brukt er GB 18030, som er
 968 Unicode med en annen koding enn UTF-8, mens Taiwan og andre asiatiske
 969 land gjerne bruker Big5 eller andre tegnsett.</p>
 970
 971 <p>UTF-8 er dominerende i Norge, men det er tidsperioder der forskjellige
 972 datasystemer utvekslet data i henhold til ISO-8859-1, ISO-8859-15,
 973 Windows-1252, Codepage 865 og ISO-646-60 / Codepage 1016 mens
 974 overgangen til UTF-8 pågikk. Det er ikke slik at et datasystem enkelt
 975 kan tvinges til å bruke et tegnsett, da det er flere lag i et
 976 datasystem som må settes opp til å bruke riktig tegnsett, og
 977 tegnsettproblemet fort oppstår når det er et eller annet i
 978 datasystemet som bruker feil tegnsett.</p>
 979
 980 <p>Et klassisk eksempel på problemet er en utveksling av tekst mellom to
 981 systemer der teksten i utgangspunktet er kodet i UTF-8, men går
 982 gjennom noe som er ISO-8859-1 underveis. Dette kan vises med at ordet
 983 «på» i et slik scenario ender opp som «pÃ¥». Det er mulig å spore
 984 dette tilbake til verdiene symbolene er tilordnet i tegnsettene. «på»
 985 blir til «pÃ¥» fordi «å» i UTF-8 er representert med U+C3AF, og dersom
 986 vi ser på hva disse verdiene representerer, ser vi at
 987 sekstentallssystemverdien C3 er 1100 0011 i totallssystemet og
 988 symbolet med dette tallet i ISO-8859-1 er Ã.</p>
 989
 990 <p>Vi ser det samme med sekstentallssystemverdien A5, som er 1010 0101 i
 991 totallssystemet, og tilsvarende symbol i ISO-8859-1 er ¥. Slik
 992 mojibake kan lett skje hvis «på» i utgangspunktet var representert med
 993 UTF-8, men ble behandlet med et system som bruker ISO-8859-1. Det er
 994 ingen automatikk i å fange opp slike ødeleggelser mens tekstlig
 995 innhold utveksles mellom datasystemer.</p>
 996
 997 <p>En utfordring for depotarkivene er at bruken av tegnsett ikke alltid
 998 har vært regulert, og at det kan finnes flere dokumentasjonssamlinger
 999 som er opprettet med varierende tegnsett før gjeldende forskrift
1000 inntraff – uten at det er mulig å avlede fra filene hvilket tegnsett
1001 som ble brukt. Et eksempel på dette er €-symbolet, som kom først etter
1002 at ISO-8859-1 var tatt i bruk. Det kan bli en utfordring for et
1003 depotarkiv, men så lenge det er kjent hvilket tegnsett var i bruk, så
1004 bør det gå bra.  Riksarkivarens
1005 forskrift<sup>[<a id="tegnsett_access_footnoteref_4" href="#tegnsett_access_footnotedef_4" title="View footnote.">4</a>]</sup>
1006 formaliserer dette ved å kreve følgende:</p>
1007
1008 <blockquote>
1009 <p>§ 5-11. Tegnsett i arkivuttrekk</p>
1010
1011 <ol>
1012   <li>Arkivuttrekk og medfølgende struktur- og innholdsbeskrivelser skal
1013       overføres som ren tekst i ukryptert form, og benytte godkjent
1014       tegnsett.</li>
1015
1016   <li>Godkjente tegnsett er:
1017     <ol>
1018       <li>Unicode UTF-8<br>
1019           (ISO/IEC 10646-1:2000 Annex D)</li>
1020       <li>ISO 8859-1:1998, Latin 1</li>
1021       <li>ISO 8859-4:1998, Latin 4 for samiske tegn.</li>
1022     </ol></li>
1023
1024   <li>Andre tegnsett aksepteres bare etter avtale med Arkivverket.</li>
1025 </ol>
1026 </blockquote>
1027
1028 <p id="tegnsett_access_ditt_ansvar"><strong>Ditt ansvar</strong></p>
1029
1030 <p>På mange måter burde ikke tegnsett være et problem i 2023, men sånn er
1031 det nok ikke. Land som har oppgradert til UTF-8 som primærtegnsett for
1032 utveksling av tekstlig innhold, begrenser problematikken betraktelig,
1033 men globalt sett så er tegnsettutfordringen ikke løst fordi ikke alle
1034 er enige om å bruke samme tegnsett.  Det kan være geopolitiske eller
1035 kulturelle hensyn som ligger til grunn for dette.</p>
1036
1037 <p>Det er uansett verdt å merke at selv om bruken av UTF-8 skulle bli
1038 100% utbredt, så er det et historisk perspektiv (ASCII-7,
1039 ISO-8859-variantene, UTF-8) her som gjør tegnsett til et problemområde
1040 arkivarene må forstå og håndtere.  Som danningsarkivar har du et
1041 ansvar for å vite hvilket tegnsett systemene og databasene dere
1042 forvalter, er i samsvar med. Det er noe IT-avdelingen din eller
1043 programvareleverandørene enkelt skal kunne svare på, og svaret skal
1044 være UTF-8 for alle nye systemer.</p>
1045
1046 <hr>
1047
1048 <p id="tegnsett_access_footnotedef_1"><a href="#tegnsett_access_footnoteref_1">1</a>. Tegnsettkilde <a href="https://en.wikipedia.org/wiki/ISO/IEC_8859">https://en.wikipedia.org/wiki/ISO/IEC_8859</a></p>
1049
1050 <p id="tegnsett_access_footnotedef_2"><a href="#tegnsett_access_footnoteref_2">2</a>. <a href="https://ionathan.ch/2022/04/09/angzarr.html">https://ionathan.ch/2022/04/09/angzarr.html</a></p>
1051
1052 <p id="tegnsett_access_footnotedef_3"><a href="#tegnsett_access_footnoteref_3">3</a>. <a href="https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78">https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78</a></p>
1053
1054 <p id="tegnsett_access_footnotedef_4"><a href="#tegnsett_access_footnoteref_4">4</a>. <a href="https://lovdata.no/forskrift/2017-12-19-2286/§5-11">https://lovdata.no/forskrift/2017-12-19-2286/§5-11</a></p>
1055
1056 </blockquote>
1057
1058 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i Norge.</p>
1059
1060 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1061 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1062 til min adresse
1063 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
1064 betaling med bitcoin er ikke anonymt. :)</p>
1065 </div>
1066       <div class="tags">
1067
1068
1069         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1070
1071
1072       </div>
1073     </div>
1074     <div class="padding"></div>
1075
1076     <div class="entry">
1077       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html">New and improved sqlcipher in Debian for accessing Signal database</a></div>
1078       <div class="date">12th November 2023</div>
1079       <div class="body"><p>For a while now I wanted to have direct access to the
1080 <a href="https://signal.org/">Signal</a> database of messages and
1081 channels of my Desktop edition of Signal.  I prefer the enforced end
1082 to end encryption of Signal these days for my communication with
1083 friends and family, to increase the level of safety and privacy as
1084 well as raising the cost of the mass surveillance government and
1085 non-government entities practice these days.  In August I came across
1086 a nice
1087 <a href="https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/">recipe
1088 on how to use sqlcipher to extract statistics from the Signal
1089 database</a> explaining how to do this.  Unfortunately this did not
1090 work with the version of sqlcipher in Debian.  The
1091 <a href="http://tracker.debian.org/sqlcipher/">sqlcipher</a>
1092 package is a "fork" of the sqlite package with added support for
1093 encrypted databases.  Sadly the current Debian maintainer
1094 <a href="https://bugs.debian.org/961598">announced more than three
1095 years ago that he did not have time to maintain sqlcipher</a>, so it
1096 seemed unlikely to be upgraded by the maintainer.  I was reluctant to
1097 take on the job myself, as I have very limited experience maintaining
1098 shared libraries in Debian.  After waiting and hoping for a few
1099 months, I gave up the last  week, and set out to update the package.  In
1100 the process I orphaned it to make it more obvious for the next person
1101 looking at it that the package need proper maintenance.</p>
1102
1103 <p>The version in Debian was around five years old, and quite a lot of
1104 changes had taken place upstream into the Debian maintenance git
1105 repository.  After spending a few days importing the new upstream
1106 versions, realising that upstream did not care much for SONAME
1107 versioning as I saw library symbols being both added and removed with
1108 minor version number changes to the project, I concluded that I had to
1109 do a SONAME bump of the library package to avoid surprising the
1110 reverse dependencies.  I even added a simple
1111 autopkgtest script to ensure the package work as intended.  Dug deep
1112 into the hole of learning shared library maintenance, I set out a few
1113 days ago to upload the new version to Debian experimental to see what
1114 the quality assurance framework in Debian had to say about the result.
1115 The feedback told me the pacakge was not too shabby, and yesterday I
1116 uploaded the latest version to Debian unstable.  It should enter
1117 testing today or tomorrow, perhaps delayed by
1118 <a href="https://bugs.debian.org/1055812">a small library
1119 transition</a>.</p>
1120
1121 <p>Armed with a new version of sqlcipher, I can now have a look at the
1122 SQL database in ~/.config/Signal/sql/db.sqlite.  First, one need to
1123 fetch the encryption key from the Signal configuration using this
1124 simple JSON extraction command:</p>
1125
1126 <pre>/usr/bin/jq -r '."key"' ~/.config/Signal/config.json</pre>
1127
1128 <p>Assuming the result from that command is 'secretkey', which is a
1129 hexadecimal number representing the key used to encrypt the database.
1130 Next, one can now connect to the database and inject the encryption
1131 key for access via SQL to fetch information from the database.  Here
1132 is an example dumping the database structure:</p>
1133
1134 <pre>
1135 % sqlcipher ~/.config/Signal/sql/db.sqlite
1136 sqlite> PRAGMA key = "x'secretkey'";
1137 sqlite> .schema
1138 CREATE TABLE sqlite_stat1(tbl,idx,stat);
1139 CREATE TABLE conversations(
1140       id STRING PRIMARY KEY ASC,
1141       json TEXT,
1142
1143       active_at INTEGER,
1144       type STRING,
1145       members TEXT,
1146       name TEXT,
1147       profileName TEXT
1148     , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
1149 CREATE TABLE identityKeys(
1150       id STRING PRIMARY KEY ASC,
1151       json TEXT
1152     );
1153 CREATE TABLE items(
1154       id STRING PRIMARY KEY ASC,
1155       json TEXT
1156     );
1157 CREATE TABLE sessions(
1158       id TEXT PRIMARY KEY,
1159       conversationId TEXT,
1160       json TEXT
1161     , ourServiceId STRING, serviceId STRING);
1162 CREATE TABLE attachment_downloads(
1163     id STRING primary key,
1164     timestamp INTEGER,
1165     pending INTEGER,
1166     json TEXT
1167   );
1168 CREATE TABLE sticker_packs(
1169     id TEXT PRIMARY KEY,
1170     key TEXT NOT NULL,
1171
1172     author STRING,
1173     coverStickerId INTEGER,
1174     createdAt INTEGER,
1175     downloadAttempts INTEGER,
1176     installedAt INTEGER,
1177     lastUsed INTEGER,
1178     status STRING,
1179     stickerCount INTEGER,
1180     title STRING
1181   , attemptedStatus STRING, position INTEGER DEFAULT 0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
1182       INTEGER DEFAULT 0 NOT NULL);
1183 CREATE TABLE stickers(
1184     id INTEGER NOT NULL,
1185     packId TEXT NOT NULL,
1186
1187     emoji STRING,
1188     height INTEGER,
1189     isCoverOnly INTEGER,
1190     lastUsed INTEGER,
1191     path STRING,
1192     width INTEGER,
1193
1194     PRIMARY KEY (id, packId),
1195     CONSTRAINT stickers_fk
1196       FOREIGN KEY (packId)
1197       REFERENCES sticker_packs(id)
1198       ON DELETE CASCADE
1199   );
1200 CREATE TABLE sticker_references(
1201     messageId STRING,
1202     packId TEXT,
1203     CONSTRAINT sticker_references_fk
1204       FOREIGN KEY(packId)
1205       REFERENCES sticker_packs(id)
1206       ON DELETE CASCADE
1207   );
1208 CREATE TABLE emojis(
1209     shortName TEXT PRIMARY KEY,
1210     lastUsage INTEGER
1211   );
1212 CREATE TABLE messages(
1213         rowid INTEGER PRIMARY KEY ASC,
1214         id STRING UNIQUE,
1215         json TEXT,
1216         readStatus INTEGER,
1217         expires_at INTEGER,
1218         sent_at INTEGER,
1219         schemaVersion INTEGER,
1220         conversationId STRING,
1221         received_at INTEGER,
1222         source STRING,
1223         hasAttachments INTEGER,
1224         hasFileAttachments INTEGER,
1225         hasVisualMediaAttachments INTEGER,
1226         expireTimer INTEGER,
1227         expirationStartTimestamp INTEGER,
1228         type STRING,
1229         body TEXT,
1230         messageTimer INTEGER,
1231         messageTimerStart INTEGER,
1232         messageTimerExpiresAt INTEGER,
1233         isErased INTEGER,
1234         isViewOnce INTEGER,
1235         sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
1236         GENERATED ALWAYS AS (type IS 'story'), isChangeCreatedByUs INTEGER NOT NULL DEFAULT 0, isTimerChangeFromSync INTEGER
1237         GENERATED ALWAYS AS (
1238           json_extract(json, '$.expirationTimerUpdate.fromSync') IS 1
1239         ), seenStatus NUMBER default 0, storyDistributionListId STRING, expiresAt INT
1240         GENERATED ALWAYS
1241         AS (ifnull(
1242           expirationStartTimestamp + (expireTimer * 1000),
1243           9007199254740991
1244         )), shouldAffectActivity INTEGER
1245         GENERATED ALWAYS AS (
1246           type IS NULL
1247           OR
1248           type NOT IN (
1249             'change-number-notification',
1250             'contact-removed-notification',
1251             'conversation-merge',
1252             'group-v1-migration',
1253             'keychange',
1254             'message-history-unsynced',
1255             'profile-change',
1256             'story',
1257             'universal-timer-notification',
1258             'verified-change'
1259           )
1260         ), shouldAffectPreview INTEGER
1261         GENERATED ALWAYS AS (
1262           type IS NULL
1263           OR
1264           type NOT IN (
1265             'change-number-notification',
1266             'contact-removed-notification',
1267             'conversation-merge',
1268             'group-v1-migration',
1269             'keychange',
1270             'message-history-unsynced',
1271             'profile-change',
1272             'story',
1273             'universal-timer-notification',
1274             'verified-change'
1275           )
1276         ), isUserInitiatedMessage INTEGER
1277         GENERATED ALWAYS AS (
1278           type IS NULL
1279           OR
1280           type NOT IN (
1281             'change-number-notification',
1282             'contact-removed-notification',
1283             'conversation-merge',
1284             'group-v1-migration',
1285             'group-v2-change',
1286             'keychange',
1287             'message-history-unsynced',
1288             'profile-change',
1289             'story',
1290             'universal-timer-notification',
1291             'verified-change'
1292           )
1293         ), mentionsMe INTEGER NOT NULL DEFAULT 0, isGroupLeaveEvent INTEGER
1294         GENERATED ALWAYS AS (
1295           type IS 'group-v2-change' AND
1296           json_array_length(json_extract(json, '$.groupV2Change.details')) IS 1 AND
1297           json_extract(json, '$.groupV2Change.details[0].type') IS 'member-remove' AND
1298           json_extract(json, '$.groupV2Change.from') IS NOT NULL AND
1299           json_extract(json, '$.groupV2Change.from') IS json_extract(json, '$.groupV2Change.details[0].aci')
1300         ), isGroupLeaveEventFromOther INTEGER
1301         GENERATED ALWAYS AS (
1302           isGroupLeaveEvent IS 1
1303           AND
1304           isChangeCreatedByUs IS 0
1305         ), callId TEXT
1306         GENERATED ALWAYS AS (
1307           json_extract(json, '$.callId')
1308         ));
1309 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
1310 CREATE TABLE jobs(
1311         id TEXT PRIMARY KEY,
1312         queueType TEXT STRING NOT NULL,
1313         timestamp INTEGER NOT NULL,
1314         data STRING TEXT
1315       );
1316 CREATE TABLE reactions(
1317         conversationId STRING,
1318         emoji STRING,
1319         fromId STRING,
1320         messageReceivedAt INTEGER,
1321         targetAuthorAci STRING,
1322         targetTimestamp INTEGER,
1323         unread INTEGER
1324       , messageId STRING);
1325 CREATE TABLE senderKeys(
1326         id TEXT PRIMARY KEY NOT NULL,
1327         senderId TEXT NOT NULL,
1328         distributionId TEXT NOT NULL,
1329         data BLOB NOT NULL,
1330         lastUpdatedDate NUMBER NOT NULL
1331       );
1332 CREATE TABLE unprocessed(
1333         id STRING PRIMARY KEY ASC,
1334         timestamp INTEGER,
1335         version INTEGER,
1336         attempts INTEGER,
1337         envelope TEXT,
1338         decrypted TEXT,
1339         source TEXT,
1340         serverTimestamp INTEGER,
1341         sourceServiceId STRING
1342       , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
1343 CREATE TABLE sendLogPayloads(
1344         id INTEGER PRIMARY KEY ASC,
1345
1346         timestamp INTEGER NOT NULL,
1347         contentHint INTEGER NOT NULL,
1348         proto BLOB NOT NULL
1349       , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT 0 NOT NULL);
1350 CREATE TABLE sendLogRecipients(
1351         payloadId INTEGER NOT NULL,
1352
1353         recipientServiceId STRING NOT NULL,
1354         deviceId INTEGER NOT NULL,
1355
1356         PRIMARY KEY (payloadId, recipientServiceId, deviceId),
1357
1358         CONSTRAINT sendLogRecipientsForeignKey
1359           FOREIGN KEY (payloadId)
1360           REFERENCES sendLogPayloads(id)
1361           ON DELETE CASCADE
1362       );
1363 CREATE TABLE sendLogMessageIds(
1364         payloadId INTEGER NOT NULL,
1365
1366         messageId STRING NOT NULL,
1367
1368         PRIMARY KEY (payloadId, messageId),
1369
1370         CONSTRAINT sendLogMessageIdsForeignKey
1371           FOREIGN KEY (payloadId)
1372           REFERENCES sendLogPayloads(id)
1373           ON DELETE CASCADE
1374       );
1375 CREATE TABLE preKeys(
1376         id STRING PRIMARY KEY ASC,
1377         json TEXT
1378       , ourServiceId NUMBER
1379         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1380 CREATE TABLE signedPreKeys(
1381         id STRING PRIMARY KEY ASC,
1382         json TEXT
1383       , ourServiceId NUMBER
1384         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1385 CREATE TABLE badges(
1386         id TEXT PRIMARY KEY,
1387         category TEXT NOT NULL,
1388         name TEXT NOT NULL,
1389         descriptionTemplate TEXT NOT NULL
1390       );
1391 CREATE TABLE badgeImageFiles(
1392         badgeId TEXT REFERENCES badges(id)
1393           ON DELETE CASCADE
1394           ON UPDATE CASCADE,
1395         'order' INTEGER NOT NULL,
1396         url TEXT NOT NULL,
1397         localPath TEXT,
1398         theme TEXT NOT NULL
1399       );
1400 CREATE TABLE storyReads (
1401         authorId STRING NOT NULL,
1402         conversationId STRING NOT NULL,
1403         storyId STRING NOT NULL,
1404         storyReadDate NUMBER NOT NULL,
1405
1406         PRIMARY KEY (authorId, storyId)
1407       );
1408 CREATE TABLE storyDistributions(
1409         id STRING PRIMARY KEY NOT NULL,
1410         name TEXT,
1411
1412         senderKeyInfoJson STRING
1413       , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
1414 CREATE TABLE storyDistributionMembers(
1415         listId STRING NOT NULL REFERENCES storyDistributions(id)
1416           ON DELETE CASCADE
1417           ON UPDATE CASCADE,
1418         serviceId STRING NOT NULL,
1419
1420         PRIMARY KEY (listId, serviceId)
1421       );
1422 CREATE TABLE uninstalled_sticker_packs (
1423         id STRING NOT NULL PRIMARY KEY,
1424         uninstalledAt NUMBER NOT NULL,
1425         storageID STRING,
1426         storageVersion NUMBER,
1427         storageUnknownFields BLOB,
1428         storageNeedsSync INTEGER NOT NULL
1429       );
1430 CREATE TABLE groupCallRingCancellations(
1431         ringId INTEGER PRIMARY KEY,
1432         createdAt INTEGER NOT NULL
1433       );
1434 CREATE TABLE IF NOT EXISTS 'messages_fts_data'(id INTEGER PRIMARY KEY, block BLOB);
1435 CREATE TABLE IF NOT EXISTS 'messages_fts_idx'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
1436 CREATE TABLE IF NOT EXISTS 'messages_fts_content'(id INTEGER PRIMARY KEY, c0);
1437 CREATE TABLE IF NOT EXISTS 'messages_fts_docsize'(id INTEGER PRIMARY KEY, sz BLOB);
1438 CREATE TABLE IF NOT EXISTS 'messages_fts_config'(k PRIMARY KEY, v) WITHOUT ROWID;
1439 CREATE TABLE edited_messages(
1440         messageId STRING REFERENCES messages(id)
1441           ON DELETE CASCADE,
1442         sentAt INTEGER,
1443         readStatus INTEGER
1444       , conversationId STRING);
1445 CREATE TABLE mentions (
1446         messageId REFERENCES messages(id) ON DELETE CASCADE,
1447         mentionAci STRING,
1448         start INTEGER,
1449         length INTEGER
1450       );
1451 CREATE TABLE kyberPreKeys(
1452         id STRING PRIMARY KEY NOT NULL,
1453         json TEXT NOT NULL, ourServiceId NUMBER
1454         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1455 CREATE TABLE callsHistory (
1456         callId TEXT PRIMARY KEY,
1457         peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
1458         ringerId TEXT DEFAULT NULL, -- ringer uuid
1459         mode TEXT NOT NULL, -- enum "Direct" | "Group"
1460         type TEXT NOT NULL, -- enum "Audio" | "Video" | "Group"
1461         direction TEXT NOT NULL, -- enum "Incoming" | "Outgoing
1462         -- Direct: enum "Pending" | "Missed" | "Accepted" | "Deleted"
1463         -- Group: enum "GenericGroupCall" | "OutgoingRing" | "Ringing" | "Joined" | "Missed" | "Declined" | "Accepted" | "Deleted"
1464         status TEXT NOT NULL,
1465         timestamp INTEGER NOT NULL,
1466         UNIQUE (callId, peerId) ON CONFLICT FAIL
1467       );
1468 [ dropped all indexes to save space in this blog post ]
1469 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
1470       WHEN
1471         new.body IS NOT NULL AND new.isViewOnce = 1
1472       BEGIN
1473         DELETE FROM messages_fts WHERE rowid = old.rowid;
1474       END;
1475 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
1476       WHEN new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1477       BEGIN
1478         INSERT INTO messages_fts
1479           (rowid, body)
1480         VALUES
1481           (new.rowid, new.body);
1482       END;
1483 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
1484         DELETE FROM messages_fts WHERE rowid = old.rowid;
1485         DELETE FROM sendLogPayloads WHERE id IN (
1486           SELECT payloadId FROM sendLogMessageIds
1487           WHERE messageId = old.id
1488         );
1489         DELETE FROM reactions WHERE rowid IN (
1490           SELECT rowid FROM reactions
1491           WHERE messageId = old.id
1492         );
1493         DELETE FROM storyReads WHERE storyId = old.storyId;
1494       END;
1495 CREATE VIRTUAL TABLE messages_fts USING fts5(
1496         body,
1497         tokenize = 'signal_tokenizer'
1498       );
1499 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
1500       WHEN
1501         (new.body IS NULL OR old.body IS NOT new.body) AND
1502          new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1503       BEGIN
1504         DELETE FROM messages_fts WHERE rowid = old.rowid;
1505         INSERT INTO messages_fts
1506           (rowid, body)
1507         VALUES
1508           (new.rowid, new.body);
1509       END;
1510 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
1511       BEGIN
1512         INSERT INTO mentions (messageId, mentionAci, start, length)
1513
1514     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1515       bodyRanges.value ->> 'start' as start,
1516       bodyRanges.value ->> 'length' as length
1517     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1518     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1519
1520         AND messages.id = new.id;
1521       END;
1522 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
1523       BEGIN
1524         DELETE FROM mentions WHERE messageId = new.id;
1525         INSERT INTO mentions (messageId, mentionAci, start, length)
1526
1527     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1528       bodyRanges.value ->> 'start' as start,
1529       bodyRanges.value ->> 'length' as length
1530     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1531     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1532
1533         AND messages.id = new.id;
1534       END;
1535 sqlite>
1536 </pre>
1537
1538 <p>Finally I have the tool needed to inspect and process Signal
1539 messages that I need, without using the vendor provided client.  Now
1540 on to transforming it to a more useful format.</p>
1541
1542 <p>As usual, if you use Bitcoin and want to show your support of my
1543 activities, please send Bitcoin donations to my address
1544 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1545 </div>
1546       <div class="tags">
1547
1548
1549         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
1550
1551
1552       </div>
1553     </div>
1554     <div class="padding"></div>
1555
1556     <div class="entry">
1557       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html">New chrpath release 0.17</a></div>
1558       <div class="date">10th November 2023</div>
1559       <div class="body"><p>The chrpath package provide a simple command line tool to remove or
1560 modify the rpath or runpath of compiled ELF program.  It is almost 10
1561 years since I updated the code base, but I stumbled over the tool
1562 today, and decided it was time to move the code base from Subversion
1563 to git and find a new home for it, as the previous one (Debian Alioth)
1564 has been shut down.  I decided to go with
1565 <a href="https://codeberg.org/">Codeberg</a> this time, as it is my git
1566 service of choice these days, did a quick and dirty migration to git
1567 and updated the code with a few patches I found in the Debian bug
1568 tracker.  These are the release notes:</p>
1569
1570 <p>New in 0.17 released 2023-11-10:</p>
1571
1572 <ul>
1573 <li>Moved project to Codeberg, as Alioth is shut down.</li>
1574 <li>Add Solaris support (use &lt;sys/byteorder.h> instead of &lt;byteswap.h>).
1575    Patch from Rainer Orth.</li>
1576 <li>Added missing newline from printf() line.  Patch from Frank Dana.</li>
1577 <li>Corrected handling of multiple ELF sections. Patch from Frank Dana.</li>
1578 <li>Updated build rules for .deb.  Partly based on patch from djcj.</li>
1579 </ul>
1580
1581 <p>The latest edition is tagged and available from
1582 <a href="https://codeberg.org/pere/chrpath">https://codeberg.org/pere/chrpath</a>.
1583
1584 <p>As usual, if you use Bitcoin and want to show your support of my
1585 activities, please send Bitcoin donations to my address
1586 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1587 </div>
1588       <div class="tags">
1589
1590
1591         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
1592
1593
1594       </div>
1595     </div>
1596     <div class="padding"></div>
1597
1598     <p style="text-align: right;"><a href="index.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
1599     <div id="sidebar">
1600
1601
1602
1603 <h2>Archive</h2>
1604 <ul>
1605
1606 <li>2024
1607 <ul>
1608
1609 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/01/">January (1)</a></li>
1610
1611 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/02/">February (1)</a></li>
1612
1613 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/03/">March (2)</a></li>
1614
1615 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/04/">April (2)</a></li>
1616
1617 </ul></li>
1618
1619 <li>2023
1620 <ul>
1621
1622 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
1623
1624 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
1625
1626 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/04/">April (2)</a></li>
1627
1628 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/05/">May (3)</a></li>
1629
1630 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/06/">June (1)</a></li>
1631
1632 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/08/">August (1)</a></li>
1633
1634 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/09/">September (1)</a></li>
1635
1636 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/10/">October (1)</a></li>
1637
1638 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/11/">November (4)</a></li>
1639
1640 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/12/">December (1)</a></li>
1641
1642 </ul></li>
1643
1644 <li>2022
1645 <ul>
1646
1647 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
1648
1649 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
1650
1651 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
1652
1653 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
1654
1655 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
1656
1657 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
1658
1659 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
1660
1661 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
1662
1663 </ul></li>
1664
1665 <li>2021
1666 <ul>
1667
1668 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
1669
1670 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
1671
1672 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
1673
1674 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
1675
1676 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
1677
1678 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
1679
1680 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
1681
1682 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
1683
1684 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
1685
1686 </ul></li>
1687
1688 <li>2020
1689 <ul>
1690
1691 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
1692
1693 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
1694
1695 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
1696
1697 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
1698
1699 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
1700
1701 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
1702
1703 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
1704
1705 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
1706
1707 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
1708
1709 </ul></li>
1710
1711 <li>2019
1712 <ul>
1713
1714 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
1715
1716 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
1717
1718 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
1719
1720 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
1721
1722 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
1723
1724 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
1725
1726 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
1727
1728 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
1729
1730 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
1731
1732 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
1733
1734 </ul></li>
1735
1736 <li>2018
1737 <ul>
1738
1739 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
1740
1741 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
1742
1743 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
1744
1745 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
1746
1747 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
1748
1749 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
1750
1751 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
1752
1753 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
1754
1755 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
1756
1757 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
1758
1759 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
1760
1761 </ul></li>
1762
1763 <li>2017
1764 <ul>
1765
1766 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1767
1768 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
1769
1770 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
1771
1772 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
1773
1774 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
1775
1776 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
1777
1778 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
1779
1780 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
1781
1782 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
1783
1784 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
1785
1786 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
1787
1788 </ul></li>
1789
1790 <li>2016
1791 <ul>
1792
1793 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1794
1795 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1796
1797 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1798
1799 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1800
1801 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1802
1803 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1804
1805 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1806
1807 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1808
1809 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1810
1811 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1812
1813 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1814
1815 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1816
1817 </ul></li>
1818
1819 <li>2015
1820 <ul>
1821
1822 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1823
1824 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1825
1826 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1827
1828 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1829
1830 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1831
1832 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1833
1834 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1835
1836 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1837
1838 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1839
1840 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1841
1842 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1843
1844 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1845
1846 </ul></li>
1847
1848 <li>2014
1849 <ul>
1850
1851 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1852
1853 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1854
1855 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1856
1857 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1858
1859 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1860
1861 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1862
1863 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1864
1865 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1866
1867 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1868
1869 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1870
1871 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1872
1873 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1874
1875 </ul></li>
1876
1877 <li>2013
1878 <ul>
1879
1880 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1881
1882 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1883
1884 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1885
1886 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1887
1888 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1889
1890 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1891
1892 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1893
1894 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1895
1896 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1897
1898 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1899
1900 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1901
1902 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1903
1904 </ul></li>
1905
1906 <li>2012
1907 <ul>
1908
1909 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1910
1911 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1912
1913 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1914
1915 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1916
1917 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1918
1919 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1920
1921 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1922
1923 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1924
1925 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1926
1927 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1928
1929 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1930
1931 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1932
1933 </ul></li>
1934
1935 <li>2011
1936 <ul>
1937
1938 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1939
1940 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1941
1942 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1943
1944 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1945
1946 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1947
1948 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1949
1950 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1951
1952 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1953
1954 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1955
1956 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1957
1958 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1959
1960 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1961
1962 </ul></li>
1963
1964 <li>2010
1965 <ul>
1966
1967 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1968
1969 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1970
1971 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1972
1973 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1974
1975 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1976
1977 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1978
1979 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1980
1981 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1982
1983 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1984
1985 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1986
1987 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1988
1989 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1990
1991 </ul></li>
1992
1993 <li>2009
1994 <ul>
1995
1996 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1997
1998 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1999
2000 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
2001
2002 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
2003
2004 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
2005
2006 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
2007
2008 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
2009
2010 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
2011
2012 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
2013
2014 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
2015
2016 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
2017
2018 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
2019
2020 </ul></li>
2021
2022 <li>2008
2023 <ul>
2024
2025 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
2026
2027 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
2028
2029 </ul></li>
2030
2031 </ul>
2032
2033
2034
2035 <h2>Tags</h2>
2036 <ul>
2037
2038  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
2039
2040  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
2041
2042  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
2043
2044  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
2045
2046  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
2047
2048  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (13)</a></li>
2049
2050  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
2051
2052  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
2053
2054  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (3)</a></li>
2055
2056  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (198)</a></li>
2057
2058  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
2059
2060  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
2061
2062  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
2063
2064  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
2065
2066  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (32)</a></li>
2067
2068  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
2069
2070  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (460)</a></li>
2071
2072  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
2073
2074  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
2075
2076  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
2077
2078  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
2079
2080  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
2081
2082  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
2083
2084  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
2085
2086  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (18)</a></li>
2087
2088  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
2089
2090  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (6)</a></li>
2091
2092  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
2093
2094  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
2095
2096  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
2097
2098  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (5)</a></li>
2099
2100  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
2101
2102  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
2103
2104  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
2105
2106  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
2107
2108  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (46)</a></li>
2109
2110  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (15)</a></li>
2111
2112  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (25)</a></li>
2113
2114  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (324)</a></li>
2115
2116  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (199)</a></li>
2117
2118  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (41)</a></li>
2119
2120  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
2121
2122  <li><a href="https://people.skolelinux.org/pere/blog/tags/opensnitch">opensnitch (4)</a></li>
2123
2124  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
2125
2126  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
2127
2128  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (4)</a></li>
2129
2130  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
2131
2132  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
2133
2134  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
2135
2136  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
2137
2138  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
2139
2140  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
2141
2142  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
2143
2144  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
2145
2146  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
2147
2148  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
2149
2150  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (76)</a></li>
2151
2152  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
2153
2154  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
2155
2156  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (65)</a></li>
2157
2158  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
2159
2160  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
2161
2162  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
2163
2164  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (22)</a></li>
2165
2166  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (80)</a></li>
2167
2168  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
2169
2170  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
2171
2172 </ul>
2173
2174
2175     </div>
2176     <p style="text-align: right">
2177  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
2178 </p>
2179
2180   </body>
2181 </html>