Faramir wrote:
> El 12-04-2012 20:29, John Clizbe escribió:
> ...
>
>>> pool.sks-keyservers.net adds them to its own list. So really,
>>> that's the only address you need. :)
>
>> It's best to stick with the pool address, otherwise if you select a
>> single server, you'll run into trouble if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
How can we use private IPs ?
>OK, here's my list of addresses:
>192.168.1.2booboo # Windows 2003 Svr[*]
>192.168.1.4yogi# Slackware Linux
>192.168.1.5picnic # Slackware Linux
>192.168.1.18 basket # MacOS X
>192.168.1.19 horse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/04/12 22:47, Michael Talbot-Wilson wrote:
> On Mon, 16 Apr 2012, Robert J. Hansen wrote:
>
>> On 4/16/2012 12:12 AM, Michael Talbot-Wilson wrote:
>>> Found nothing in the FAQ on this.
>>
>> First, it's an entirely expected thing. It's not a pro
On Thu, 19 Apr 2012 11:56, peter.c.dietr...@freenet.de said:
> I use gpg on Windows XP Sp3 via gpg4win 2.1.1-svn1694.
I don't know this version. The last released one is 2.1.0. Meanwhile
we switched to git and thus the svn prefix does not make sense anymore.
Please test with the 2.1.0.
Salam-
On Mon, 23 Apr 2012 16:34:16 +0200, Werner Koch wrote:
On Thu, 19 Apr 2012 11:56, peter.c.dietr...@freenet.de said:
I use gpg on Windows XP Sp3 via gpg4win 2.1.1-svn1694.
I don't know this version. The last released one is 2.1.0. Meanwhile
we switched to git and thus the svn prefix does n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.04.2012 12:23, Mustrum wrote:
> How can we use private IPs ?
>
>
>> OK, here's my list of addresses: 192.168.1.2 booboo # Windows
>> 2003 Svr[*] 192.168.1.4 yogi# Slackware Linux 192.168.1.5 picnic
>> # Slackware Linux 192.168.1.1
Mustrum wrote:
> How can we use private IPs ?
>
See below.
>
>>OK, here's my list of addresses:
>>192.168.1.2 booboo # Windows 2003 Svr[*]
>>192.168.1.4 yogi# Slackware Linux
>>192.168.1.5 picnic # Slackware Linux
>>192.168.1.18 basket # MacOS X
>>192.168.1.19 horse # Solaris 10
>
