Generated.

[homepage.git] / blog / data / 2016-04-02-trusted-timestamping-syslog.txt

diff --git a/blog/data/2016-04-02-trusted-timestamping-syslog.txt b/blog/data/2016-04-02-trusted-timestamping-syslog.txt
index fe1a8d117ae923b0e83dcad48387c1310ecd25f2..3d47fcb302523ca4595ba6a51e8626b826ee3c77 100644 (file)
--- a/blog/data/2016-04-02-trusted-timestamping-syslog.txt
+++ b/blog/data/2016-04-02-trusted-timestamping-syslog.txt
@@ -3,13 +3,13 @@ Tags: english, sikkerhet
 Date: 2016-04-02 09:50
 
 <p>Two years ago, I had
-<a href="http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html">a
+<a href="http://www.hungry.com/~pere/blog/Public_Trusted_Timestamping_services_for_everyone.html">a
 look at trusted timestamping options available</a>, and among
 other things noted a still open
 <a href="https://bugs.debian.org/742553">bug in the tsget script</a>
 included in openssl that made it harder than necessary to use openssl
 as a trusted timestamping client.  A few days ago I was told
-<a href="https::/www.difi.no/">the Norwegian government office DIFI</a> is
+<a href="https:/www.difi.no/">the Norwegian government office DIFI</a> is
 close to releasing their own trusted timestamp service, and in the
 process I was happy to learn about a replacement for the tsget script
 using only curl:</p>