In order to determine how trustworthy a digital signature of a file is, you need to grab the file, the digital signature, and you will need to import the user’s public key. This wikipedia fragment describes what is meant by a “trustworthy signature” in terms of the Web of Trust.
This is the command I run to determine the level of trust of my signed foaf file.
gpg --verify --no-tty --status-fd 2 --command-fd 0 foaf.rdf.asc foaf.rdf<br />
Which results in the folowing output :
gpg: Signature made Wed 3 Jun 23:19:52 2009 BST using RSA key ID 51F2F7EF<br />
[GNUPG:] SIG_ID foL1PiWCT+546VnE17UG2QvWJeE 2009-06-03 1244067592<br />
[GNUPG:] GOODSIG 9ED0B04E51F2F7EF Mischa Tuffield ([email protected]) <[email protected]><br />
gpg: Good signature from "Mischa Tuffield ([email protected]) <[email protected]>"<br />
gpg: aka "Mischa Tuffield (http://id.ecs.soton.ac.uk/person/6914) <[email protected]>"<br />
[GNUPG:] VALIDSIG 18A2AF280CA59E77AE512BB39ED0B04E51F2F7EF 2009-06-03 1244067592 0 4 0 1 2 00 18A2AF280CA59E77AE512BB39ED0B04E51F2F7EF<br />
[GNUPG:] TRUST_ULTIMATE<br />
This is an automatic way of evaluating how trust worthy statement at the end of a URI are.
I had one of my hard-drives fail miserably a couple of weeks ago, and have only now recovered all of my blog content from Google’s and Yahoo’s caches. I have recreated all of the content, and have set up a cronjob to backup my sql tables, I had copies of most of the important stuff on my machine, and only lost my sql tables … d’oh….
I have set the following 301 redirects from all of the old URLs, I don’t think I have missed any out. Do shout if you find any old broken URLs on my site.
redirect 301 /blog/2009/04/02/barcamp-09/ /blog/2009/07/07/barcamp-09/<br />
redirect 301 /blog/2009/03/24/time-machine-to-a-linux-box/ /blog/2009/07/07/timemachine-to-a-linux-box/<br />
redirect 301 /blog/2009/03/23/signing-a-public-key/ /blog/2009/07/08/signing-someone’s-public-key/<br />
redirect 301 /blog/2009/03/20/making-foaf-useful/ /blog/2009/07/08/making-foaf-useful/<br />
redirect 301 /blog/2009/03/19/yum_64bit_binaries/ /blog/2009/07/07/configuring-yum-to-only-install-64bit-binaries/<br />
redirect 301 /blog/2009/03/19/webdav_webid/ /blog/2009/07/08/enabling-a-writable-webid-with-webdav/<br />
redirect 301 /blog/2009/03/18/foafwot/ /blog/2009/07/08/enabling-trust-in-a-foaf-document/<br />
redirect 301 /blog/2009/03/17/signingverifyinggpg/ /blog/2009/07/08/signing-and-verifying-documents-using-gnupg/<br />
redirect 301 /blog/2009/02/05/ah-good-work-tobyink/ /blog/2009/07/07/ah-good-work-tobyink-…/<br />
redirect 301 /blog/2009/01/28/duplicate-dylib-libiconv2/ /blog/2009/07/07/duplicate-dylib-libiconv-2-dylib/<br />
redirect 301 /blog/2008/12/31/ld-duplicate-symbol-mac-osx/ /blog/2009/07/07/ld-duplicate-symbol-_g_bit_nth_lsf-mac-osx-leoparddarwin/<br />
I have used Jules blog post to have a go at iPhone tethering and it seems to work fine. Make sure that if you attempt to tether you should use Jules’s update’d howto on 2009-06-18. All you have to do is point your iPhone at the following url http://www.jules.fm/files/uk.o2.mobileconfig and you can follow the instruction on how to run it here http://richardlai.xanga.com/704930537/enable-tethering-on-iphone-30—too-easy-worldwide-carriers/