Sorry, this entry is only available in Deutsch.

Continue reading →

I recently set up a file storage with the purpose of being super safe.
Here is what one needs to do and why:
Continue reading →

I recently decided against building my own server from ordered parts and simply bought an older Mac Pro for a good value. It was roughly 200€ more than the build-it-yourself way, but therefor it can run OS X smoothly, which saves me time where I don’t need to babysit my machine.

Nevertheless, it can not go without a bit of hacking.
read on how to upgrade to 5.1 and run Apple’s Hardware Tests from an USB Stick

The behavior of the delete button changed in iOS 7: It no longer archives gmails but moves them to trash.
see how to restore the old behavior

In xtend everything is an expression. Thus you can pass a method to another method as a parameter in the following way:
Continue reading →

I (re-)created gpg-keys.
Here my recommended steps:
1. First create one or more keys:
There are many tutorials, I recommend the one mentioned in my last post:
http://patrick.mukherjee.de/?p=151

2. List all keys:
gpg –list-secret-keys

now save each:
2. export the public-key as a text-file. This can be distributed without being afraid of mail-filtern, etc.:
gpg -ao pubKey_.asc –export
where stands for either the short-ID of the key or the associated email-addresse.

3. The most important step: create a “revokation certificate”! So that you can revocate your published key at any time (maybe you forget the passphrase). This is only possible using the passphrase and the private key!
gpg -ao revokeCert_.asc –gen-revoke

4. Optionally save the private key in a ASCCII-file. The file is, of cause, encrypted using a passphrase. Store it very secure (you can even print it).
gpg -a –export-secret-keys | gpg -aco privKey_.asc

5. Now publish your key(s) to a key-server. It is sufficient to publish it to one server – the server distributes it to all other server.
gpg –send-keys

… while trying around I made a mistake and deleted my key prior revoking the key. Now the wrongly published keys are stored online for all eternety and will confuse people, who look for my key.
So, please, do not use these keys, as they do not exist anymore:

2048R/C80A87DF
2048R/3BD998A9

http://www.robertsosinski.com/2008/02/18/working-with-pgp-and-mac-os-x/

Old, but still valid. Though now there is a GUI (in the installer https://www.gpgtools.org/installer/index.html) this command line tutorial explains the basics nice 🙂

18 days ago I started this blog. Today Google notified me that my Blog has been crawled and can be found via a google search. Without any action on my side to be registered.
Well, they did not exactly notified my, but I got informed by monitoring the usage of my name in the web.
This can be done using http://www.google.com/alerts, which I can highly recommend!

The first comments in my blog turned out to be SPAM. But identifying it is not that easy as a google search does not show many hits.
For everybody who is unsure I created this post: Here I will list all SPAM comments I receive. Please feel free to add you own SPAM findings in the comments. I never thought I would say that … so, permission granted, but only for this post!

So: go SPAM and enjoy your meal 😉

EDIT: I changed my mind … only a month after this post and I got 58 SPAM comments! I will install a SPAM sorting plugin …
However, here are not the single messages, but instead the pattern I encountered:

(click to see the SPAM comments’ pattern)