Converted pages to temp site.

[homepage.git] / blog / archive / 2016 / 10 / 10.rss

<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
        <channel>
                <title>Petter Reinholdtsen - Entries from October 2016</title>
                <description>Entries from October 2016</description>
                <link>https://www.hungry.com/~pere/blog/</link>

        
        <item>
                <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
                <link>https://www.hungry.com/~pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>        
                <guid isPermaLink="true">https://www.hungry.com/~pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
                <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
                <description>&lt;p&gt;In July
&lt;a href=&quot;https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
the ability to receive SMS messages (aka without a cell phone).  It is
time to share some experiences and provide an updated setup.&lt;/p&gt;

&lt;p&gt;The Signal app have worked fine for several months now, and I use
it regularly to chat with my loved ones.  I had a major snag at the
end of my summer vacation, when the the app completely forgot my
setup, identity and keys.  The reason behind this major mess was
running out of disk space.  To avoid that ever happening again I have
started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
roll back to an earlier version if the files are wiped by mistake.  I
had to use it once after introducing the git backup.  When rolling
back to an earlier version, one need to use the &#39;reset session&#39; option
in Signal to get going, and notify the people you talk with about the
problem.  I assume there is some sequence number tracking in the
protocol to detect rollback attacks.  The git repository is rather big
(674 MiB so far), but I have not tried to figure out if some of the
content can be added to a .gitignore file due to lack of spare
time.&lt;/p&gt;

&lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
make it impossible to send messages using Signal.  I could still
receive them, but had to patch the code with a new timestamp to send.
I believe the timeout is added by the developers to force people to
upgrade to the latest version of the app, even when there is no
protocol changes, to reduce the version skew among the user base and
thus try to keep the number of support requests down.&lt;/p&gt;

&lt;p&gt;Since my original recipe, the Signal source code changed slightly,
making the old patch fail to apply cleanly.  Below is an updated
patch, including the shell wrapper I use to start Signal.  The
original version required a new user to locate the JavaScript console
and call a function from there.  I got help from a friend with more
JavaScript knowledge than me to modify the code to provide a GUI
button instead.  This mean that to get started you just need to run
the wrapper and click the &#39;Register without mobile phone&#39; to get going
now.  I&#39;ve also modified the timeout code to always set it to 90 days
in the future, to avoid having to patch the code regularly.&lt;/p&gt;

&lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;

&lt;ol&gt;

&lt;li&gt;First, install required packages to get the source code and the
browser you need.  Signal only work with Chrome/Chromium, as far as I
know, so you need to install it.

&lt;pre&gt;
apt install git tor chromium
git clone https://github.com/WhisperSystems/Signal-Desktop.git
&lt;/pre&gt;&lt;/li&gt;

&lt;li&gt;Modify the source code using command listed in the the patch
block below.&lt;/li&gt;

&lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
&lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).

&lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
number you can receive calls to the next minute, receive the
verification code and enter it into the form field and press
&#39;Register&#39;.  Note, the phone number you use will be user Signal
username, ie the way others can find you on Signal.&lt;/li&gt;

&lt;li&gt;You can now use Signal to contact others.  Note, new contacts do
not show up in the contact list until you restart Signal, and there is
no way to assign names to Contacts.  There is also no way to create or
update chat groups.  I suspect this is because the web app do not have
a associated contact database.&lt;/li&gt;

&lt;/ol&gt;

&lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
main author moxie0 reject federation and accept dependencies to major
corporations like Google (part of the code is fetched from Google) and
Amazon (the central coordination point is owned by Amazon).  See for
example
&lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
view on these issues.  But the network effect is strong in this case,
and several of the people I want to communicate with already use
Signal.  Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
laptop&lt;/a&gt;?  It already work on Windows and Android, and is included
in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
&lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
working on Debian Stable.&lt;/p&gt;

&lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
working.  It switch to the production servers, disable to timeout,
make registration easier and add the shell wrapper:&lt;/p&gt;

&lt;pre&gt;
cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
diff --git a/js/background.js b/js/background.js
index 24b4c1d..579345f 100644
--- a/js/background.js
+++ b/js/background.js
@@ -33,9 +33,9 @@
         });
     });
 
-    var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
+    var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
     var SERVER_PORTS = [80, 4433, 8443];
-    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
+    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
     var messageReceiver;
     window.getSocketStatus = function() {
         if (messageReceiver) {
diff --git a/js/expire.js b/js/expire.js
index 639aeae..beb91c3 100644
--- a/js/expire.js
+++ b/js/expire.js
@@ -1,6 +1,6 @@
 ;(function() {
     &#39;use strict&#39;;
-    var BUILD_EXPIRATION = 0;
+    var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
 
     window.extension = window.extension || {};
 
diff --git a/js/views/install_view.js b/js/views/install_view.js
index 7816f4f..1d6233b 100644
--- a/js/views/install_view.js
+++ b/js/views/install_view.js
@@ -38,7 +38,8 @@
             return {
                 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
                 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
-                &#39;click .step3&#39;: this.selectStep.bind(this, 3)
+                &#39;click .step3&#39;: this.selectStep.bind(this, 3),
+                &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
             };
         },
         clearQR: function() {
diff --git a/options.html b/options.html
index dc0f28e..8d709f6 100644
--- a/options.html
+++ b/options.html
@@ -14,7 +14,10 @@
         &amp;lt;div class=&#39;nav&#39;&gt;
           &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
           &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
-          &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
+          &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
+           &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
+
+         &amp;lt;/div&gt;
           &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
           &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
           &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
--- /dev/null   2016-10-07 09:55:13.730181472 +0200
+++ b/run-signal-app   2016-10-10 08:54:09.434172391 +0200
@@ -0,0 +1,12 @@
+#!/bin/sh
+set -e
+cd $(dirname $0)
+mkdir -p userdata
+userdata=&quot;`pwd`/userdata&quot;
+if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
+    (cd $userdata &amp;&amp; git init)
+fi
+(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
+exec chromium \
+  --proxy-server=&quot;socks://localhost:9050&quot; \
+  --user-data-dir=$userdata --load-and-launch-app=`pwd`
EOF
chmod a+rx run-signal-app
&lt;/pre&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>NRKs kildevern når NRK-epost deles med utenlands etterretning?</title>
                <link>https://www.hungry.com/~pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</link>        
                <guid isPermaLink="true">https://www.hungry.com/~pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</guid>
                <pubDate>Sat, 8 Oct 2016 08:15:00 +0200</pubDate>
                <description>&lt;p&gt;NRK
&lt;a href=&quot;https://nrkbeta.no/2016/09/02/securing-whistleblowers/&quot;&gt;lanserte
for noen uker siden&lt;/a&gt; en ny
&lt;a href=&quot;https://www.nrk.no/varsle/&quot;&gt;varslerportal som bruker
SecureDrop til å ta imot tips&lt;/a&gt; der det er vesentlig at ingen
utenforstående får vite at NRK er tipset.  Det er et langt steg
fremover for NRK, og når en leser bloggposten om hva de har tenkt på
og hvordan løsningen er satt opp virker det som om de har gjort en
grundig jobb der.  Men det er ganske mye ekstra jobb å motta tips via
SecureDrop, så varslersiden skriver &quot;Nyhetstips som ikke krever denne
typen ekstra vern vil vi gjerne ha på nrk.no/03030&quot;, og 03030-siden
foreslår i tillegg til et webskjema å bruke epost, SMS, telefon,
personlig oppmøte og brevpost.  Denne artikkelen handler disse andre
metodene.&lt;/p&gt;

&lt;p&gt;Når en sender epost til en @nrk.no-adresse så vil eposten sendes ut
av landet til datamaskiner kontrollert av Microsoft.  En kan sjekke
dette selv ved å slå opp epostleveringsadresse (MX) i DNS.  For NRK er
dette i dag &quot;nrk-no.mail.protection.outlook.com&quot;.  NRK har som en ser
valgt å sette bort epostmottaket sitt til de som står bak outlook.com,
dvs. Microsoft.  En kan sjekke hvor nettverkstrafikken tar veien
gjennom Internett til epostmottaket vha. programmet
&lt;tt&gt;traceroute&lt;/tt&gt;, og finne ut hvem som eier en Internett-adresse
vha. whois-systemet.  Når en gjør dette for epost-trafikk til @nrk.no
ser en at trafikken fra Norge mot nrk-no.mail.protection.outlook.com
går via Sverige mot enten Irland eller Tyskland (det varierer fra gang
til gang og kan endre seg over tid).&lt;/p&gt;

&lt;p&gt;Vi vet fra
&lt;a href=&quot;https://no.wikipedia.org/wiki/FRA-loven&quot;&gt;introduksjonen av
FRA-loven&lt;/a&gt; at IP-trafikk som passerer grensen til Sverige avlyttes
av Försvarets radioanstalt (FRA).  Vi vet videre takket være
Snowden-bekreftelsene at trafikk som passerer grensen til
Storbritannia avlyttes av Government Communications Headquarters
(GCHQ).  I tillegg er er det nettopp lansert et forslag i Norge om at
forsvarets E-tjeneste skal få avlytte trafikk som krysser grensen til
Norge. Jeg er ikke kjent med dokumentasjon på at Irland og Tyskland
gjør det samme.  Poenget er uansett at utenlandsk etterretning har
mulighet til å snappe opp trafikken når en sender epost til @nrk.no.
I tillegg er det selvsagt tilgjengelig for Microsoft som er underlagt USAs
jurisdiksjon og
&lt;a href=&quot;https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data&quot;&gt;samarbeider
med USAs etterretning på flere områder&lt;/a&gt;.  De som tipser NRK om
nyheter via epost kan dermed gå ut fra at det blir kjent for mange
andre enn NRK at det er gjort.&lt;/p&gt;

&lt;p&gt;Bruk av SMS og telefon registreres av blant annet telefonselskapene
og er tilgjengelig i følge lov og forskrift for blant annet Politi,
NAV og Finanstilsynet, i tillegg til IT-folkene hos telefonselskapene
og deres overordnede.  Hvis innringer eller mottaker bruker
smarttelefon vil slik kontakt også gjøres tilgjengelig for ulike
app-leverandører og de som lytter på trafikken mellom telefon og
app-leverandør, alt etter hva som er installert på telefonene som
brukes.&lt;/p&gt;

&lt;p&gt;Brevpost kan virke trygt, og jeg vet ikke hvor mye som registreres
og lagres av postens datastyrte postsorteringssentraler.  Det vil ikke
overraske meg om det lagres hvor i landet hver konvolutt kommer fra og
hvor den er adressert, i hvert fall for en kortere periode.  Jeg vet
heller ikke hvem slik informasjon gjøres tilgjengelig for.  Det kan
være nok til å ringe inn potensielle kilder når det krysses med hvem
som kjente til aktuell informasjon og hvor de befant seg (tilgjengelig
f.eks.  hvis de bærer mobiltelefon eller bor i nærheten).&lt;/p&gt;

&lt;p&gt;Personlig oppmøte hos en NRK-journalist er antagelig det tryggeste,
men en bør passe seg for å bruke NRK-kantina.  Der bryter de nemlig
&lt;a href=&quot;http://www.lovdata.no/all/hl-19850524-028.html#14&quot;&gt;Sentralbanklovens
paragraf 14&lt;/a&gt; og nekter folk å betale med kontanter.  I stedet
krever de at en varsle sin bankkortutsteder om hvor en befinner seg
ved å bruke bankkort.  Banktransaksjoner er tilgjengelig for
bankkortutsteder (det være seg VISA, Mastercard, Nets og/eller en
bank) i tillegg til politiet og i hvert fall tidligere med Se &amp; Hør
(via utro tjenere, slik det ble avslørt etter utgivelsen av boken
«Livet, det forbannede» av Ken B. Rasmussen).  Men hvor mange kjenner
en NRK-journalist personlig?  Besøk på NRK på Marienlyst krever at en
registrerer sin ankost elektronisk i besøkssystemet.  Jeg vet ikke hva
som skjer med det datasettet, men har grunn til å tro at det sendes ut
SMS til den en skal besøke med navnet som er oppgitt.  Kanskje greit å
oppgi falskt navn.&lt;/p&gt;

&lt;p&gt;Når så tipset er kommet frem til NRK skal det behandles
redaksjonelt i NRK.  Der vet jeg via ulike kilder at de fleste
journalistene bruker lokalt installert programvare, men noen bruker
Google Docs og andre skytjenester i strid med interne retningslinjer
når de skriver.  Hvordan vet en hvem det gjelder?  Ikke vet jeg, men
det kan være greit å spørre for å sjekke at journalisten har tenkt på
problemstillingen, før en gir et tips.  Og hvis tipset omtales internt
på epost, er det jo grunn til å tro at også intern eposten vil deles
med Microsoft og utenlands etterretning, slik tidligere nevnt, men det
kan hende at det holdes internt i NRKs interne MS Exchange-løsning.
Men Microsoft ønsker å få alle Exchange-kunder over &quot;i skyen&quot; (eller
andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
lenge det i så fall vil vare.&lt;/p&gt;

&lt;p&gt;I tillegg vet en jo at
&lt;a href=&quot;https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196&quot;&gt;NRK
har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
intern og ekstern Internett-trafikk&lt;/a&gt; hos NRK ved oppsett av såkalte
VDI-noder, på tross av
&lt;a href=&quot;https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584&quot;&gt;protester
fra NRKs journalistlag&lt;/a&gt;.  Jeg vet ikke om den vil kunne snappe opp
dokumenter som lagres på interne filtjenere eller dokumenter som lages
i de interne webbaserte publiseringssystemene, men vet at hva noden
ser etter på nettet kontrolleres av NSM og oppdateres automatisk, slik
at det ikke gir så mye mening å sjekke hva noden ser etter i dag når
det kan endres automatisk i morgen.&lt;/p&gt;

&lt;p&gt;Personlig vet jeg ikke om jeg hadde turt tipse NRK hvis jeg satt på
noe som kunne være en trussel mot den bestående makten i Norge eller
verden.  Til det virker det å være for mange åpninger for
utenforstående med andre prioriteter enn NRKs journalistiske fokus.
Og den største truslen for en varsler er jo om metainformasjon kommer
på avveie, dvs. informasjon om at en har vært i kontakt med en
journalist.  Det kan være nok til at en kommer i myndighetenes
søkelys, og de færreste har nok operasjonell sikkerhet til at vil tåle
slik flombelysning på sitt privatliv.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
                <link>https://www.hungry.com/~pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>        
                <guid isPermaLink="true">https://www.hungry.com/~pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
                <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
system&lt;/a&gt; provide a practical and easy way to figure out which
packages support the hardware in a given machine.  The command line
tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
convenient way to list and install packages relevant for the current
hardware during system installation, both user space packages and
firmware packages. The GUI background daemon on the other hand provide
a pop-up proposing to install packages when a new dongle is inserted
while using the computer.  For example, if you plug in a smart card
reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
that package isn&#39;t already installed, and if you plug in a USB video
camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
cheese is currently missing.  This already work just fine.&lt;/p&gt;

&lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
package names.  When I started no such database existed in Debian, so
I made my own data set and included it with the isenkram package and
made isenkram fetch the latest version of this database from git using
http.  This way the isenkram users would get updated package proposals
as soon as I learned more about hardware related packages.&lt;/p&gt;

&lt;p&gt;The hardware is identified using modalias strings.  The modalias
design is from the Linux kernel where most hardware descriptors are
made available as a strings that can be matched using filename style
globbing.  It handle USB, PCI, DMI and a lot of other hardware related
identifiers.&lt;/p&gt;

&lt;p&gt;The downside to the Isenkram specific database is that there is no
information about relevant distribution / Debian version, making
isenkram propose obsolete packages too.  But along came AppStream, a
cross distribution mechanism to store and collect metadata about
software packages.  When I heard about the proposal, I contacted the
people involved and suggested to add a hardware matching rule using
modalias strings in the specification, to be able to use AppStream for
mapping hardware to packages.  This idea was accepted and AppStream is
now a great way for a package to announce the hardware it support in a
distribution neutral way.  I wrote
&lt;a href=&quot;https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
recipe on how to add such meta-information&lt;/a&gt; in a blog post last
December.  If you have a hardware related package in Debian, please
announce the relevant hardware IDs using AppStream.&lt;/p&gt;

&lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
RCX or NXT unit, announce this support using AppStream.  The effect is
that when you insert such LEGO robot controller into your Debian
machine, Isenkram will propose to install the packages needed to get
it working.  The intention is that this should allow the local user to
start programming his robot controller right away without having to
guess what packages to use or which permissions to fix.&lt;/p&gt;

&lt;p&gt;But when I sat down with my son the other day to program our NXT
unit using his Debian Stretch computer, I discovered something
annoying.  The local console user (ie my son) did not get access to
the USB device for programming the unit.  This used to work, but no
longer in Jessie and Stretch.  After some investigation and asking
around on #debian-devel, I discovered that this was because udev had
changed the mechanism used to grant access to local devices.  The
ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
no longer applied, because LDAP users no longer was added to the
plugdev group during login.  Michael Biebl told me that this method
was obsolete and the new method used ACLs instead.  This was good
news, as the plugdev mechanism is a mess when using a remote user
directory like LDAP.  Using ACLs would make sure a user lost device
access when she logged out, even if the user left behind a background
process which would retain the plugdev membership with the ConsoleKit
setup.  Armed with this knowledge I moved on to fix the access problem
for the LEGO Mindstorms related packages.&lt;/p&gt;

&lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;.  It can either be
applied directly for a device, or is applied in
/lib/udev/rules.d/70-uaccess.rules for classes of devices.  As the
LEGO Mindstorms udev rules did not have a class, I decided to add the
tag directly in the udev rules files included in the packages.  Here
is one example.  For the nqc C compiler for the RCX, the
&lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:

&lt;p&gt;&lt;pre&gt;
SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
    SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end.  I suspect all
packages using plugdev in their /lib/udev/rules.d/ files should be
changed to use this tag (either directly or indirectly via
&lt;tt&gt;70-uaccess.rules&lt;/tt&gt;).  Perhaps a lintian check should be created
to detect this?&lt;/p&gt;

&lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
It is unclear to me if the uaccess tag is an internal implementation
detail like the udev-acl tag used by
&lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;.  If it is, I guess the
indirect method is the preferred way.  Michael
&lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
documentation from the systemd project&lt;/a&gt; and I hope it will make
this clearer.  For now I use the generic classes when they exist and
is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
directly if no such class exist.&lt;/p&gt;

&lt;p&gt;To learn more about the isenkram system, please check out
&lt;a href=&quot;https://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To help out making life for LEGO constructors in Debian easier,
please join us on our IRC channel
&lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
LEGO team&lt;/a&gt; in the Alioth project we created yesterday.  A mailing
list is not yet created, but we are working on it. :)&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>