Guess what.. there are tricks to circumvent that

Ingredients

• existing SOCKS proxy reachable on the network
• netcat

As an example I'll describe how to connect with git to a remote repository via netcat through a SOCKS proxy. Git command line client itself doesn't support SOCKS proxies directly. But it does support a proxy command. So we abuse netcat to do the conversion for git.

1.) Step - create a shell script

As git can only handle a proxy command without any parameter we create a small shell script to act as that command:

#!/bin/bash
nc -xproxy.mydomain.com:1080 -X5 $*

Save this as proxy_command.sh and give it execution rights.

Now export an environment variable for GIT to make use of this proxy command:

export GIT_PROXY_COMMAND=/Volumes/Repositories/explain-it-tools/proxy_command.sh

And now you can use git as you would without network restrictions:

git clone git://github.com/altercation/solarized.git

aptitude update .... .... Reading package lists... Done W: GPG error: http://ppa.launchpad.net hardy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 35CC62D2200CBE07

W: You may want to run apt-get update to correct these problems

Die angebotene Lösung mit apt-get update funktioniert leider nicht.

Nach einigen Recherchen habe ich jetzt folgenden Weg gefunden um den fehlenden Schlüssel für aptitude verfügbar zu machen:

Zuerst muss der Schlüssel geholt werden. Das geht mit gpg:

gpg --recv-keys 35CC62D2200CBE07

Dann diesen Schlüssel in eine Datei exportieren:

gpg -a --export 200CBE07 > newsite.key.gpg

Und letztlich aptitude den neuen Schlüssel mitteilen:

apt-key add newsite.key.gpg

Schon funktioniert aptitude update wieder ohne Fehlermeldungen.