-<p>After this, the machine had internet connectivity, and I could
-upgrade it and install the sysvinit packages from experimental and
-enable it as the default boot system in Hurd.</p>
-
-<p>But before I did that, I set a password on the root user, as ssh is
-running on the machine it for ssh login to work a password need to be
-set. Also, note that a bug somewhere in openssh on Hurd block
-compression from working. Remember to turn that off on the client
-side.</p>
-
-<p>Run these commands as root to upgrade and test the new sysvinit
-stuff:</p>
-
-<p><blockquote><pre>
-cat > /etc/apt/sources.list.d/experimental.list <<EOF
-deb http://http.debian.net/debian/ experimental main
-EOF
-apt-get update
-apt-get dist-upgrade
-apt-get install -t experimental initscripts sysv-rc sysvinit \
- sysvinit-core sysvinit-utils
-update-alternatives --config runsystem
-</pre></blockquote></p>
-
-<p>To reboot after switching boot system, you have to use
-<tt>reboot-hurd</tt> instead of just <tt>reboot</tt>, as there is not
-yet a sysvinit process able to receive the signals from the normal
-'reboot' command. After switching to sysvinit as the boot system,
-upgrading every package and rebooting, the network come up with DHCP
-after boot as it should, and the settrans/pkill hack mentioned at the
-start is no longer needed. But for some strange reason, there are no
-longer any login prompt in the virtual console, so I logged in using
-ssh instead.
-
-<p>Note that there are some race conditions in Hurd making the boot
-fail some times. No idea what the cause is, but hope the Hurd porters
-figure it out. At least Justus said on IRC (#debian-hurd on
-irc.debian.org) that they are aware of the problem. A way to reduce
-the impact is to upgrade to the Hurd packages built by Justus by
-adding this repository to the machine:</p>
-
-<p><blockquote><pre>
-cat > /etc/apt/sources.list.d/hurd-ci.list <<EOF
-deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
-EOF
-</pre></blockquote></p>
-
-<p>At the moment the prebuilt virtual machine get some packages from
-http://ftp.debian-ports.org/debian, because some of the packages in
-unstable do not yet include the required patches that are lingering in
-BTS. This is the completely list of "unofficial" packages installed:</p>
-
-<p><blockquote><pre>
-# aptitude search '?narrow(?version(CURRENT),?origin(Debian Ports))'
-i emacs - GNU Emacs editor (metapackage)
-i gdb - GNU Debugger
-i hurd-recommended - Miscellaneous translators
-i isc-dhcp-client - ISC DHCP client
-i isc-dhcp-common - common files used by all the isc-dhcp* packages
-i libc-bin - Embedded GNU C Library: Binaries
-i libc-dev-bin - Embedded GNU C Library: Development binaries
-i libc0.3 - Embedded GNU C Library: Shared libraries
-i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
-i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
-i multiarch-support - Transitional package to ensure multiarch compatibilit
-i A x11-common - X Window System (X.Org) infrastructure
-i xorg - X.Org X Window System
-i A xserver-xorg - X.Org X server
-i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
-#
-</pre></blockquote></p>
-
-<p>All in all, testing hurd has been an interesting experience. :)
-X.org did not work out of the box and I never took the time to follow
-the porters instructions to fix it. This time I was interested in the
-command line stuff.<p>
-</div>
- <div class="tags">
-
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
-
-
- </div>
- </div>
- <div class="padding"></div>
-
- <div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_fist_full_of_non_anonymous_Bitcoins.html">A fist full of non-anonymous Bitcoins</a></div>
- <div class="date">29th January 2014</div>
- <div class="body"><p>Bitcoin is a incredible use of peer to peer communication and
-encryption, allowing direct and immediate money transfer without any
-central control. It is sometimes claimed to be ideal for illegal
-activity, which I believe is quite a long way from the truth. At least
-I would not conduct illegal money transfers using a system where the
-details of every transaction are kept forever. This point is
-investigated in
-<a href="https://www.usenix.org/publications/login">USENIX ;login:</a>
-from December 2013, in the article
-"<a href="https://www.usenix.org/system/files/login/articles/03_meiklejohn-online.pdf">A
-Fistful of Bitcoins - Characterizing Payments Among Men with No
-Names</a>" by Sarah Meiklejohn, Marjori Pomarole,Grant Jordan, Kirill
-Levchenko, Damon McCoy, Geoffrey M. Voelker, and Stefan Savage. They
-analyse the transaction log in the Bitcoin system, using it to find
-addresses belong to individuals and organisations and follow the flow
-of money from both Bitcoin theft and trades on Silk Road to where the
-money end up. This is how they wrap up their article:</p>
-
-<p><blockquote>
-<p>"To demonstrate the usefulness of this type of analysis, we turned
-our attention to criminal activity. In the Bitcoin economy, criminal
-activity can appear in a number of forms, such as dealing drugs on
-Silk Road or simply stealing someone else’s bitcoins. We followed the
-flow of bitcoins out of Silk Road (in particular, from one notorious
-address) and from a number of highly publicized thefts to see whether
-we could track the bitcoins to known services. Although some of the
-thieves attempted to use sophisticated mixing techniques (or possibly
-mix services) to obscure the flow of bitcoins, for the most part
-tracking the bitcoins was quite straightforward, and we ultimately saw
-large quantities of bitcoins flow to a variety of exchanges directly
-from the point of theft (or the withdrawal from Silk Road).</p>
-
-<p>As acknowledged above, following stolen bitcoins to the point at
-which they are deposited into an exchange does not in itself identify
-the thief; however, it does enable further de-anonymization in the
-case in which certain agencies can determine (through, for example,
-subpoena power) the real-world owner of the account into which the
-stolen bitcoins were deposited. Because such exchanges seem to serve
-as chokepoints into and out of the Bitcoin economy (i.e., there are
-few alternative ways to cash out), we conclude that using Bitcoin for
-money laundering or other illicit purposes does not (at least at
-present) seem to be particularly attractive."</p>
-</blockquote><p>
-
-<p>These researches are not the first to analyse the Bitcoin
-transaction log. The 2011 paper
-"<a href="http://arxiv.org/abs/1107.4524">An Analysis of Anonymity in
-the Bitcoin System</A>" by Fergal Reid and Martin Harrigan is
-summarized like this:</p>
-
-<p><blockquote>
-"Anonymity in Bitcoin, a peer-to-peer electronic currency system, is a
-complicated issue. Within the system, users are identified by
-public-keys only. An attacker wishing to de-anonymize its users will
-attempt to construct the one-to-many mapping between users and
-public-keys and associate information external to the system with the
-users. Bitcoin tries to prevent this attack by storing the mapping of
-a user to his or her public-keys on that user's node only and by
-allowing each user to generate as many public-keys as required. In
-this chapter we consider the topological structure of two networks
-derived from Bitcoin's public transaction history. We show that the
-two networks have a non-trivial topological structure, provide
-complementary views of the Bitcoin system and have implications for
-anonymity. We combine these structures with external information and
-techniques such as context discovery and flow analysis to investigate
-an alleged theft of Bitcoins, which, at the time of the theft, had a
-market value of approximately half a million U.S. dollars."
-</blockquote></p>
-
-<p>I hope these references can help kill the urban myth that Bitcoin
-is anonymous. It isn't really a good fit for illegal activites. Use
-cash if you need to stay anonymous, at least until regular DNA
-sampling of notes and coins become the norm. :)</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+<p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
+one option, while the user need to choose which file (mappe) to use
+among the two created by the API tester. The <tt>archive-pdf</tt>
+tool can be found in the git repository for the API tester.</p>
+
+<p>In the project, I have been mostly working on
+<a href="https://github.com/petterreinholdtsen/noark5-tester">the API
+tester</a> so far, while getting to know the code base. The API
+tester currently use
+<a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
+to traverse the entire exposed service API and verify that the exposed
+operations and objects match the specification, as well as trying to
+create objects holding metadata and uploading a simple XML file to
+store. The tester has proved very useful for finding flaws in our
+implementation, as well as flaws in the reference site and the
+specification.</p>
+
+<p>The test document I uploaded is a summary of all the specification
+defects we have collected so far while implementing the web service.
+There are several unclear and conflicting parts of the specification,
+and we have
+<a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
+writing down</a> the questions we get from implementing it. We use a
+format inspired by how <a href="http://www.opengroup.org/austin/">The
+Austin Group</a> collect defect reports for the POSIX standard with
+<a href="http://www.opengroup.org/austin/mantis.html">their
+instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
+
+<p>The Nikita project is implemented using Java and Spring, and is
+fairly easy to get up and running using Docker containers for those
+that want to test the current code base. The API tester is
+implemented in Python.</p>
projects / homepage.git / blobdiff