pool.sks-keyservers.net and ipv6

Greetings

As of yesterday the main pool.sks-keyservers.net includes AAAA records
for IPv6-enabled SKS keyservers.

This should not affect ordinary working systems, but if it for some
reason someone is operating with a broken IPv6 setup it could cause
delays, for this reason an IPv4 pool is added at
ipv4.pool.sks-keyservers.net for those affected ( according to google's
report Global IPv6 statistics - Measuring the current state of IPv6 for
ordinary users 0.09% of users have broken IPv6 connectivity )

So it shouldn't be many complaints, but consider yourself warned :)
--
----------------------------
Kristian Fiskerstrand
http://www.kfwebs.net
----------------------------
Fabricando fit faber
Practice makes perfect
----------------------------
http://www.secure-my-email.com
http://www.secure-my-internet.com

Encryption Test

Hello! Who would like to practice using OpenPGP with me? I attached my
public key. Respond with your public key and I will send you an
encrypted message. I want to make sure I'm doing it correctly. - Sushi

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Enigmail Encryption Test

Hi Mister Sushi
What can I help?
Give my information and I make it!
Hi Ray

--

-- 
Raimund Macek
E-Mail: raimund.macek <at> ray-undma-ek.net
Homepage: http://www.ray-undma-ek.net

Hello all

Hello,

I`m new at PGP, and trying to know how it works. Tried some times to
send test letters to Adele mail robot, but it replies that I didn`t
signed or encrypted. But I did... welll... at least i tried.

Could someone help me with this problem?

Best regards,
Rain.

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: Hello all

RainmakerLTU wrote the following on 2/2/09 12:37 PM:
> Hello,
> 
> I`m new at PGP, and trying to know how it works. Tried some times to
> send test letters to Adele mail robot, but it replies that I didn`t
> signed or encrypted. But I did... welll... at least i tried.
> 
> Could someone help me with this problem?
> 
> Best regards,
> Rain.

Rainmaker,

the message you posted to this list was signed, and its signature verifies:

OpenPGP Security Info
Good signature from RainmakerLTU (GSF pass) <rainmakerltu <at> gmail.com>
Key ID: 0x0BAED577 / Signed on: 2/2/09 12:37 PM
Key fingerprint: 3DE6 0565 951F C502 E44A 6779 9F1C D66E 0BAE D577

Furthermore you are using:
Version: GnuPG v1.4.9 (MingW32)
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
X-Enigmail-Version: 0.95.7

Everything seems to be OK.

About the Adele mail robot, I can't help, sorry.

ty

Yeah, thank you, everything seems OK to me too... at last the robot
correctly identified encrypted mail from me.

Rain.

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: Building Enigmail for TB comm-central: static or shared, libxul or not?

Michael J Gruber wrote:
> Patrick Brunschwig venit, vidit, dixit 26.01.2009 14:56:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Michael J Gruber wrote:
>>> Ludwig Hügelschäfer venit, vidit, dixit 01/23/09 20:42:
>>>> Hi,
>>>>
>>>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>>>> Hi there,
>>>>>
>>>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>>>> can't used binary Enigmail xpi either).
>>>>>
>>>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>>>
>>>>> For building Enigmail (from cvs),
>>>> Are you using enigmail trunk (aka 0.96a)?
>>> Yes, that's what I meant by cvs, sorry. A current cvs checkout from
>>> trunk.
>>>
>>>>> I've been following the instructions
>>>>> on the Enigmail website and ended up with the attached error which
>>>>> seems
>>>>> to be related to a conflict in build options (shared/static).
>>>>>
>>>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>>>> because d.m.o. says TB can't be built shared with libxul (and also

Re: Building Enigmail for TB comm-central: static or shared, libxul or not?

David Ward venit, vidit, dixit 03.02.2009 09:59:
> Michael J Gruber wrote:
>> Patrick Brunschwig venit, vidit, dixit 26.01.2009 14:56:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>> Michael J Gruber wrote:
>>>> Ludwig Hügelschäfer venit, vidit, dixit 01/23/09 20:42:
>>>>> Hi,
>>>>>
>>>>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>>>>> Hi there,
>>>>>>
>>>>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>>>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>>>>> can't used binary Enigmail xpi either).
>>>>>>
>>>>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>>>>
>>>>>> For building Enigmail (from cvs),
>>>>> Are you using enigmail trunk (aka 0.96a)?
>>>> Yes, that's what I meant by cvs, sorry. A current cvs checkout from
>>>> trunk.
>>>>
>>>>>> I've been following the instructions
>>>>>> on the Enigmail website and ended up with the attached error which
>>>>>> seems
>>>>>> to be related to a conflict in build options (shared/static).
>>>>>>
>>>>>> I've built TB with "ac_add_options --enable-static --disable-libxul"

Re: Building Enigmail for TB comm-central: static or shared, libxul or not?

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: Building Enigmail for TB comm-central: static or shared, libxul or not?

Michael J Gruber wrote:
> I'm still not sure whether the culprit is Thunderbird's (even though
> it builds and runs) or Enigmail's build process.

We understand that some people (distro maintainers, mostly) need to be
looking to the future and getting a 64-bit toolchain and release ready.
 These people should feel free to contact the Enigmail team off-list.
Tell us as precisely as possible about your current build environment,
including at the very least:

	* Base Thunderbird version
	* All diffs and patches to the base Tbird
	* Enigmail version being built
	* All diffs and patches to the base Enigmail
	* Toolchain used (autoconf, automake, libtool,
	  GNU Make, gcc, ld, libc, libstdc++)

We will provide as much guidance as we can for how to prepare for
Thunderbird 3.  However, due to the limited amount of time we have, we
can really only help distro maintainers and significant third-party
developers (PortableApps, etc.).

Everyone else should wait for Thunderbird 3 to be officially released.
If you want to try and compile Enigmail for 64-bit betas of Thunderbird
3, well... we wish you a lot of luck.  If it works, great.  If it
doesn't, we hope you're able to fix it.