alex@brithombar:~$ finger tolimar@db.debian.org
[db.debian.org]
uid=tolimar,ou=users,dc=debian,dc=org
First name: Alexander
Last name: Reichle-Schmehl
Email: Alexander Reichle-Schmehl
URL: http://www.schmehl.info/
IRC nickname: Tolimar
Jabber ID: tolimar@jabber.ccc.de
Fingerprint: 46CD D292 0692 D5A2 8F81 2E48 0717 74E0 00D8 CD16
Key block: finger tolimar/key@db.debian.org

alex@brithombar$ gpg --edit-key 00D8CD16
Secret key is available.

pub  1024D/00D8CD16  created: 2002-09-28  expires: never       usage: SC
             trust: ultimate      validity: ultimate
sub  1024g/C5F3F285  created: 2002-09-28  expires: never       usage: E
[ultimate] (1). Alexander Schmehl (university) <schmehl@cs.uni-frankfurt.de>
[ultimate] (2) Alexander Schmehl (privat) <alexander@schmehl.info>
[ultimate] (3) Alexander Schmehl (university) <schmehl@informatik.uni-frankfurt.de>
[ultimate] (4) Alexander Schmehl <tolimar@debian.org>
[ revoked] (5) Alexander Schmehl < deleted >
[ultimate] (6) Alexander Schmehl <schmehl@uni-hildesheim.de>
Please note that the shown key validity is not necessarily correct
unless you restart the program.

Command> adduid
Real name: Alexander Reichle-Schmehl
Email address: tolimar@debian.org
Comment:
You selected this USER-ID:
    "Alexander Reichle-Schmehl "

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o

You need a passphrase to unlock the secret key for
user: "Alexander Schmehl (university) "
1024-bit DSA key, ID 00D8CD16, created 2002-09-28


pub  1024D/00D8CD16  created: 2002-09-28  expires: never       usage: SC
             trust: ultimate      validity: ultimate
sub  1024g/C5F3F285  created: 2002-09-28  expires: never       usage: E
[ultimate] (1). Alexander Schmehl (university) <schmehl@cs.uni-frankfurt.de>
[ultimate] (2) Alexander Schmehl (privat) <alexander@schmehl.info>
[ultimate] (3) Alexander Schmehl (university) <schmehl@informatik.uni-frankfurt.de>
[ultimate] (4) Alexander Schmehl <tolimar@debian.org>
[ revoked] (5) Alexander Schmehl < deleted >
[ultimate] (6) Alexander Schmehl <schmehl@uni-hildesheim.de>
[ultimate] (7) Alexander Reichle-Schmehl <tolimar@debian.org>

Command> save

alex@brithombar$ gpg --send-key 00D8CD16
gpg: sending key 00D8CD16 to hkp server keyserver.noreply.org

http://blog.schmehl.info/Debian/opensourcecensus Thu, 24 Apr 2008 23:20:00 +0100 Alexander Schmehl (alexander@schmehl.info) /Debian http://blog.schmehl.info/Debian/opensourcecensus Meike wonders about Open Source Census and their 45 MB tarball (and several other strange things).

The good news is: There is a 270KB ruby thingy which seems to do the same, and even while marked as Expert User Only it seems to run just fine... I think; I lost patience after it scanned my /home for 6 minutes, and I didn't found a possibility to tell it not to scan my /home (which I don't wont him to scan) or /srv (which just contains a lot of files where it won't find anything usefull).

BTW: While we are at complaining at them: Please make the system so, that I don't need to register to send you my data. Thanks. http://blog.schmehl.info/Debian/planet-and-dpn Sun, 20 Apr 2008 14:14:00 +0100 Alexander Schmehl (alexander@schmehl.info) /Debian http://blog.schmehl.info/Debian/planet-and-dpn Jörg Jaspert wonders, if planet.debian.org should be available as a mailing list, too. That's a proposal to solve the problem, that planet has been used by more or less official announcement and discussions, but not all people have time / want to read planet.

An other solution would be to make sure, that important blog posts are mention in the next issue of the Debian Project News (which have just been started and could still need some help). http://blog.schmehl.info/Debian/bsp-1 Sun, 06 Apr 2008 01:48:00 +0100 Alexander Schmehl (alexander@schmehl.info) /Debian http://blog.schmehl.info/Debian/bsp-1 deciding to go on a diet the day before you are invited to a all you can eat pasta & co restaurant. http://blog.schmehl.info/bsp-1 Sat, 05 Apr 2008 23:21:00 +0100 Alexander Schmehl (alexander@schmehl.info) http://blog.schmehl.info/bsp-1 deciding to on a died the day before you are invited to a all you can eat paste & co restaurant. http://blog.schmehl.info/home-alone Fri, 22 Feb 2008 18:54:00 +0100 Alexander Schmehl (alexander@schmehl.info) http://blog.schmehl.info/home-alone I'm wondering...

$ find debian/uploads/ -iname \*.changes -mtime -10|wc -l
22

Maybe it isn't that bad, if your girlfriend leaves you for some days alone at home?

PS: Of course it is... but you get some work done. http://blog.schmehl.info/Debian/home-alone Fri, 22 Feb 2008 18:54:00 +0100 Alexander Schmehl (alexander@schmehl.info) /Debian http://blog.schmehl.info/Debian/home-alone I'm wondering...

$ find debian/uploads/ -iname \*.changes -mtime -10|wc -l
22

Maybe it isn't that bad, if your girlfriend leaves you for some days alone at home?

PS: Of course it is... but you get some work done. http://blog.schmehl.info/Debian/apache-basic-auth-location-match Thu, 10 Jan 2008 22:43:00 +0100 Alexander Schmehl (alexander@schmehl.info) /Debian http://blog.schmehl.info/Debian/apache-basic-auth-location-match The other day, I had an interesting problem, regarding Apache, the LocationMatch directive and regular expressions. I'll put it here, so I'll be able to find it again...

Actually it was a quite simple problem: A simple web page, where all web pages are protected with a password. No big Problem: Use a <location /> and AuthType basic, problem solved.... or isn't it?

Some documents might be needed to be available without the authentication... for example robots.txt... or the funky custom error document, which explains how to get the authentication data, in case the authentication fails.

Looking at the documentation, found a solution: LocationMatch exists, where you specify a regular expression, which must match, for the following configuration to apply.

What isn't mentioned in the documentation, that the obvious solution... something like <LocationMatch !"^/(robots.txt|my401handler.html"> doesn't work. See apache bug 10932. Needed quite some time, to find this out...

Luckily Meike found the bug report above, which has a workaround for that problem: Use <LocationMatch "^/(?!robots.txt|my401handler.html)">