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