From olav at mozilla-enigmail.org  Sun Mar  1 06:00:39 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Sun, 01 Mar 2009 15:00:39 +0100
Subject: [Enigmail] Configuring Enigmail, testing with Adele
In-Reply-To: <49A86A66.4050200@gmail.com>
References: <306359.55974.qm@web51406.mail.re2.yahoo.com>
	<49A86A66.4050200@gmail.com>
Message-ID: <49AA9507.60805@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Jonas, hi Crow,

>> attempting to verify correct configuration with adele-en at gnupp.de.
>> It replies "I could not find a public key that matches your email address"
>> I have published my public key to a keyserver, and the public key is inline
>> with the email.
>
> I had the same problem when I tried to send my key in an encrypted
> message. I solved it by first sending a signed, unencrypted message with
> my key attached, and then a signed encrypted message.

Adele does not recursively decrypt/verify messages. If would have to decrypt
and then import the key from the resulting cleartext which it doesn't.

You can work around that by
1) first sending your key unencryptedly and then test encrypted mail
2) attach your key unencryptedly instead of pasting it inline
3) use PGP/MIME

>>  How do I ensure that Enigmail is configured correctly?

You sent an email to the mailing list instead of the robot. This is the best
way to achieve a solution quickly. However, your post was not even signed.

Please retry sending a signed email to the list, optionally with your public
key attached. You may test encrypted mails with me (NOT to the list!).

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkmqlQQACgkQL/NBt8fdKe1W+wCfXDib1MC+/0AELti5WzMa2Ino
njcAn290pvZi6azNjxFf7cUr9F1eazIO
=Ubkr
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Tue Mar  3 17:57:07 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Tue, 03 Mar 2009 20:57:07 -0500
Subject: [Enigmail] From offlist
Message-ID: <49ADDFF3.7040500@sixdemonbag.org>

David D-- contacted me off-list with a question.  He doesn't want to
post on the list for reasons known only to him.  This is his question,
with his email address and last name stripped, reposted with his permission.

My response will be following separately.

=====

I'm looking to start encrypting my emails, but I'm not sure whether to
use SSL or Gnu Private Guard (through Enigmal with Thunderbird). I'm
definitely not an expert on this, but am I right in understanding that
with SSL (using a server from trustmail or swissmail) you can send an
email to anyone whether they have a key or not, but with Enigmal the
recipient has to have a key for the email to be encrypted? Using SSL is
the email only encrypted up to the server where it is deciphered and
then passed onto the recipient? If this is the case it seems that using
Enigmail is more secure, but how would you send an encrypted email to
someone whose public key is not on any directory?

From rjh at sixdemonbag.org  Tue Mar  3 18:14:44 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Tue, 03 Mar 2009 21:14:44 -0500
Subject: [Enigmail] From offlist
In-Reply-To: <49ADDFF3.7040500@sixdemonbag.org>
References: <49ADDFF3.7040500@sixdemonbag.org>
Message-ID: <49ADE414.2000902@sixdemonbag.org>

Robert J. Hansen wrote:
> David D-- contacted me off-list with a question.  He doesn't want to 
> post on the list for reasons known only to him.  This is his
> question, with his email address and last name stripped, reposted
> with his permission.

<reaches for the list moderator hat>

We generally prefer these questions to be posted to the list instead of
to themselves personally.  The reasons are both technical and cultural.

The technical reason is that other people may have this same question.
If this question is asked on-list and answers are posted on-list, then
Google can index them and future users can just Google instead of asking
us.  Taking questions to the list, instead of to private email, is a
kindness to future users.  We heartily recommend it for that reason.

The second technical reason is the list serves as a load balancer.  If
you throw the question on the list, then any of half-a-dozen very
knowledgeable people will speak up and give an answer.  Other people who
don't speak up as much but who have run into your problem before may
throw their two cents in, too.  But if people just look for someone who
posts a lot of answers and then email that person off-list, that person
will soon find themselves drowned; there's no load balancing.

Finally, the cultural reason is that we have generally decided this is
the forum we'd like to use to talk about Enigmail.  We try to keep a
pretty friendly list and we encourage people to make use of it.  If
people are just going to email us off-list, then why bother with the
list at all?

If you have a very real need for privacy (and I've seen no evidence to
think David D-- doesn't), then sure, email us off-list.  We'll try to
help.  But most questions belong on the list unless there's a very real
need otherwise.

<removes hat>


David D-- wrote:
> I'm looking to start encrypting my emails, but I'm not sure whether
> to use SSL or Gnu Private Guard (through Enigmal with Thunderbird).
> I'm definitely not an expert on this, but am I right in understanding
> that with SSL (using a server from trustmail or swissmail) you can
> send an email to anyone whether they have a key or not, but with
> Enigmal the recipient has to have a key for the email to be
> encrypted?

SSL and GnuPG provide two very different sets of capabilities.  They're
really apples and oranges.  SSL will protect your email when you're
sending your email to your email server.  However, once it leaves your
email server it's in cleartext.  It travels the internet in cleartext,
it arrives at your recipient's server in cleartext, it's put in your
recipient's mailbox in cleartext.

For some people, this is enough.  Other people want an end-to-end
encryption channel.  GnuPG provides that.

You're correct in that SSL doesn't require you to have your recipient's
public key and GnuPG does.

> If this is the case it seems that using Enigmail is more secure, but
> how would you send an encrypted email to someone whose public key is
> not on any directory?

You send them an email and ask for their key.  They email it back to
you, and you import it to your local keyring.  It's possible for a
malicious attacker to have replaced the public key your correspondent
sent you with a public key of the attacker's choosing, though -- what we
call a Man In The Middle attack -- so it's important to verify that you
received the correct key.  The usual way to do this is to contact your
friend by some method other than email and ask them for a fingerprint of
their key.  If the fingerprint they give you matches the one you find by
looking at your copy of their key, then you have the correct key.


From alaric at metrocast.net  Tue Mar  3 18:26:40 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Tue, 03 Mar 2009 21:26:40 -0500
Subject: [Enigmail] From offlist
In-Reply-To: <49ADE414.2000902@sixdemonbag.org>
References: <49ADDFF3.7040500@sixdemonbag.org>
	<49ADE414.2000902@sixdemonbag.org>
Message-ID: <49ADE6E0.7010405@metrocast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Robert J. Hansen wrote:
> You send them an email and ask for their key.  They email it back to
> you, and you import it to your local keyring.  It's possible for a
> malicious attacker to have replaced the public key your correspondent
> sent you with a public key of the attacker's choosing, though -- what we
> call a Man In The Middle attack -- so it's important to verify that you
> received the correct key.  The usual way to do this is to contact your
> friend by some method other than email and ask them for a fingerprint of
> their key.  If the fingerprint they give you matches the one you find by
> looking at your copy of their key, then you have the correct key.

Barring, of course, the extremely unlikely case of fingerprint
collisions, by chance or design.  If you're being attacked by someone
with enough savvy and processing power to engineer a by-design key
fingerprint collision more or less in real time, the odds are you're
already completely screwed anyway, so there's relatively little point in
worrying about it.


- --
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric at caerllewys.net   alaric at metrocast.net   phil at co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkmt5uAACgkQ0DfOju+hMkk/cACfR2XGhI5Ci+R2CVHHVS110RlD
SkEAn18f1ME0OXvrOqrSaLSdcudtYUiN
=ou+4
-----END PGP SIGNATURE-----

From faramir.cl at gmail.com  Tue Mar  3 20:32:33 2009
From: faramir.cl at gmail.com (Faramir)
Date: Wed, 04 Mar 2009 01:32:33 -0300
Subject: [Enigmail] From offlist
In-Reply-To: <49ADE414.2000902@sixdemonbag.org>
References: <49ADDFF3.7040500@sixdemonbag.org>
	<49ADE414.2000902@sixdemonbag.org>
Message-ID: <49AE0461.9040904@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Robert J. Hansen escribi?:

> SSL and GnuPG provide two very different sets of capabilities.  They're
> really apples and oranges.  SSL will protect your email when you're
> sending your email to your email server.  However, once it leaves your
> email server it's in cleartext.  It travels the internet in cleartext,
> it arrives at your recipient's server in cleartext, it's put in your
> recipient's mailbox in cleartext.

  Maybe he was confusing SSL with S/MIME, after all, both use x.509
certificates...

  Best Regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJJrgRhAAoJEMV4f6PvczxAUCYH+QHm1lezv0qYGQg1tzaqnuo4
K4w8pQrftTFcCtBddFwQONUtymR7WnTELmQlU8CJa1iGREqAsAqKF/+oywD1Jhms
TxqecAHR3V8kb/kvMJIR2W/Gs7QjUESOntBboYN6EDeBSRGHskKwVMtaj5odXXYd
g4icWN0akuK2r9Bi8aa1fJ439uzP8VFCP0E6AhNwgDav2DMZNbJUYXIiuOiIREZz
y3BDxJUcP5RHsI9YV4JScyuINxEpIM9kxD3tYOotOgzEt6rl62Xn8HSTzX3LzCG2
VnPtWK+yXXJ4Fv4CZFlsMx+6qoKFDTAdwjJ3cflDmQ4XK2yrJgpvErJP1y0Sz/4=
=Ia0u
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Wed Mar  4 01:05:26 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Wed, 04 Mar 2009 04:05:26 -0500
Subject: [Enigmail] From offlist
In-Reply-To: <49AE0461.9040904@gmail.com>
References: <49ADDFF3.7040500@sixdemonbag.org>	<49ADE414.2000902@sixdemonbag.org>
	<49AE0461.9040904@gmail.com>
Message-ID: <49AE4456.2000806@sixdemonbag.org>

Faramir wrote:
>   Maybe he was confusing SSL with S/MIME, after all, both use x.509
> certificates...

He seemed to get the SSL capabilities correct, though, which makes me
think he really meant SSL.

S/MIME and GnuPG have effectively identical capabilities.

From cejohnsonsr at cableone.net  Sun Mar  8 05:40:25 2009
From: cejohnsonsr at cableone.net (Ed Johnson)
Date: Sun, 08 Mar 2009 07:40:25 -0500
Subject: [Enigmail] Signature test help request
Message-ID: <49B3BCB9.5070002@cableone.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have used Enigmail to sign this email. I have also attached my public
key (I think). I haven't had any luck with Adele so I'm pretty sure I'm
doing something wrong. Just not sure what.

Thanx for any help.

Ed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmzvLkACgkQylXUVp3mRTtH8QCfWAj3sqNMyGqErBWSc6PELTtQ
kxAAn0SHojootFb6aPh0r7KhEUzJahZU
=AwOz
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Ed Johnson cejohnsonsr at cableone.net (0x9DE6453B) pub.asc
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090308/cf9428a2/attachment.ksh>

From jmoore3rd at bellsouth.net  Sun Mar  8 05:52:27 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Sun, 08 Mar 2009 08:52:27 -0400
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3BCB9.5070002@cableone.net>
References: <49B3BCB9.5070002@cableone.net>
Message-ID: <49B3BF8B.4080906@bellsouth.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ed Johnson wrote:
> I have used Enigmail to sign this email. I have also attached my public
> key (I think). I haven't had any luck with Adele so I'm pretty sure I'm
> doing something wrong. Just not sure what.

OpenPGP Security Info

UNTRUSTED Good signature from Ed Johnson <cejohnsonsr at cableone.net>
Key ID: 0x9DE6453B / Signed on: 3/8/2009 8:40 AM
Key fingerprint: 8EA3 642C 3300 6948 035F 6ED4 CA55 D456 9DE6 453B

"UNTRUSTED" just indicates that I have not Signed Your Key nor do We
have any 'Trust Paths' in common.

> Thanx for any help.

There is nothing 'wrong' with attaching a copy of Your Key to messages
but a far more efficient method would be to Upload Your Key to a
Keyserver. [I endorse hkp://pool.sks-keyservers.net]; this will allow
You to simply Sign messages and the recipient can easily retrieve Your
Key from the Server(s).

JOHN ;)
Timestamp: Sunday 08 Mar 2009, 08:52  --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4925: (MingW32)
Comment: Public Key at:  http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: https://www.gswot.org
Comment: Homepage:  http://tinyurl.com/yzhbhx

iQEcBAEBCgAGBQJJs7+FAAoJEBCGy9eAtCsP/ZMIAKZnJUjCGQS0kVdVnSXEoaAz
bRPI6W9rS+y/z/g/QGz6gXW2wEyemEE5xDqsCB6eM5ZZGRTdiEQBXnH3xrXMESud
nbDa0P+k/am9bX6UCNetaqoUhTy1p5LvzzSiH6BjhjA+35TQ84WpbqodiIiMyINq
KUpLsOLnbyeUM88vd2G1GTDRhnBEUrrRCncbI6MuigmHL0yguHbM+vc6BArhZ4dp
DyPDKeGd5eZGuTMHuQHK9WfAM6/myX7lQLMbSKu2iC9AF3rnL9JNt/XA/Qyx7MdF
TXo0X8vVRwIGtn7Vd6S5beHlE+AqEqpshfNILb1BxhfgqHy3WtIbo3ygSmdDm9w=
=FKa/
-----END PGP SIGNATURE-----

From cejohnsonsr at cableone.net  Sun Mar  8 06:30:14 2009
From: cejohnsonsr at cableone.net (Ed Johnson)
Date: Sun, 08 Mar 2009 08:30:14 -0500
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3BF8B.4080906@bellsouth.net>
References: <49B3BCB9.5070002@cableone.net> <49B3BF8B.4080906@bellsouth.net>
Message-ID: <49B3C866.6090907@cableone.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you, John. I'm assuming you were able to read the message & verify
the signature. I uploaded my public key to the server you suggested
during Enigmail setup. I downloaded your key from the same server. I've
been trying to follow the Quick Start guide from the Enigmail website.
There are a couple of differences between the guide & what I actually
see on Thunderbird, but I think I have the "signature only" part
completed. Would you mind terribly if I use you for a test of "signed &
encrypted"? If not I'll send a short, signed, encrypted message for you
to judge.

Thank you again,

Ed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmzyGYACgkQylXUVp3mRTt7NQCeMynCb+vJqo1oOiti6mH/RDqm
SSkAn1sopT6FeilI3Q4pYBywSCO+7zOr
=2Z91
-----END PGP SIGNATURE-----

From shavital at mac.com  Sun Mar  8 06:39:49 2009
From: shavital at mac.com (Charly Avital)
Date: Sun, 08 Mar 2009 09:39:49 -0400
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3BCB9.5070002@cableone.net>
References: <49B3BCB9.5070002@cableone.net>
Message-ID: <49B3CAA5.3050201@mac.com>

Ed Johnson wrote the following on 3/8/09 8:40 AM:
> I have used Enigmail to sign this email. I have also attached my public
> key (I think). I haven't had any luck with Adele so I'm pretty sure I'm
> doing something wrong. Just not sure what.
> 
> Thanx for any help.
> 
> Ed


Hi Ed,

You did attach your public key.

OpenPGP Security Info
Good signature from Ed Johnson <cejohnsonsr at cableone.net>
Key ID: 0x9DE6453B / Signed on: 3/8/09 8:40 AM
Key fingerprint: 8EA3 642C 3300 6948 035F 6ED4 CA55 D456 9DE6 453B

Welcome.
Charly
MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
GPG2 2.0.11 - Thunderbird 2.0.0.19 +Enigmail 0.95.7 - Apple's
Mail+GPGMail 1.2.0 (v56), PGP key: 0xA57A8EFA

From stefanxe at gmx.net  Sun Mar  8 06:58:28 2009
From: stefanxe at gmx.net (Stefan X)
Date: Sun, 08 Mar 2009 14:58:28 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
Message-ID: <49B3CF04.90806@gmx.net>

Hi!
I am testing my new OpenPGP Card but unfortunately experiencing a
fundamental problem with Enigmail.

I have two accounts and two email addresses A and B and using Enigmail
on both. Account B is set up with the OpenPGP Card. Sending an encypted
(but unsigned) Email from B (OpenPGP Card) to A works without a problem.
Sending an encrypted Email from A to B (OpenPGP Card), decrypting the
message with Enigmail fails:

"Error - secret key needed to decrypt message
No SmartCard could not be found in your reader"

So I save the email and decrypt it with "gpg -d mail.eml" which works
without any problem. The message is encrypted with the third subkey of
the card. For me it seems that Enigmail is expecting a card with the ID
bound to the email address but this is NOT the encryption key. Because
of this Enigmail may think the available smart card is not the required one.

Also I experiencing a similar problem when trying to sign a message with
the OpenPGP Card.

I set up account B from scratch, generated new keys on the card and I am
pretty sure I did no mistake. Any idea what is wrong and how to correct
it? I really appreciate any help!

Regards
Stefan

From olav at mozilla-enigmail.org  Sun Mar  8 07:04:24 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Sun, 08 Mar 2009 15:04:24 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3CF04.90806@gmx.net>
References: <49B3CF04.90806@gmx.net>
Message-ID: <49B3D068.7070201@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Stefan,

> It seems that Enigmail is expecting a card with the ID bound to the email
> address but this is NOT the encryption key. Because of this Enigmail may
> think the available smart card is not the required one.

Third key = Authentication key on card or a subkey bound to the UID?

But I'd expect that when "gpg -d mail.eml" works (without explicitely
telling GnuPG which keyID to use), then Enigmail should do aswell.

Could you please enable Enigmail debugging and create a debug log?

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: http://privat.seyfarth.de/olav/schluessel.html

iEYEAREIAAYFAkmz0GcACgkQL/NBt8fdKe05GACfWN42Kas5AVOl8MtzgzpCPBII
JywAnRy7cM7vBWFWHv6eQXELJrrmvQ/v
=1PFx
-----END PGP SIGNATURE-----

From cejohnsonsr at cableone.net  Sun Mar  8 07:19:18 2009
From: cejohnsonsr at cableone.net (Ed Johnson)
Date: Sun, 08 Mar 2009 09:19:18 -0500
Subject: [Enigmail] Oops! Big time newbie mistake
Message-ID: <49B3D3E6.5090109@cableone.net>

This message isn't signed or encrypted because as soon as I got the
signature all figured out I accidentally changed the file with my
passphrase. Must have cut instead of copy before I saved. It's gone. So
now I need to learn how to revoke the key(s) I generated. I created
revocation certificate(s) during key generation.

Any help is appreciated.

Ed

From stefanxe at gmx.net  Sun Mar  8 07:48:22 2009
From: stefanxe at gmx.net (Stefan X)
Date: Sun, 08 Mar 2009 15:48:22 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3D068.7070201@mozilla-enigmail.org>
References: <49B3CF04.90806@gmx.net> <49B3D068.7070201@mozilla-enigmail.org>
Message-ID: <49B3DAB6.8030607@gmx.net>

Hi Olav!

>> It seems that Enigmail is expecting a card with the ID bound to the email
>> address but this is NOT the encryption key. Because of this Enigmail may
>> think the available smart card is not the required one.
> 
> Third key = Authentication key on card or a subkey bound to the UID?

By third key I mean the last key of three listed when executing "gpg
--card-status". I am not sure whether this is a authentication key.

> But I'd expect that when "gpg -d mail.eml" works (without explicitely
> telling GnuPG which keyID to use), then Enigmail should do aswell.
> 
> Could you please enable Enigmail debugging and create a debug log?

Please see the following debug:

2009-03-08 15:38:18.759 enigmail.js: Logging debug output to ~//enigdbug.txt
2009-03-08 15:38:18.783 enigmail.js: Enigmail version 0.95.0
2009-03-08 15:38:18.783 enigmail.js: OS/CPU=Linux i686
2009-03-08 15:38:18.784 enigmail.js: Platform=X11
2009-03-08 15:38:18.784 enigmail.js: composeSecure=true
2009-03-08 15:38:18.786 enigmail.js: Enigmail.initialize: gEnvList =
DISPLAY=:0.0,HOME=/home/otto,LANG=de_DE.UTF-8,LOGNAME=otto,LD_LIBRARY_PATH=/usr/lib/thunderbird:/usr/lib/thunderbird/plugins:/usr/lib/mre/mre-2.0.0.19,MOZILLA_FIVE_HOME=/usr/lib/thunderbird,PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games,PWD=/home/otto,SHELL=/bin/bash,USER=otto
2009-03-08 15:38:18.787 enigmail.js: ResolvePath: filePath=gpg
2009-03-08 15:38:18.788 EnigmailAgentPath=/usr/bin/gpg

2009-03-08 15:38:18.800 enigmail> /usr/bin/gpg --charset utf8  --batch
--no-tty --version
2009-03-08 15:38:18.800 gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Unterst?tzte Verfahren:
?ff.Schl?ssel: RSA, RSA-E, RSA-S, ELG-E, DSA
Verschl?.: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Komprimierung: nicht komprimiert, ZIP, ZLIB, BZIP2

2009-03-08 15:38:18.801 enigmail.js: detectGpgAgent
2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent: GPG_AGENT_INFO
variable available
2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
2009-03-08 15:38:18.803 enigmail.js: Enigmail.stillActive:
2009-03-08 15:38:18.803 enigmail.js: Enigmail.initialize: END
2009-03-08 15:38:18.807 enigmail.js: Enigmail.mimeInitialized: false
2009-03-08 15:38:18.807 enigmailMessengerOverlay.js: loading
enigmail:dummy ...
2009-03-08 15:38:18.808 enigmailCommon.js: EnigGetFrame: name=messagepane
2009-03-08 15:38:18.810 enigmail.js: getClassObject:
cid={847b3a11-7ab1-11d4-8f02-006008948af5}
2009-03-08 15:38:18.811 enigmail.js:
EnigmailProtocolHandlerFactory.createInstance
2009-03-08 15:38:18.811 enigmail.js: EnigmailProtocolHandler.QueryInterface
2009-03-08 15:38:18.812 enigmail.js: EnigmailProtocolHandler.newURI:
aSpec='enigmail:dummy'
2009-03-08 15:38:18.813 enigmail.js: EnigmailProtocolHandler.newChannel:
URI='enigmail:dummy'
2009-03-08 15:38:18.823 enigmailMessengerOverlay.js: enigMessageFrameUnload
2009-03-08 15:38:18.824 enigmailMsgHdrViewOverlay.js: enigMessageUnload
2009-03-08 15:38:18.902 enigmailMessengerOverlay.js: enigMessageFrameLoad
2009-03-08 15:38:18.903 enigmailMessengerOverlay.js: *****enigMimeInit
2009-03-08 15:38:18.904 enigmailMessengerOverlay.js: *****enigMimeInit:
handlePGPMime=true
2009-03-08 15:38:18.906 enigmail.js: Enigmail.mimeInitialized: true
2009-03-08 15:38:18.906 enigmailMessengerOverlay.js: *****enigMimeInit:
RELOADING MESSAGE
2009-03-08 15:38:18.907 enigmailMessengerOverlay.js: enigMessageReload:
false
2009-03-08 15:38:18.988 enigmailMessengerOverlay.js: enigMessageFrameUnload
2009-03-08 15:38:18.989 enigmailMessengerOverlay.js: enigMessageCleanup
2009-03-08 15:38:18.995 enigmailMsgHdrViewOverlay.js: enigStartHeaders
2009-03-08 15:38:18.997 enigmailCommon.js: EnigGetFrame: name=messagepane
2009-03-08 15:38:18.998 enigmailMsgHdrViewOverlay.js: msgFrame=[object
Window]
2009-03-08 15:38:18.999 enigmailMsgHdrViewOverlay.js: enigPrepSecurityInfo
2009-03-08 15:38:19.011 enigmailMsgHdrViewOverlay.js: enigEndHeaders
2009-03-08 15:38:19.014 enigmail.js: Enigmail.decryptMessageStart:
prompter=[xpconnect wrapped nsIPrompt], verifyOnly=false, noOutput=false
2009-03-08 15:38:19.015 enigmail.js: Enigmail.execStart: command =
/usr/bin/gpg --charset utf8  --batch --no-tty --status-fd 2 -d,
needPassphrase=true, domWindow=null, prompter=[xpconnect wrapped
nsIPrompt], listener=null, noProxy=false
2009-03-08 15:38:19.015 enigmail.js: GetPassphrase:
2009-03-08 15:38:19.016 enigmail.js: WriteFileContents: file=~//enigcmd.txt
2009-03-08 15:38:19.230 enigmail.js: WriteFileContents: file=~//enigenv.txt
2009-03-08 15:38:19.352 enigmail.js: Enigmail.execStart: copied command
line/env to files ~//enigcmd.txt/enigenv.txt
2009-03-08 15:38:19.353
enigmail> /usr/bin/gpg --charset utf8  --batch --no-tty --status-fd 2 -d
--use-agent
2009-03-08 15:38:19.354 enigmail.js: Enigmail.execStart: pipetrans =
[xpconnect wrapped nsIPipeTransport]
2009-03-08 15:38:19.371 enigmail.js: Enigmail.decryptMessageEnd:
uiFlags=8, outputLen=1, pipeTransport=[xpconnect wrapped
nsIPipeTransport], verifyOnly=false, noOutput=false
2009-03-08 15:38:19.372 enigmail.js: Enigmail.execEnd:
2009-03-08 15:38:19.373 enigmail.js: WriteFileContents: file=~//enigerr.txt
2009-03-08 15:38:19.507 enigmail.js: Enigmail.execEnd: copied command
err output to file ~//enigerr.txt
2009-03-08 15:38:19.508 enigmail.js: Enigmail.execEnd: exitCode = 2
2009-03-08 15:38:19.509 enigmail.js: Enigmail.execEnd: errOutput =
[GNUPG:] ENC_TO AF9A794E93F89FE5 1 0
[GNUPG:] CARDCTRL 4
gpg: selecting openpgp failed: unknown command
[GNUPG:] ENC_TO E36CE9BFC1920D94 16 0
gpg: verschl?sselt mit 4096-Bit ELG-E Schl?ssel, ID C1920DA5, erzeugt
2007-09-05
      "Test Mustermann <a at example.com>"
[GNUPG:] NO_SECKEY E36CE9BFC1920D94
gpg: verschl?sselt mit 1024-Bit RSA Schl?ssel, ID 93F89FE5, erzeugt
2009-03-08
      "Otto Test <b at example.com>"
gpg: Entschl?sselung mit Public-Key-Verfahren fehlgeschlagen:
Allgemeiner Fehler
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_FAILED
gpg: Entschl?sselung fehlgeschlagen: Geheimer Schl?ssel ist nicht vorhanden
[GNUPG:] END_DECRYPTION

2009-03-08 15:38:19.509 enigmail.js: Enigmail.parseErrorOutput:
2009-03-08 15:38:19.511 enigmail.js: Enigmail.parseErrorOutput:
statusFlags = 08010100
2009-03-08 15:38:19.511 No SmartCard could not be found in your reader
Please insert your SmartCard and repeat the operation
2009-03-08 15:38:19.512 enigmail.js: Enigmail.stillActive:
2009-03-08 15:38:19.512 enigmail.js: Enigmail.decryptMessageEnd: Error
in command execution
2009-03-08 15:38:19.513 enigmailMsgHdrViewOverlay.js:
EnigMimeHeaderSink.updateSecurityStatus: uriSpec=
2009-03-08 15:38:19.515 enigmailMsgHdrViewOverlay.js:
EnigMimeHeaderSink.updateSecurityStatus:
msgUriSpec=imap-message://otto%40example.com at mail.example.com/INBOX#3
2009-03-08 15:38:19.516 enigmailMsgHdrViewOverlay.js:
enigUpdateHdrIcons: exitCode=2, statusFlags=136380672, keyId=null,
userId=null, gpg command line and output:
/usr/bin/gpg --charset utf8  --batch --no-tty --status-fd 2 -d --use-agent
No SmartCard could not be found in your reader
Please insert your SmartCard and repeat the operation
2009-03-08 15:38:19.517 enigmailCommon.js: EnigConvertToUnicode: utf-8
2009-03-08 15:38:19.673 enigmailMessengerOverlay.js: enigMessageFrameLoad
2009-03-08 15:38:19.676 enigmailMessengerOverlay.js: enigMessageDecrypt:
[object Event]
2009-03-08 15:38:19.677 enigmailMessengerOverlay.js: content-type:
multipart/encrypted; protocol="application/pgp-encrypted";
boundary="------------enig0EC1272783899CA2C003D34C"
2009-03-08 15:38:19.678 enigmailMessengerOverlay.js:
content-transfer-encoding:
2009-03-08 15:38:19.679 enigmailMessengerOverlay.js: x-enigmail-version:
0.95.7
2009-03-08 15:38:19.680 enigmailMessengerOverlay.js: multipart/encrypted
2009-03-08 15:38:19.681 enigmail.js: Enigmail.mimeInitialized: true

From cejohnsonsr at cableone.net  Sun Mar  8 08:01:48 2009
From: cejohnsonsr at cableone.net (Ed Johnson)
Date: Sun, 08 Mar 2009 10:01:48 -0500
Subject: [Enigmail] Signed & Encrypted Test
Message-ID: <49B3DDDC.3080103@cableone.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok... So I uploaded the revocation certificate(s) to the keyserver, then
generated new key(s) & uploaded them to the keyserver, and finally
tested the signature & encryption @ Adele. So now I guess if I get an
answer to this, & can read it, I must have done something right.

Here goes nothing!

Ed :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmz3dwACgkQeaf7ePY/KppG0wCePKmdjc4gjAdhM6bg8yyP1IHi
eY0AnA4wb5WJlTs3iOp8HzcsvCP30UzD
=GJIr
-----END PGP SIGNATURE-----

From olav at mozilla-enigmail.org  Sun Mar  8 09:07:12 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Sun, 08 Mar 2009 17:07:12 +0100
Subject: [Enigmail] Oops! Big time newbie mistake
In-Reply-To: <49B3D3E6.5090109@cableone.net>
References: <49B3D3E6.5090109@cableone.net>
Message-ID: <49B3ED30.4020208@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Ed,

> [I deleted my private key's passphrase which was written in a file]

your passphrase should be in your memory rather than in a file. If you create
a file or paper copy, make sure to protect it thoroughly. Personally, I only
memorize a handful of passphrases for encryption. All other passwords I store
encryptedly using one of the "master" passwords. Make sure you are able to
remember your private key passphrase. You'll have to type it quite often once
you start using signing/encrypting on a regular basis.

> I need to learn how to revoke the key(s) I generated.
> I created revocation certificate(s) during key generation.

Your key appears to be revoked properly. So you seem to have managed already.

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: http://privat.seyfarth.de/olav/schluessel.html

iEYEAREIAAYFAkmz7S8ACgkQL/NBt8fdKe35DwCfYTMii4jEi0n1sfoR8rkp/Sd5
ITIAnRq91aQ+aIKO4/ryyz8XTcvBBmK2
=hawm
-----END PGP SIGNATURE-----

From jmoore3rd at bellsouth.net  Sun Mar  8 09:13:32 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Sun, 08 Mar 2009 12:13:32 -0400
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3C866.6090907@cableone.net>
References: <49B3BCB9.5070002@cableone.net> <49B3BF8B.4080906@bellsouth.net>
	<49B3C866.6090907@cableone.net>
Message-ID: <49B3EEAC.606@bellsouth.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ed Johnson wrote:

> Would you mind terribly if I use you for a test of "signed &
> encrypted"? If not I'll send a short, signed, encrypted message for you
> to judge.

No Problem whatsoever with exchanging Encrypted Messages.  PLEASE send
them to Me directly and _not_ to the Enigmail List.

JOHN ;)
Timestamp: Sunday 08 Mar 2009, 12:13  --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4925: (MingW32)
Comment: Public Key at:  http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: https://www.gswot.org
Comment: Homepage:  http://tinyurl.com/yzhbhx

iQEcBAEBCgAGBQJJs+6rAAoJEBCGy9eAtCsPmk8H/jDbxMCBu7BCj2T9wtwe+LHQ
fUWdIQDB45XvLaHOaN7UGABz6EKmVuHkpqp5YJH91PQefoaoceyk39WE3juNBgC2
PyrsToszebSRj7FLjiLdPEacVEY7WX3lMd2c+wOj8ceFZrkcUIZLdGzycU1D04st
NHLU3ouTytgEPJsrlGprMol8EotagKLxuRytb5k6GxIAWlhn2eMmQmia1vlapSyK
h1V+zAysVQXeQPolklfOBrLnbnOH2nJ4NJQGMy8T5lihXQpcU3Xy8sufvAx+YRsP
WxyYSatr7jsHiOL2QRxFQTID3isk9uSCuN/nQwYypmLr2V3GMf7btpOghHSWYdc=
=27ll
-----END PGP SIGNATURE-----

From olav at mozilla-enigmail.org  Sun Mar  8 09:15:51 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Sun, 08 Mar 2009 17:15:51 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3DAB6.8030607@gmx.net>
References: <49B3CF04.90806@gmx.net> <49B3D068.7070201@mozilla-enigmail.org>
	<49B3DAB6.8030607@gmx.net>
Message-ID: <49B3EF37.4070304@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Stefan,

> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'

Could you please disable "use GPG agent" in OpenPGP advanced settings and
try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
might also try using GnuPG 2.x and reenable "use GPG agent".

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: http://privat.seyfarth.de/olav/schluessel.html

iEYEAREIAAYFAkmz7zYACgkQL/NBt8fdKe1pOQCgv28TdzyEiOv39RBKuuwLaPYv
/sgAoJpvki2F3l8SRwscqsoZZWcZ4dlp
=cfi8
-----END PGP SIGNATURE-----

From jmoore3rd at bellsouth.net  Sun Mar  8 09:20:48 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Sun, 08 Mar 2009 12:20:48 -0400
Subject: [Enigmail] Oops! Big time newbie mistake
In-Reply-To: <49B3D3E6.5090109@cableone.net>
References: <49B3D3E6.5090109@cableone.net>
Message-ID: <49B3F060.6090401@bellsouth.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ed Johnson wrote:
> This message isn't signed or encrypted because as soon as I got the
> signature all figured out I accidentally changed the file with my
> passphrase. Must have cut instead of copy before I saved. It's gone. So
> now I need to learn how to revoke the key(s) I generated. I created
> revocation certificate(s) during key generation.
> 
> Any help is appreciated.

Congratulations on generating a Revocation Certificate _prior_ to losing
the passphrase.  :-D

Now, simply Import the Revocation Certificate into Your Keyring and then
Upload the revoked Key to the same Keyserver as before.

Then You are done; except for generation and Upload of a New Key.  ;)

JOHN 8-)
Timestamp: Sunday 08 Mar 2009, 12:20  --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4925: (MingW32)
Comment: Public Key at:  http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: https://www.gswot.org
Comment: Homepage:  http://tinyurl.com/yzhbhx

iQEcBAEBCgAGBQJJs/BeAAoJEBCGy9eAtCsPwxAH/RzQ97LxJEAzncfEsah8eajS
ATK1mHjGHHNTyejVTa4B+q6FRDY1MJ9n9Vi2TkYq9IET7REPav69qCM2k3aHHimp
GjviLJ8xlmm7112DEimLeO0h3sBzdDy16mABrYSlccgCI98MKteg5gSnhzE+EXyn
mhPBAzq5QdJvDMTy+SDtPAeXtapQVlEIC6Kv9AyAyg1/SjdxTA2uXXi/fT4Iq6ug
qXK5zX7irMoCs3hgbtGqPXHpQK0X5p3muIqDHu6O6cMhoMvB0cUqV+zHOJh4V55g
t0pJQYffUGR3MQUlonBOULjYrZwZ+/7PqFXbmbaQP24QlPaZqwYvkBNzWx5T17k=
=zjqH
-----END PGP SIGNATURE-----

From jmoore3rd at bellsouth.net  Sun Mar  8 09:22:20 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Sun, 08 Mar 2009 12:22:20 -0400
Subject: [Enigmail] Signed & Encrypted Test
In-Reply-To: <49B3DDDC.3080103@cableone.net>
References: <49B3DDDC.3080103@cableone.net>
Message-ID: <49B3F0BC.3020803@bellsouth.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ed Johnson wrote:
> Ok... So I uploaded the revocation certificate(s) to the keyserver, then
> generated new key(s) & uploaded them to the keyserver, and finally
> tested the signature & encryption @ Adele. So now I guess if I get an
> answer to this, & can read it, I must have done something right.

Whew!  From the Subject I feared You had sent an Encrypted message to
the List.

This Message, and Signature, verified as Good.

JOHN ;)
Timestamp: Sunday 08 Mar 2009, 12:22  --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4925: (MingW32)
Comment: Public Key at:  http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: https://www.gswot.org
Comment: Homepage:  http://tinyurl.com/yzhbhx

iQEcBAEBCgAGBQJJs/C6AAoJEBCGy9eAtCsPgCsH/As/2JTjql4W+oQH51TBzwvM
OF4mwVzpNUhwFiTJ58KeVDPft99KSlYYMtocG/rIGvAjU8jIcGshmrQ6HAphx9TI
8/80bhBAciZstqZVhP2BDhruqGMcJa6ycMUEwpSI/PbQACkPEagby44qTfvKIGSL
IE4b3mhft+UD8zvO1Xw9ghU2m7djgL72Cn/M9BDo8Nrq8FnLq1EZuihyzTffijNP
XZknEgdkvR8CmWLNvKSuLC9jp+R8Z62tRohonQAltpg5NSxSwSH2UBB0PKJ5DyYD
ybChY1gcZT5dApd3aGE4Xo0TOznK7eZNmGkTAyprVxyF7qziz+dCogIdE/Uvns4=
=GJ3d
-----END PGP SIGNATURE-----

From alaric at metrocast.net  Sun Mar  8 09:47:28 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Sun, 08 Mar 2009 12:47:28 -0400
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3BCB9.5070002@cableone.net>
References: <49B3BCB9.5070002@cableone.net>
Message-ID: <49B3F6A0.8050603@metrocast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ed Johnson wrote:
> I have used Enigmail to sign this email. I have also attached my public
> key (I think). I haven't had any luck with Adele so I'm pretty sure I'm
> doing something wrong. Just not sure what.

I got:
OpenPGP Security Info

UNTRUSTED REVOKED KEY Good signature from Ed Johnson
<cejohnsonsr at cableone.net>
Key ID: 0x9DE6453B / Signed on: 03/08/09 08:40
Key fingerprint: 8EA3 642C 3300 6948 035F 6ED4 CA55 D456 9DE6 453B


Which seems to imply you've done something wrong.  Did you prepare
yourself a revocation certificate against future need, then
inadvertently upload it...?



- --
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric at caerllewys.net   alaric at metrocast.net   phil at co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkmz9qAACgkQ0DfOju+hMknjxwCfWFJsV/k9Hpxp675jv//XQ0gl
fQQAn3/yi7iS3qmImvbobzx4GVZS4ans
=Qvua
-----END PGP SIGNATURE-----

From alaric at metrocast.net  Sun Mar  8 09:50:27 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Sun, 08 Mar 2009 12:50:27 -0400
Subject: [Enigmail] Signed & Encrypted Test
In-Reply-To: <49B3DDDC.3080103@cableone.net>
References: <49B3DDDC.3080103@cableone.net>
Message-ID: <49B3F753.1040608@metrocast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ed Johnson wrote:
> Ok... So I uploaded the revocation certificate(s) to the keyserver, then
> generated new key(s) & uploaded them to the keyserver, and finally
> tested the signature & encryption @ Adele. So now I guess if I get an
> answer to this, & can read it, I must have done something right.

Aha.  That explains the revoked-key message I got.

This one looks good:

OpenPGP Security Info

UNTRUSTED Good signature from Ed Johnson <cejohnsonsr at cableone.net>
Key ID: 0xF63F2A9A / Signed on: 03/08/09 11:01
Key fingerprint: 4AA6 16DE 3C8C 233F 4785 4DCF 79A7 FB78 F63F 2A9A




- --
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric at caerllewys.net   alaric at metrocast.net   phil at co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkmz91MACgkQ0DfOju+hMklpZgCbBfbV6ujSnavlTy8TnS9iv0GY
JPsAoJS1bYGQs7xH7rpl5R9uA488EE3F
=xZCl
-----END PGP SIGNATURE-----

From stefanxe at gmx.net  Sun Mar  8 10:23:02 2009
From: stefanxe at gmx.net (Stefan X)
Date: Sun, 08 Mar 2009 18:23:02 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3EF37.4070304@mozilla-enigmail.org>
References: <49B3CF04.90806@gmx.net>
	<49B3D068.7070201@mozilla-enigmail.org>	<49B3DAB6.8030607@gmx.net>
	<49B3EF37.4070304@mozilla-enigmail.org>
Message-ID: <49B3FEF6.7080704@gmx.net>

Hi Olav,
the funny thing is, "use GPG agent" is already DISABLED! What to do?

Regards
Stefan

Olav Seyfarth schrieb:
> Hi Stefan,
> 
>> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
>> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
> 
> Could you please disable "use GPG agent" in OpenPGP advanced settings and
> try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
> might also try using GnuPG 2.x and reenable "use GPG agent".
> 
> Olav
_______________________________________________
Enigmail mailing list
Enigmail at mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail


From stefanxe at gmx.net  Sun Mar  8 11:18:42 2009
From: stefanxe at gmx.net (Stefan X)
Date: Sun, 08 Mar 2009 19:18:42 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3FEF6.7080704@gmx.net>
References: <49B3CF04.90806@gmx.net>	<49B3D068.7070201@mozilla-enigmail.org>	<49B3DAB6.8030607@gmx.net>	<49B3EF37.4070304@mozilla-enigmail.org>
	<49B3FEF6.7080704@gmx.net>
Message-ID: <49B40C02.5040605@gmx.net>

I found out that I don't have gnupg-agent installed. So I am wondering
why Enigmail executes gnupg with the --use-agent argument. It seems that
Seahorse (which is installed by default in Ubuntu) simulates a
gnupg-agent. At least after killing the seahorse background process the
error message (when decrypting the message) changes to the following:

OpenPGP Security Info

Error - secret key needed to decrypt message

gpg command line and output:
/usr/bin/gpg --charset utf8  --batch --no-tty --status-fd 2 -d --use-agent
can't connect to `/tmp/seahorse-VSOdb4/S.gpg-agent': No such file or
directory
gpg: detected reader `Gemplus GemPC Twin 00 00'
can't connect to `/tmp/seahorse-VSOdb4/S.gpg-agent': No such file or
directory
gpg: Verbindung zu '/tmp/seahorse-VSOdb4/S.gpg-agent' kann nicht
aufgebaut werden: connect failed
gpg: Passwortsatz kann im Batchmodus nicht abgefragt werden
gpg: PIN-Callback meldete Fehler: Allgemeiner Fehler

I suspect that Seahorse is not able to handle smartcards. If so it may
be a solution to use gpg-agent instead. Unfortunately I didn't figured
out how to do this. Also please note that Seahorse depends of the
important package ubuntu-desktop so I would prefer avoiding its removal.

Any idea?

Regards
Stefan

Stefan X schrieb:
> Hi Olav,
> the funny thing is, "use GPG agent" is already DISABLED! What to do?
> 
> Regards
> Stefan
> 
> Olav Seyfarth schrieb:
>> Hi Stefan,
>>
>>> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
>>> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
>> Could you please disable "use GPG agent" in OpenPGP advanced settings and
>> try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
>> might also try using GnuPG 2.x and reenable "use GPG agent".
>>
>> Olav
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail
> 
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail
> 

From base4ingenieros at gmail.com  Sun Mar  8 14:02:52 2009
From: base4ingenieros at gmail.com (=?ISO-8859-1?Q?Jos=E9_P=E9rez_Ram=EDrez?=)
Date: Sun, 08 Mar 2009 21:02:52 +0000
Subject: [Enigmail] Consulta archivo adjunto a un correo
Message-ID: <49B4327C.9090601@gmail.com>

I have received an email with the archive I adjunt to this message

comentarios.txt.pgp , but I don't see i can open in anyway.
What's the solution. Is well sended ?
Thanks
Excuse my language. I'm from Canary Islands
-- 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: comentarios.txt.pgp
Type: application/pgp-encrypted
Size: 2069 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090308/66d0123d/attachment.bin>

From faramir.cl at gmail.com  Sun Mar  8 14:28:26 2009
From: faramir.cl at gmail.com (Faramir)
Date: Sun, 08 Mar 2009 18:28:26 -0300
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3BCB9.5070002@cableone.net>
References: <49B3BCB9.5070002@cableone.net>
Message-ID: <49B4387A.4010000@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ed Johnson escribi?:
> I have used Enigmail to sign this email. I have also attached my public
> key (I think). I haven't had any luck with Adele so I'm pretty sure I'm
> doing something wrong. Just not sure what.

  The signature is right, but your key has been revoked...

  Best Regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJJtDh6AAoJEMV4f6PvczxAV9oH/3QuVDKFawejVGF1MGbjUxyS
zEjsB2muxa+Upx3eVl/nIgdaNW1SGpm3Ta9uzqXwmcHFXnaZ0NaVplq0Fxzz5eu8
IlWOPWb+Jw0eEXxVkIVwhqfAIy3IVvQ/Oqnm5r1jORqJXV5hFGcjOaMPmnCu3/wR
VVWF5Yu47xciNBTuc/fUIgu2JBwNCkGozSeg5zoYiz79bqC9Epy85yEvO+yJVSrI
KOexS2FrloVQ5db0b/oThSFviMCFCNmfmU0krSiNYszRjlEWgHxkHpkl3Om09MIn
EkpweNE1VsLQPoEV7Qu10HQybtwRU758hv1YLFsLmdYSHmsJrZBeg/Lly/u1R6E=
=g6Mh
-----END PGP SIGNATURE-----

From faramir.cl at gmail.com  Sun Mar  8 14:51:38 2009
From: faramir.cl at gmail.com (Faramir)
Date: Sun, 08 Mar 2009 18:51:38 -0300
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B4327C.9090601@gmail.com>
References: <49B4327C.9090601@gmail.com>
Message-ID: <49B43DEA.9040604@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jos? P?rez Ram?rez escribi?:
> I have received an email with the archive I adjunt to this message
> 
> comentarios.txt.pgp , but I don't see i can open in anyway.
> What's the solution. Is well sended ?
> Thanks
> Excuse my language. I'm from Canary Islands

  It seems the file was encrypted to 2 different keys. The OpenPGP
Packets info shows:

:pubkey enc packet: version 3, algo 16, keyid E6DCA708CE35C83D
	data: [4096 bits]
	data: [4095 bits]
:pubkey enc packet: version 3, algo 16, keyid E45FC8B3A94DD644
	data: [2045 bits]
	data: [2047 bits]
:encrypted data packet:
	length: 496
	mdc_method: 2

  Searching at keyservers, I didn't find anything with the first keyid,
but the second one is the encrypting subkey of the following key:

pub  1024D/0xDAC18C9B  creado: 2009-02-05  caduca: nunca
      Huella de clave = C22C D7CC 5EE8 A2F2 597D  EABC F889 6941 DAC1 8C9B

     Jos? P?rez Ram?rez (claves para base4ingenieros) <base4ingenieros
AT gmail.com>

  If you don't have the private key for that key, or for the other one
(which is not in keyservers), you can't open it...

  Do you have an OpenPGP key? (PGP or GnuPG).

  If you have a key that can decrypt the file, and you need hints about
how to use it, I'm sure people here will be able to help you, no matter
if you are using windows, linux, PGP or GnuPG...

  I'll put my reply in spanish too:

  Mir? en la informaci?n de paquetes OpenPGP del archivo, y al parecer
fue cifrado (por ahi dicen que la palabra "encriptado" no existe en
Castellano) para 2 claves diferentes. De la primera no encontr?
informaci?n, pero la segunda es la subclave de cifrado de la clave cuyos
datos puse m?s arriba. ?Tienes una clave OpenPGP (ya sea que uses PGP o
GnuPG, tambien conocido como GPG)? Si no, no hay manera de que lo
descifres. Si tienes una clave, pero no lo cifraron para tu clave,
igualmente no hay manera de que lo descifres.

  Ahora, si tienes una de las claves que pueden abrir el archivo, seria
cosa de guardar el adjunto en el ordenador, y usar el programa OpenPGP
que tengas para descifrarlo. Yo solo se usar GnuPG, y adem?s lo uso con
interfaces de usuario (para Windows), asi que puede que mi manera de
usarlo no te sirva de mucho, dependiendo de qu? uses t?. Si te puedo
orientar un poco m?s, avisame y tratar? de ayudarte.

  Saludos

Best Regards

P.S: both replies are a bit different... I tend to write longer when I
write in Spanish...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJJtD3qAAoJEMV4f6PvczxAaf0H/jO+lHm/A0MtUHBPP8HihrwU
SKYuVsvx32OvThzgAfJZ1iGL5TR7s7C/s+Sm5ycj8LBRkHuOUkOiADxK8fabREnX
Mz8JNDHPGA4RH3kymfbJLdfRS7SIG5eevshg75vpQq/dbioHI3bryCmbqLgKr77W
dTXTteNiQ+GsoW89JoU+aGQ53Zozccaj/7HPN+qhmVqiBO7MH9VliIdm3L3Mhgnf
4L0+K3sPraidMJOWX0Qw2mFRT2aYu9+mfe3+Sv8LdGwlz9FBila4NevRGSYAbJdT
ieH28EAVvpMIt5selCJDRw89xLaPTcgFnH3ePa63pplB4fst3Z7RN6tJavzRqV4=
=DfzI
-----END PGP SIGNATURE-----

From John at Mozilla-Enigmail.org  Sun Mar  8 17:57:13 2009
From: John at Mozilla-Enigmail.org (John Clizbe)
Date: Sun, 08 Mar 2009 19:57:13 -0500
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B4327C.9090601@gmail.com>
References: <49B4327C.9090601@gmail.com>
Message-ID: <49B46969.7030403@Mozilla-Enigmail.org>

Jos? P?rez Ram?rez wrote:
> I have received an email with the archive I adjunt to this message
> 
> comentarios.txt.pgp , but I don't see i can open in anyway.
> What's the solution. Is well sended ?
> Thanks

As Faramir pointed out, it looks to be encrypted to one of your keys.

If you still have access to the key, click the item once to select it,
then right-click for the context menu and choose 'Decrypt and Open'.

-- 
John P. Clizbe                      Inet:John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net  or
     mailto:pgp-public-keys at gingerbear.net?subject=HELP

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 678 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090308/cc1fc7ea/attachment.bin>

From base4ingenieros at gmail.com  Sun Mar  8 18:20:33 2009
From: base4ingenieros at gmail.com (=?ISO-8859-1?Q?Jos=E9_P=E9rez_Ram=EDrez?=)
Date: Mon, 09 Mar 2009 01:20:33 +0000
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B46969.7030403@Mozilla-Enigmail.org>
References: <49B4327C.9090601@gmail.com>
	<49B46969.7030403@Mozilla-Enigmail.org>
Message-ID: <49B46EE1.4040508@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
John Clizbe escribi?:
> Jos? P?rez Ram?rez wrote:
>> I have received an email with the archive I adjunt to this message
>>
>> comentarios.txt.pgp , but I don't see i can open in anyway.
>> What's the solution. Is well sended ?
>> Thanks
>
> As Faramir pointed out, it looks to be encrypted to one of your keys.
>
> If you still have access to the key, click the item once to select it,
> then right-click for the context menu and choose 'Decrypt and Open'.
>
>
> ----------------------------------------------------------------------
>
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail
Done. I have read with no problem the archive.
Thank very much
I sign this message. Tellme if you receive my public key I post together.
Adjunto mi clave p?blica en este mensaje - public key goes with this
message.
- --

- --

    *Jos? D. P?rez Ram?rez*
           Proyectos y Peritaciones
 
 Avenida Tres de Mayo, 12
       38003 Santa Cruz de Tenerife

      Correo electr?nico: base4ingenieros at gmail.com
Tlf: 619040850 Fax 922200309

 

- ----------------------------------------------------------------------
 
*Este mensaje, y en su caso cualquier fichero anexo al mismo, se
dirige exclusivamente a su destinatario y puede contener
informaci?n privilegiada y/o confidencial siendo para uso exclusivo
del destinatario. Si no es Vd. el destinatario indicado, queda
notificado de que la utilizaci?n, divulgaci?n y/o copia sin
autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha
recibido
este mensaje por error, le rogamos que nos lo comunique inmediatamente
por esta misma v?a y proceda a su destrucci?n. Asimismo,
se le advierte que toda la informaci?n personal contenida en este
mensaje se encuentra protegida por la Ley Org?nica 15/1999, de
13 de diciembre de protecci?n de datos de car?cter personal, quedando
totalmente prohibido su uso y/o tratamiento, as? como la
cesi?n de aquella a terceros al margen de lo dispuesto en la citada
ley protectora de datos personales y de su normativa
de desarrollo. (Standart Disclaimer Appended) *
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFJtG7g+IlpQdrBjJsRApWnAJ4zorAVGZ/Eq6C3dC29Rwd5TGZf/gCdGpVO
6bX8ZIvSoTS8tH2JJn95QYk=
=9LDM
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090309/ad0b1e9c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDAC18C9B.asc
Type: application/pgp-keys
Size: 1741 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090309/ad0b1e9c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDAC18C9B.asc.sig
Type: application/octet-stream
Size: 65 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090309/ad0b1e9c/attachment.obj>

From olav at seyfarth.de  Mon Mar  9 01:05:23 2009
From: olav at seyfarth.de (Olav Seyfarth)
Date: Mon, 09 Mar 2009 09:05:23 +0100
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B46EE1.4040508@gmail.com>
References: <49B4327C.9090601@gmail.com>	<49B46969.7030403@Mozilla-Enigmail.org>
	<49B46EE1.4040508@gmail.com>
Message-ID: <49B4CDC3.1070206@seyfarth.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hola Jos?,

> I sign this message. Tellme if you receive my public key I post together.

your attached key and sig is fine.

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Dies ist eine elektronische Signatur nach OpenPGP-Standard
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAkm0zcEACgkQL/NBt8fdKe1SiQCfbEjx6tWRnHKDqMa1cjFDLtj5
zZMAn3v3jhlNJ6FGYzm5XfYgu0SK7W+W
=k43z
-----END PGP SIGNATURE-----

From olav at mozilla-enigmail.org  Mon Mar  9 01:06:15 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Mon, 09 Mar 2009 09:06:15 +0100
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B46EE1.4040508@gmail.com>
References: <49B4327C.9090601@gmail.com>	<49B46969.7030403@Mozilla-Enigmail.org>
	<49B46EE1.4040508@gmail.com>
Message-ID: <49B4CDF7.4010309@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hola Jos?,

> I sign this message. Tellme if you receive my public key I post together.

your attached key and sig is fine.

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Dies ist eine elektronische Signatur nach OpenPGP-Standard
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAkm0zcEACgkQL/NBt8fdKe1SiQCfbEjx6tWRnHKDqMa1cjFDLtj5
zZMAn3v3jhlNJ6FGYzm5XfYgu0SK7W+W
=k43z
-----END PGP SIGNATURE-----

From patrick at mozilla-enigmail.org  Mon Mar  9 05:26:13 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Mon, 09 Mar 2009 13:26:13 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B3FEF6.7080704@gmx.net>
References: <49B3CF04.90806@gmx.net>	<49B3D068.7070201@mozilla-enigmail.org>	<49B3DAB6.8030607@gmx.net>	<49B3EF37.4070304@mozilla-enigmail.org>
	<49B3FEF6.7080704@gmx.net>
Message-ID: <49B50AE5.7090607@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Stefan X wrote:
> Olav Seyfarth schrieb:
>> Hi Stefan,
>>
>>> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
>>> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
>> Could you please disable "use GPG agent" in OpenPGP advanced settings and
>> try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
>> might also try using GnuPG 2.x and reenable "use GPG agent".
>>
>> Olav
>
> Hi Olav,
> the funny thing is, "use GPG agent" is already DISABLED! What to do?
>


Please don't top-post. To disable the use of gpg-agent, unset the
environment variavle GPG_AGENT_INFO.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSbUK5HcOpHodsOiwAQivewf/WDgULmj6rFPsfWzypaynDClamZU2lm/1
w6vErqNme2ykWrwdUfeDA1AIIFPzNSKd7yibEfLT+szRi/KWhpMqPC8Kt12sZGPh
sKhanCgn9wxMskfK6kqTtTzK9D2j/ov62NsSnlOYwiHOcYvSR8wUtDX8TbTYnrlt
ssiWa8Lh666xscp6TgWV7x7LB+5rPdoCAgMf2/kIRLqmcH/PiTLcEva4zYQIRGQe
AswSN3hMw07NYxmPTMXrIBLeB917BUj9vp79d7k/mIQ/031zyTtJfPwORskDBxyl
TQWLUDe5ue6rFLbA5ckiGOYAy+j6oD60Nr2nbmIq1xOX/UIfX72Ubg==
=cyyt
-----END PGP SIGNATURE-----

From base4ingenieros at gmail.com  Mon Mar  9 05:57:36 2009
From: base4ingenieros at gmail.com (=?ISO-8859-1?Q?Jos=E9_P=E9rez_Ram=EDrez?=)
Date: Mon, 09 Mar 2009 12:57:36 +0000
Subject: [Enigmail] Consulta archivo adjunto a un correo
In-Reply-To: <49B4CDF7.4010309@mozilla-enigmail.org>
References: <49B4327C.9090601@gmail.com>	<49B46969.7030403@Mozilla-Enigmail.org>	<49B46EE1.4040508@gmail.com>
	<49B4CDF7.4010309@mozilla-enigmail.org>
Message-ID: <49B51240.8060207@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Olav Seyfarth escribi?:
> Hola Jos?,
>
>> I sign this message. Tellme if you receive my public key I post
> together.
>
> your attached key and sig is fine.
>
> Olav
___*Thank everybody.*

____________________________________________
Enigmail mailing list
Enigmail at mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

- --

- --

    *Jos? D. P?rez Ram?rez*
           Proyectos y Peritaciones
 
 Avenida Tres de Mayo, 12
       38003 Santa Cruz de Tenerife

      Correo electr?nico: base4ingenieros at gmail.com
Tlf: 619040850 Fax 922200309

 

- -------------------------
 
*Este mensaje, y en su caso cualquier fichero anexo al mismo, se
dirige exclusivamente a su destinatario y puede contener
informaci?n privilegiada y/o confidencial siendo para uso exclusivo
del destinatario. Si no es Vd. el destinatario indicado, queda
notificado de que la utilizaci?n, divulgaci?n y/o copia sin
autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha
recibido
este mensaje por error, le rogamos que nos lo comunique inmediatamente
por esta misma v?a y proceda a su destrucci?n. Asimismo,
se le advierte que toda la informaci?n personal contenida en este
mensaje se encuentra protegida por la Ley Org?nica 15/1999, de
13 de diciembre de protecci?n de datos de car?cter personal, quedando
totalmente prohibido su uso y/o tratamiento, as? como la
cesi?n de aquella a terceros al margen de lo dispuesto en la citada
ley protectora de datos personales y de su normativa
de desarrollo. (Standart Disclaimer Appended) *
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFJtRJA+IlpQdrBjJsRAlYEAKCBRbhVfYLq8WYUA/AapihLareeUwCgnYPE
LHcj6jepngSljm8No/KZbIc=
=whtA
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090309/8e63af37/attachment.html>

From 85.ayush2 at gmail.com  Sun Mar  8 06:33:43 2009
From: 85.ayush2 at gmail.com (Ayush Sharma)
Date: Sun, 08 Mar 2009 19:03:43 +0530
Subject: [Enigmail] Signature test help request
In-Reply-To: <49B3C866.6090907@cableone.net>
References: <49B3BCB9.5070002@cableone.net> <49B3BF8B.4080906@bellsouth.net>
	<49B3C866.6090907@cableone.net>
Message-ID: <49B3C937.5080606@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ed,

Ed Johnson wrote:
> Thank you, John.
<snip>
Would you mind terribly if I use you for a test of "signed &
> encrypted"? If not I'll send a short, signed, encrypted message for you
> to judge.

You can use me for the "S&E" test too. My key will be imported into your
keyring as I am sending you a signed message.

Best Regards, and wish you a relaxing Sunday,
- -Ayush
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJJs8k3AAoJEFn2wHFCa2+7W+AH/2a7Pss2SXr6LRUGja3szaaJ
29u+l3n2y9vtbF35y8l6iTiaFcJO5ED2RrkXprUrUKUWHrmVeCwnwslGTmXstr6B
yY8OnMj03LHrl1bVciD88AW5r5VAivbHqp16ZXMMOuhAsuTuBsJUxD4MD4UsgTN/
Nphw90ZnQ20OsYrntLRbvaoIhUh9/mGAFpVM7b9KM88GQZhuz6IMREOmSGIFUDBG
4LxuEm56YopDXNWjgUgsqtxl9ne5mGblzXARfH4k29WTuDPU5xZhsv9FlKxjJvxa
fSAAZQLAydFgkFxo1gvpiVM0W3hcDztMMuQGWxg4SftOQByf6BwfDA6CnjG9TEE=
=QvoT
-----END PGP SIGNATURE-----

From stefanxe at gmx.net  Tue Mar 10 01:16:10 2009
From: stefanxe at gmx.net (Stefan X)
Date: Tue, 10 Mar 2009 09:16:10 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B50AE5.7090607@mozilla-enigmail.org>
References: <49B3CF04.90806@gmx.net>	<49B3D068.7070201@mozilla-enigmail.org>	<49B3DAB6.8030607@gmx.net>	<49B3EF37.4070304@mozilla-enigmail.org>	<49B3FEF6.7080704@gmx.net>
	<49B50AE5.7090607@mozilla-enigmail.org>
Message-ID: <49B621CA.5070003@gmx.net>

Hi Patrick!
Thanks a lot for your tip.

I open a shell, "unset GPG_AGENT_INFO" and execute Thunderbird
afterwards in the same shell. This solves the problem for me. I can use
the OpenPGP card without a problem. :-)

For my understanding the problem is that Seahorse does not support
smartcards but is used in Ubuntu as the default way for PIN handling.
Also disabling the option to use GPG Agent in Enigmail does not work for
any reason. If using smart cards, Seahorse does not work but GnuPG
itself would do a better job. So two questions are remaining:

1. I wouldn't like each time to start a shell, unset GPG_AGENT_INFO and
execute Thunderbird afterwards. There should be a more elegant
workaround. For my understanding unsetting GPG_AGENT_INFO in ~/.profile
 would not be a good solution because Seahorse may be appropriate in
other cases. So I would like to unset GPG_AGENT_INFO for Thunderbird
only. Maybe it is possible to define a alias "thunderbird" which unsets
the variable before executing the application? Or any other elegant
solution?

2. Should/Could this problem be fixed in Enigmail?

Best regards
Stefan

Patrick Brunschwig schrieb:
> Stefan X wrote:
>> Olav Seyfarth schrieb:
>>> Hi Stefan,
>>>
>>>> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
>>>> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
>>> Could you please disable "use GPG agent" in OpenPGP advanced settings and
>>> try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
>>> might also try using GnuPG 2.x and reenable "use GPG agent".
>>>
>>> Olav
>> Hi Olav,
>> the funny thing is, "use GPG agent" is already DISABLED! What to do?
> 
> 
> 
> Please don't top-post. To disable the use of gpg-agent, unset the
> environment variavle GPG_AGENT_INFO.
> 
> -Patrick
_______________________________________________
Enigmail mailing list
Enigmail at mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail


From patrick at mozilla-enigmail.org  Tue Mar 10 01:59:47 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Tue, 10 Mar 2009 09:59:47 +0100
Subject: [Enigmail] OpenPGP Card: fundamental problems
In-Reply-To: <49B621CA.5070003@gmx.net>
References: <49B3CF04.90806@gmx.net>	<49B3D068.7070201@mozilla-enigmail.org>	<49B3DAB6.8030607@gmx.net>	<49B3EF37.4070304@mozilla-enigmail.org>	<49B3FEF6.7080704@gmx.net>	<49B50AE5.7090607@mozilla-enigmail.org>
	<49B621CA.5070003@gmx.net>
Message-ID: <49B62C03.6030103@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Stefan X wrote:
>>>>> 2009-03-08 15:38:18.802 enigmail.js: detectGpgAgent:
>>>>> GPG_AGENT_INFO='/tmp/seahorse-axoWSa/S.gpg-agent:5551:1'
>>>> Could you please disable "use GPG agent" in OpenPGP advanced settings and
>>>> try again? I suspect it's a problem between GnuPG 1.4.9 and seahorse. You
>>>> might also try using GnuPG 2.x and reenable "use GPG agent".
>>>>
>>>> Olav
>>> Hi Olav,
>>> the funny thing is, "use GPG agent" is already DISABLED! What to do?
>>
>>
>> Please don't top-post. To disable the use of gpg-agent, unset the
>> environment variavle GPG_AGENT_INFO.
>
> Hi Patrick!
> Thanks a lot for your tip.
>
> I open a shell, "unset GPG_AGENT_INFO" and execute Thunderbird
> afterwards in the same shell. This solves the problem for me. I can use
> the OpenPGP card without a problem. :-)
>
> For my understanding the problem is that Seahorse does not support
> smartcards but is used in Ubuntu as the default way for PIN handling.
> Also disabling the option to use GPG Agent in Enigmail does not work for
> any reason. If using smart cards, Seahorse does not work but GnuPG
> itself would do a better job. So two questions are remaining:
>
> 1. I wouldn't like each time to start a shell, unset GPG_AGENT_INFO and
> execute Thunderbird afterwards. There should be a more elegant
> workaround. For my understanding unsetting GPG_AGENT_INFO in ~/.profile
>  would not be a good solution because Seahorse may be appropriate in
> other cases. So I would like to unset GPG_AGENT_INFO for Thunderbird
> only. Maybe it is possible to define a alias "thunderbird" which unsets
> the variable before executing the application? Or any other elegant
> solution?

I'd create a shell script that unsets GPG_AGENT_INFO, or (actually
better): use gpg-agent instead of Seahorse-agent.

> 2. Should/Could this problem be fixed in Enigmail?

No, have defined that if GPG_AGENT_INFO is available, then gpg-agent
must be used. For GnuPG v2.x you cannot live without any gpg-agent anyway.

- -Patrick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSbYsAncOpHodsOiwAQhv1Qf9FV2ofxZqlFARxruuI+thxUeq6Ej3w8UI
4PtLo6MhVkOjqcUTPduU7GDlVPR88OochUU9JZ9NFHUkhFhQeFP5iiybmBU+3CLs
AiCGexv94895J6k60gGzs/H49gJ/J80GRVTMoBYZB+iAA1PydmJfinkypqUgYr/m
GaVaxFc9Ezze1iTTXbsTOK/gPPvaf96mnKDrwhFDNcrOqhRaaIapyw/IMiuFzbHn
X/HsCVZDL0WqW56YF3X5fXDqEO0qm3MCGqqTM3qd6ptOdmSohVWNuHU/Fl0wg8gH
6gIqIJuPqJVWT9q34jmeOImajuRm1StboYj3lk6v/ckkyWyeDtVjbg==
=Xr8k
-----END PGP SIGNATURE-----

From dkg at fifthhorseman.net  Fri Mar 13 13:50:37 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Fri, 13 Mar 2009 16:50:37 -0400
Subject: [Enigmail] building the IPC library with xulrunner-dev instead of a
 full build tree
Message-ID: <49BAC71D.6010607@fifthhorseman.net>

howdy enigmail folks--

I'm new to the build process for enigmail, so this question itself might
be full of errors or misconceptions.  I'd be grateful for any
corrections people have.

Until mozilla bug 68702 [0] is closed, i'm trying to sort out a simple
way to make sure that the IPC extension to the mozilla suite can be
cleanly packaged and redistributed.  I want to see this happen because i
want to see both engimail and firegpg well-supported by free software
distributions (i'm focusing in particular on debian), and both of these
packages appear to depend on this extension.

The problem that i've run into is that most instructions to build the
IPC library (e.g. [1]) suggest building it from within a pre-built (or
half-built) mozilla source tree.

The way that debian (and ubuntu and other debian derivatives) build ad
distribute binary versions makes this kind of approach awkward and
difficult to maintain as long as the IPC library being adopted upstream.
 It's difficult (and discouraged, for maintenance and security reasons)
to use the source from package A during the build for package B.

However, debian distributes a xulrunner-dev package which appears to be
intended in part to support builds of xpcom extensions (i believe this
is also known as gecko SDK).  The ipc library is technically an xpcom
extension, right?

So: would it be possible to build the ipc extension against
xulrunner-dev directly, without setting up a full mozilla build-tree and
half-configuring it?  I'd be happy to experiment with ways to do that,
if anyone can point me in the right direction.

I've tried already with no success, but i have no experience building
xpcom extensions, and i'm leery of superstitiously tampering with the
source just to get the build to work smoothly.  The latest version i
could find [1] does compile cleanly if i have a pre-compiled external
source tree, i just want to make it build from the system-installed
development headers instead.  Is this trivial to do, and i'm just
ignorant of the switches/settings to use?  Or am i chasing a
fundamentally impossible goal?

Thanks for any advice you can give.  I'm happy to answer questions or to
clarify if what i've written makes no sense.

Regards,

	--dkg

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=68702
[1] http://blog.getfiregpg.org/2008/10/17/how-to-compile-the-ipc-library/
[2] http://mozilla-enigmail.org/ipc/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090313/4e508445/attachment.bin>

From Liste at FamilleCollet.com  Sun Mar 15 10:46:15 2009
From: Liste at FamilleCollet.com (Remi Collet)
Date: Sun, 15 Mar 2009 18:46:15 +0100
Subject: [Enigmail] Fedora + TB 3.0b2 + Enigmail 0.96a (2009-03-15)
Message-ID: <49BD3EE7.8030006@FamilleCollet.com>

Hi,

I just build enigmail 0.96a (today CVS snapshot) against thunderbird
3.0b2 (SRPM from fedora rawhide)

All build and install correctly (i386 + x86_64 without any additional
patch like the one required for TH2).

Run fine in English, but not in french (no menu, no prefs, ..)
It seems to be an issue with partially translated file.

Have you some informations about the translation status ?

Regards
Remi.



P.S. Build process (a few differences from TH2, because of OBJDIR use):

make -f client.mk export
pushd objdir-tb/mozilla/modules/libreg
make
cd ../../xpcom/string
make
cd ..
make
cd obsolete
make
popd

pushd mailnews/extensions/enigmail
./makemake -r
popd

pushd objdir-tb/mailnews/extensions/enigmail
make
make xpi
popd

From mlisten at hammernoch.net  Sun Mar 15 12:31:22 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Sun, 15 Mar 2009 20:31:22 +0100
Subject: [Enigmail] Fedora + TB 3.0b2 + Enigmail 0.96a (2009-03-15)
In-Reply-To: <49BD3EE7.8030006@FamilleCollet.com>
References: <49BD3EE7.8030006@FamilleCollet.com>
Message-ID: <49BD578A.1090707@hammernoch.net>

Hi,

Remi Collet wrote on 15.03.2009 18:46 Uhr:
> Hi,
> 
> I just build enigmail 0.96a (today CVS snapshot) against thunderbird
> 3.0b2 (SRPM from fedora rawhide)
> 
> All build and install correctly (i386 + x86_64 without any additional
> patch like the one required for TH2).
> 
> Run fine in English, but not in french (no menu, no prefs, ..)
> It seems to be an issue with partially translated file.
> 
> Have you some informations about the translation status ?

Enigmail trunk is almost never translated fully. I'm confident that this
will be fixed for a enigmail release suitable for the upcoming TB3. I
think Patrick will call for translators when the rest of the code is
stable enough for a release, if needed.

And, as always with open source projects, patches are welcome :-)

Greetings

Ludwig

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 542 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090315/3dd04050/attachment.bin>

From patrick at mozilla-enigmail.org  Mon Mar 16 02:02:45 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Mon, 16 Mar 2009 10:02:45 +0100
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BAC71D.6010607@fifthhorseman.net>
References: <49BAC71D.6010607@fifthhorseman.net>
Message-ID: <49BE15B5.5060103@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Daniel Kahn Gillmor wrote:
> howdy enigmail folks--
> 
[...]
> 
> However, debian distributes a xulrunner-dev package which appears to be
> intended in part to support builds of xpcom extensions (i believe this
> is also known as gecko SDK).  The ipc library is technically an xpcom
> extension, right?

correct.

> So: would it be possible to build the ipc extension against
> xulrunner-dev directly, without setting up a full mozilla build-tree and
> half-configuring it?  I'd be happy to experiment with ways to do that,
> if anyone can point me in the right direction.

I think it should be technically possible, even though I have never
tried it.

> I've tried already with no success, but i have no experience building
> xpcom extensions, and i'm leery of superstitiously tampering with the
> source just to get the build to work smoothly.  The latest version i
> could find [1] does compile cleanly if i have a pre-compiled external
> source tree, i just want to make it build from the system-installed
> development headers instead.  Is this trivial to do, and i'm just
> ignorant of the switches/settings to use?  Or am i chasing a
> fundamentally impossible goal?

I think it's not trivial at all. If I were you, I'd try to find out how
Enigmail is built on Debian (i.e. download the Enigmail source package
of Debian) and follow the way it's done there.

HTH,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSb4VsHcOpHodsOiwAQiX5Af+KeUPh7z6QRQSmDJeBXCiEuCviOHSL4ja
rQ4JXzwIm1mwi6FIT4VHcq86kbrXcFieQYrcuCcT8o8ESjJYCLIP2kyDSPQ2oiEk
rniXbp9ufIxUaCDlx1PGoxOBkU9j0j3LpmfwMGoHNN0aphBe4WqzWMBJ/0NbAQUi
8FhsmHWm6e2Dcyo2yAmolZEmYlzCEt6BQyxKqUBth05c5seXxtzPpCmWps19oZEP
HLqZgwHYDP9b+ILzTN5HXo6g1Kdy2Xn01SsU4k5qheDqeamfNcE1hP7gJlEGu9A0
jRN4O284zsVHpg6ZDGsx1dRxO1UgWJSWnApRghmL1DmHeWZ0XzXJaQ==
=F8e1
-----END PGP SIGNATURE-----

From Liste at FamilleCollet.com  Mon Mar 16 12:38:37 2009
From: Liste at FamilleCollet.com (Remi Collet)
Date: Mon, 16 Mar 2009 20:38:37 +0100
Subject: [Enigmail] Fedora + TB 3.0b2 + Enigmail 0.96a (2009-03-15)
In-Reply-To: <49BD578A.1090707@hammernoch.net>
References: <49BD3EE7.8030006@FamilleCollet.com>
	<49BD578A.1090707@hammernoch.net>
Message-ID: <49BEAABD.8050806@FamilleCollet.com>

Le 15/03/2009 20:31, Ludwig H?gelsch?fer a ?crit :

> Enigmail trunk is almost never translated fully. I'm confident that this
> will be fixed for a enigmail release suitable for the upcoming TB3. I
> think Patrick will call for translators when the rest of the code is
> stable enough for a release, if needed.

I think I perfectly understand how work such a OpenSource project.

> 
> And, as always with open source projects, patches are welcome :-)

My goal is not to have a french (or other) translation complete (and I
don't think I will be a good translator), it's to provide (as I'm used
to do) a working package of enigmail "in all languages" for Fedora Users
for most versions (from FC4) and most architectures (i386, x86_64, ppc
and ppc64)

So, I quickly write a small and dirty script which check each lang file
(enigmail.dtd and enimail.properties) and add the missing strings (from
then english reference file).

The result is a working extension in all languages (well, of course with
some english messages).

The script is attached.
Written in PHP (sorry, but that's the simplest language for me)

And before building enigmail, I run :

	cd mailnews/extensions/enigmail
	for rep in $(cat lang/current-languages.txt)
	do
		dos2unix lang/$rep/enigmail.dtd
		dos2unix lang/$rep/enigmail.properties
		php enigmail-fixlang.php ui/locale/en-US lang/$rep
	done

Hope it could help others.

Regards
Remi.

P.S. http://blog.famillecollet.com/en
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: enigmail-fixlang.php
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090316/2b51ecf0/attachment.ksh>

From mlisten at hammernoch.net  Mon Mar 16 13:32:55 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Mon, 16 Mar 2009 21:32:55 +0100
Subject: [Enigmail] Fedora + TB 3.0b2 + Enigmail 0.96a (2009-03-15)
In-Reply-To: <49BEAABD.8050806@FamilleCollet.com>
References: <49BD3EE7.8030006@FamilleCollet.com>	<49BD578A.1090707@hammernoch.net>
	<49BEAABD.8050806@FamilleCollet.com>
Message-ID: <49BEB777.7080609@hammernoch.net>

Remi Collet wrote on 16.03.2009 20:38 Uhr:
(...)
> 
> My goal is not to have a french (or other) translation complete (and I
> don't think I will be a good translator), it's to provide (as I'm used
> to do) a working package of enigmail "in all languages" for Fedora Users
> for most versions (from FC4) and most architectures (i386, x86_64, ppc
> and ppc64)
> 
> So, I quickly write a small and dirty script which check each lang file
> (enigmail.dtd and enimail.properties) and add the missing strings (from
> then english reference file).
> 
> The result is a working extension in all languages (well, of course with
> some english messages).

(...)

> Hope it could help others.

Thanks a lot, I'll have a try for building the enigmail nightly for Mac
OS X.

Ludwig



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 542 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090316/0d7d5f73/attachment.bin>

From dkg at fifthhorseman.net  Mon Mar 16 15:38:20 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Mon, 16 Mar 2009 18:38:20 -0400
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BE15B5.5060103@mozilla-enigmail.org>
References: <49BAC71D.6010607@fifthhorseman.net>
	<49BE15B5.5060103@mozilla-enigmail.org>
Message-ID: <49BED4DC.8040103@fifthhorseman.net>

Hi Patrick--

Thanks for the quick feedback!

On 03/16/2009 05:02 AM, Patrick Brunschwig wrote:
> I think it's not trivial at all. If I were you, I'd try to find out how
> Enigmail is built on Debian (i.e. download the Enigmail source package
> of Debian) and follow the way it's done there.

Yeah, i've looked at that.  It looks like they ship a snapshot of a
pruned mozilla build tree along with all the ipc source, so that they
can unpack into it and rebuild in there.  Seems like a kind of messy way
to do things, and "courtesy copies" of external code are discouraged by
debian policy anyway these days.

I've gotten further in my experimentation now than i did when i wrote
first, based tracing an in-tree build and a lot of searching the web.
i'm almost to the point of having libipc.so built, actually (though of
course i haven't tested the output).  The problem that i'm running into
is manifesting itself as a linker error at the last stage of the build.
 I've attached a gzipped tarball of the Makefiles i've cooked up that
appear to get it to build properly all the way through, but the linking
stage itself fails.  I've included the spew from the make process as
well in case anyone wants to take a look.

The problem i'm having looks a lot like http://bugs.debian.org/442966,
but the patches in that report don't seem to fix things for me.

> c++ -Wall -Wconversion -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-long-long -Os -g -o libipc.so -include mozilla-config.h -include xpcom-config.h -DXPCOM_GLUE -DXPCOM_GLUE_USE_NSPR -I /usr/lib/xulrunner-devel-1.9/include -I ../src -I ../public -L /usr/lib/xulrunner-devel-1.9/lib -L /usr/lib/xulrunner-devel-1.9/bin -Wl,-rpath-link,/usr/lib/xulrunner-devel-1.9/bin -lxpcom -lxul -lnspr4 -lplds4 -lplc4 -lpthread -ldl -lnss3 -Wl,-z,defs -Wl,-h,libipc.so -Wl,--as-needed -Wl,--whole-archive ../src/libipc_s.a -Wl,--no-whole-archive /usr/lib/xulrunner-devel-1.9/sdk/lib/libxpcomglue_s.a -Wl,--version-script -Wl,components-version-script -Wl,-Bsymbolic -fno-rtti -fno-exceptions -shared -fPIC -pthread -pipe -fvisibility=hidden   nsIPCModule.o
> nsIPCModule.o: In function `NSGetModule':
> /home/builder/src/xulrunner-ipc/ipc/build/nsIPCModule.cpp:104: undefined reference to `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)'
> /usr/bin/ld: libipc.so: hidden symbol `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)' isn't defined
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: ld returned 1 exit status

Unfortunately, i don't really understand hidden visibility symbols in
XPCOM well enough to brute force my way through this.  Any advice would
be welcome!  I'm also happy to give interested people access to a
minimal debian sid development environment with all the build-deps
satisfied if anyone wants to poke around themselves.

Please let me know if you see me doing anything particularly horrible in
these makefiles, or if you have suggestions that you think would be better.

Regards,

	--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian-xulrunner-ipc-makefiles.tgz
Type: application/x-gtar
Size: 2712 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090316/3ce75da3/attachment.gtar>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make-spew.gz
Type: application/gzip
Size: 1796 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090316/3ce75da3/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090316/3ce75da3/attachment-0001.bin>

From andy.ruddock at rainydayz.org  Mon Mar 16 21:59:25 2009
From: andy.ruddock at rainydayz.org (Andy Ruddock)
Date: Tue, 17 Mar 2009 05:59:25 +0100
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BED4DC.8040103@fifthhorseman.net>
References: <49BAC71D.6010607@fifthhorseman.net>	<49BE15B5.5060103@mozilla-enigmail.org>
	<49BED4DC.8040103@fifthhorseman.net>
Message-ID: <49BF2E2D.1070504@rainydayz.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Kahn Gillmor wrote:
> Hi Patrick--
> 
> Thanks for the quick feedback!
> 
> On 03/16/2009 05:02 AM, Patrick Brunschwig wrote:
>> I think it's not trivial at all. If I were you, I'd try to find out how
>> Enigmail is built on Debian (i.e. download the Enigmail source package
>> of Debian) and follow the way it's done there.
> 
> Yeah, i've looked at that.  It looks like they ship a snapshot of a
> pruned mozilla build tree along with all the ipc source, so that they
> can unpack into it and rebuild in there.  Seems like a kind of messy way
> to do things, and "courtesy copies" of external code are discouraged by
> debian policy anyway these days.
> 
> I've gotten further in my experimentation now than i did when i wrote
> first, based tracing an in-tree build and a lot of searching the web.
> i'm almost to the point of having libipc.so built, actually (though of
> course i haven't tested the output).  The problem that i'm running into
> is manifesting itself as a linker error at the last stage of the build.
>  I've attached a gzipped tarball of the Makefiles i've cooked up that
> appear to get it to build properly all the way through, but the linking
> stage itself fails.  I've included the spew from the make process as
> well in case anyone wants to take a look.
> 
> The problem i'm having looks a lot like http://bugs.debian.org/442966,
> but the patches in that report don't seem to fix things for me.
> 
>> c++ -Wall -Wconversion -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-long-long -Os -g -o libipc.so -include mozilla-config.h -include xpcom-config.h -DXPCOM_GLUE -DXPCOM_GLUE_USE_NSPR -I /usr/lib/xulrunner-devel-1.9/include -I ../src -I ../public -L /usr/lib/xulrunner-devel-1.9/lib -L /usr/lib/xulrunner-devel-1.9/bin -Wl,-rpath-link,/usr/lib/xulrunner-devel-1.9/bin -lxpcom -lxul -lnspr4 -lplds4 -lplc4 -lpthread -ldl -lnss3 -Wl,-z,defs -Wl,-h,libipc.so -Wl,--as-needed -Wl,--whole-archive ../src/libipc_s.a -Wl,--no-whole-archive /usr/lib/xulrunner-devel-1.9/sdk/lib/libxpcomglue_s.a -Wl,--version-script -Wl,components-version-script -Wl,-Bsymbolic -fno-rtti -fno-exceptions -shared -fPIC -pthread -pipe -fvisibility=hidden   nsIPCModule.o
>> nsIPCModule.o: In function `NSGetModule':
>> /home/builder/src/xulrunner-ipc/ipc/build/nsIPCModule.cpp:104: undefined reference to `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)'
>> /usr/bin/ld: libipc.so: hidden symbol `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)' isn't defined
>> /usr/bin/ld: final link failed: Nonrepresentable section on output
>> collect2: ld returned 1 exit status
> 
> Unfortunately, i don't really understand hidden visibility symbols in
> XPCOM well enough to brute force my way through this.  Any advice would
> be welcome!  I'm also happy to give interested people access to a
> minimal debian sid development environment with all the build-deps
> satisfied if anyone wants to poke around themselves.
> 
> Please let me know if you see me doing anything particularly horrible in
> these makefiles, or if you have suggestions that you think would be better.
> 

I came across this whilst trying to build enigmail for SeaMonkey,
there's a thread about it here :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442966

Maybe including the same #pragma lines in nsIPCMoule.cpp would fix it?

- --
Andy Ruddock
- ------------
andy.ruddock at rainydayz.org (GPG Key ID 0xA622D452)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm/LikACgkQfSkWkaYi1FJC7ACgg792cC1ynAI0ucRQzG7xob8e
X8oAn0jLpwgXREC6inecJ6Cu1IBuRdey
=xLrA
-----END PGP SIGNATURE-----

From dkg at fifthhorseman.net  Tue Mar 17 07:01:39 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 17 Mar 2009 10:01:39 -0400
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BF2E2D.1070504@rainydayz.org>
References: <49BAC71D.6010607@fifthhorseman.net>	<49BE15B5.5060103@mozilla-enigmail.org>	<49BED4DC.8040103@fifthhorseman.net>
	<49BF2E2D.1070504@rainydayz.org>
Message-ID: <49BFAD43.5080106@fifthhorseman.net>

Hi Andy--

On 03/17/2009 12:59 AM, Andy Ruddock wrote:
> Daniel Kahn Gillmor wrote:
>> The problem i'm having looks a lot like http://bugs.debian.org/442966,
>> but the patches in that report don't seem to fix things for me.
> 
> I came across this whilst trying to build enigmail for SeaMonkey,
> there's a thread about it here :
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442966
> 
> Maybe including the same #pragma lines in nsIPCMoule.cpp would fix it?

Thanks for the suggestion!  I tried applying either or both patches from
442966, but am still getting the same errors:

> nsIPCModule.o: In function `NSGetModule':
> /home/builder/src/xulrunner-ipc/ipc/build/nsIPCModule.cpp:106: undefined reference to `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)'
> /usr/bin/ld: libipc.so: hidden symbol `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)' isn't defined

Where is NS_NewGenericModule2 supposed to be defined?  Is this something
that should be inherited from some other class?  linked in from some
static lib?  linked in from a shared object?

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090317/73a2f97c/attachment.bin>

From andy.ruddock at rainydayz.org  Tue Mar 17 07:46:50 2009
From: andy.ruddock at rainydayz.org (Andy Ruddock)
Date: Tue, 17 Mar 2009 15:46:50 +0100
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BFAD43.5080106@fifthhorseman.net>
References: <49BAC71D.6010607@fifthhorseman.net>	<49BE15B5.5060103@mozilla-enigmail.org>	<49BED4DC.8040103@fifthhorseman.net>	<49BF2E2D.1070504@rainydayz.org>
	<49BFAD43.5080106@fifthhorseman.net>
Message-ID: <49BFB7DA.9060307@rainydayz.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Kahn Gillmor wrote:
> Hi Andy--
> 
> On 03/17/2009 12:59 AM, Andy Ruddock wrote:
>> Daniel Kahn Gillmor wrote:
>>> The problem i'm having looks a lot like http://bugs.debian.org/442966,
>>> but the patches in that report don't seem to fix things for me.
>> I came across this whilst trying to build enigmail for SeaMonkey,
>> there's a thread about it here :
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442966
>>
>> Maybe including the same #pragma lines in nsIPCMoule.cpp would fix it?
> 
> Thanks for the suggestion!  I tried applying either or both patches from
> 442966, but am still getting the same errors:
> 
>> nsIPCModule.o: In function `NSGetModule':
>> /home/builder/src/xulrunner-ipc/ipc/build/nsIPCModule.cpp:106: undefined reference to `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)'
>> /usr/bin/ld: libipc.so: hidden symbol `NS_NewGenericModule2(nsModuleInfo const*, nsIModule**)' isn't defined
> 
> Where is NS_NewGenericModule2 supposed to be defined?  Is this something
> that should be inherited from some other class?  linked in from some
> static lib?  linked in from a shared object?
> 

If you document what's in your build tree and how you put it together
I'll try it here and see if I can get anywhere.

- --
Andy Ruddock
- ------------
andy.ruddock at rainydayz.org (GPG Key ID 0xA622D452)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm/t9cACgkQfSkWkaYi1FK6GgCgmurdn5K8SloUX0YJ4x9NakGx
NiIAn1/YfmSANT6bEa8TFz+vp5Aa1UCn
=zuad
-----END PGP SIGNATURE-----

From dkg at fifthhorseman.net  Tue Mar 17 08:13:46 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 17 Mar 2009 11:13:46 -0400
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BFB7DA.9060307@rainydayz.org>
References: <49BAC71D.6010607@fifthhorseman.net>	<49BE15B5.5060103@mozilla-enigmail.org>	<49BED4DC.8040103@fifthhorseman.net>	<49BF2E2D.1070504@rainydayz.org>	<49BFAD43.5080106@fifthhorseman.net>
	<49BFB7DA.9060307@rainydayz.org>
Message-ID: <49BFBE2A.1020807@fifthhorseman.net>

On 03/17/2009 10:46 AM, Andy Ruddock wrote:
> If you document what's in your build tree and how you put it together
> I'll try it here and see if I can get anywhere.

Thanks for your offer, Andy!  The tarball with my makefiles that run
against the (otherwise unmodified) source is in my earlier e-mail to
this list.  I've just published them to the web as well.

A simple shell script to duplicate my build environment is here:

 http://lair.fifthhorseman.net/~dkg/src/xulrunner-ipc/setup-build.sh

What the script does is:

 * check to make sure that the expected build-deps are available

 * fetch the upstream source and my makefiles, checking to make sure
they were downloaded intact

 * unpack the source, and unpack my makefiles into the unpacked source

 * run make.

Any suggestions for how to get the build to complete would be welcome!

Regards,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090317/b0bafead/attachment-0001.bin>

From dkg at fifthhorseman.net  Tue Mar 17 08:44:22 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 17 Mar 2009 11:44:22 -0400
Subject: [Enigmail] building the IPC library with xulrunner-dev instead
 of a full build tree
In-Reply-To: <49BFBE2A.1020807@fifthhorseman.net>
References: <49BAC71D.6010607@fifthhorseman.net>	<49BE15B5.5060103@mozilla-enigmail.org>	<49BED4DC.8040103@fifthhorseman.net>	<49BF2E2D.1070504@rainydayz.org>	<49BFAD43.5080106@fifthhorseman.net>	<49BFB7DA.9060307@rainydayz.org>
	<49BFBE2A.1020807@fifthhorseman.net>
Message-ID: <49BFC556.6030102@fifthhorseman.net>

On 03/17/2009 11:13 AM, Daniel Kahn Gillmor wrote:
> On 03/17/2009 10:46 AM, Andy Ruddock wrote:
>> If you document what's in your build tree and how you put it together
>> I'll try it here and see if I can get anywhere.
> 
> Thanks for your offer, Andy!  The tarball with my makefiles that run
> against the (otherwise unmodified) source is in my earlier e-mail to
> this list.  I've just published them to the web as well.

Aha!  I think i've found what i needed -- curiously, the resolution is
not related to visibility=hidden, but to the fact that the static
library libxpcomglue_s.a wasn't being fully included in the final linked
output.  Including libxpcomglue_s.a in the linker list after a
-Wl,--whole-archive argument seems to make it build fine.  I'll update
my published Makefiles shortly.

The resultant stripped libipc.so on amd64 is ~186KB, which is roughly
comparable to libenigmime.so from debian's experimental repo (~167KB on
i386), so i don't appear to be including anything too excessive.

I believe i'm on to the next step, which is sorting out the rest of the
libipc packaging arrangements.  For example, i need to sort out which
xpt files need to be exported for libipc.so to be available, and how to
make sure the extension is available for iceweasel and other
xulrunner-1.9 packages, including icedove (thunderbird) 3, whenever that
drops into debian.

Advice or suggestions are welcome.  Sorry for the flood of e-mails here
as i stumble my way through.  There might be more to come.

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090317/62f1fcdc/attachment.bin>

From ludovic at mozillamessaging.com  Wed Mar 18 03:14:48 2009
From: ludovic at mozillamessaging.com (Ludovic Hirlimann)
Date: Wed, 18 Mar 2009 11:14:48 +0100
Subject: [Enigmail] Solaris Sparc builds ?
Message-ID: <49C0C998.9010400@mozillamessaging.com>

I was wondering if the Solaris build offered for download was also 
available on the sun4u platform - ie Sparc powered Solaris ?


ludovic

-- 
Ludovic Hirlimann MozillaMessaging QA lead
http://www.spreadthunderbird.com/aff/79/2

From patrick at mozilla-enigmail.org  Wed Mar 18 03:58:54 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Wed, 18 Mar 2009 11:58:54 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C0C998.9010400@mozillamessaging.com>
References: <49C0C998.9010400@mozillamessaging.com>
Message-ID: <49C0D3EE.30603@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ludovic Hirlimann wrote:
> I was wondering if the Solaris build offered for download was also
> available on the sun4u platform - ie Sparc powered Solaris ?

Did you check here: <http://enigmail.mozdev.org/download/index.php> ?

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBScDT7XcOpHodsOiwAQhneAf/azvWfHxWDneQ3G5VsJxLXZZxdafPmmvu
fAlu0fHzZ6fP89pgSXbNaCmH4OPEVc0xd7IYoSkSiEIrbJYIjDbC9hC8qIZYKxIW
g+fY4+GArHakfrYuUSQekf1gq7EhqZu9ZFPnQAMGEx+gd8TaC+3t6sq1Bfv2ya6R
i/4X/lGHWU24H5lbuzzmx+XXS3raGHINt8b8qk+GV9ni8ps3jsgW7oavZZob2ZRZ
bC6rtPKSOK2oSQ1pUjeQJ0TfRm3FFBAJ3JqYmalds/JdpQJt2Gngezsegc9bekWK
AAFXgm37x2qcqy8GPtPIOQdjQuopGQJERZNNUp4+pJVdXsmlwBMudA==
=unvZ
-----END PGP SIGNATURE-----

From ludovic at mozillamessaging.com  Wed Mar 18 04:03:14 2009
From: ludovic at mozillamessaging.com (Ludovic Hirlimann)
Date: Wed, 18 Mar 2009 12:03:14 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C0D3EE.30603@mozilla-enigmail.org>
References: <49C0C998.9010400@mozillamessaging.com>
	<49C0D3EE.30603@mozilla-enigmail.org>
Message-ID: <49C0D4F2.9020405@mozillamessaging.com>

On 3/18/09 11:58 AM, Patrick Brunschwig wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Ludovic Hirlimann wrote:
>
>> I was wondering if the Solaris build offered for download was also
>> available on the sun4u platform - ie Sparc powered Solaris ?
>>
> Did you check here:<http://enigmail.mozdev.org/download/index.php>  ?
>

I did - it says Solaris doesn't say if it's sparc or x86 ....

Ludovic

-- 
Ludovic Hirlimann MozillaMessaging QA lead
http://www.spreadthunderbird.com/aff/79/2

From mlisten at hammernoch.net  Wed Mar 18 04:05:05 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Wed, 18 Mar 2009 12:05:05 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C0D4F2.9020405@mozillamessaging.com>
References: <49C0C998.9010400@mozillamessaging.com>	<49C0D3EE.30603@mozilla-enigmail.org>
	<49C0D4F2.9020405@mozillamessaging.com>
Message-ID: <49C0D561.8020002@hammernoch.net>

Ludovic Hirlimann wrote on 18.03.2009 12:03 Uhr:
> On 3/18/09 11:58 AM, Patrick Brunschwig wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Ludovic Hirlimann wrote:
>>
>>> I was wondering if the Solaris build offered for download was also
>>> available on the sun4u platform - ie Sparc powered Solaris ?
>>>
>> Did you check here:<http://enigmail.mozdev.org/download/index.php>  ?
>>
> 
> I did - it says Solaris doesn't say if it's sparc or x86 ....

Have a look at http://drwetter.org/software/enigmail/,

there are SPARC versions available.

Ludwig

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 550 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090318/8a8f079a/attachment.bin>

From patrick at mozilla-enigmail.org  Wed Mar 18 04:06:13 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Wed, 18 Mar 2009 12:06:13 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C0D4F2.9020405@mozillamessaging.com>
References: <49C0C998.9010400@mozillamessaging.com>	<49C0D3EE.30603@mozilla-enigmail.org>
	<49C0D4F2.9020405@mozillamessaging.com>
Message-ID: <49C0D5A5.9070709@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ludovic Hirlimann wrote:
> On 3/18/09 11:58 AM, Patrick Brunschwig wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Ludovic Hirlimann wrote:
>>
>>> I was wondering if the Solaris build offered for download was also
>>> available on the sun4u platform - ie Sparc powered Solaris ?
>>>
>> Did you check here:<http://enigmail.mozdev.org/download/index.php>  ?
>>
> 
> I did - it says Solaris doesn't say if it's sparc or x86 ....

if you look at the download link, it says:
http://www.mozilla-enigmail.org/download/release/0.95/enigmail-0.95.1-sunos5-sparc.xpi

i.e. Sparc :-)

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBScDVpXcOpHodsOiwAQi0MAf/SGoj2M9oWleWwIE7ezSI/rDpRjSgKLaD
ULCdIVfRKFNedmiCNczSoZFeQez97XjID6vPKFJl22ObY/LKmt2QVYoXjwnwKhYS
WYnfHtod5TrmOeBdSatkvmxFpL7Be/mY3TsvHEKHgBgmd9d5sTyBulHdT+B+NVLi
oe/XgJqzy5aPK52Dd7Yy3zcIYbW4n5VVVmV+9AXZZK3zyVTvsl1CNKDaaYRXvK5z
C5ObvmoYglUEFNQdCBO8+/VivmRyeb6s7UOXQhd6lRlroBilm18PdyeYHQFE+kX2
ZUAPQfVeIRqoDSJ/aIpJK/Td7KF+Cq78bQ0YovAIO1FQGR/MiJX0aA==
=dzGj
-----END PGP SIGNATURE-----

From asac at jwsdot.com  Wed Mar 18 05:50:18 2009
From: asac at jwsdot.com (Alexander Sack)
Date: Wed, 18 Mar 2009 13:50:18 +0100
Subject: [Enigmail] building the IPC library with xulrunner-dev
	instead	of a full build tree
In-Reply-To: <49BED4DC.8040103@fifthhorseman.net>
References: <49BAC71D.6010607@fifthhorseman.net>
	<49BE15B5.5060103@mozilla-enigmail.org>
	<49BED4DC.8040103@fifthhorseman.net>
Message-ID: <20090318125017.GB6591@jwsdot.com>

Hi all,

(I got pointed to this thread through private mail; since i did the
enigmail package in debian,i think its worthwhile to provide my ideas
on this thing ... so here we go ..)

On Mon, Mar 16, 2009 at 06:38:20PM -0400, Daniel Kahn Gillmor wrote:
> Hi Patrick--
> 
> Thanks for the quick feedback!
> 
> On 03/16/2009 05:02 AM, Patrick Brunschwig wrote:
> > I think it's not trivial at all. If I were you, I'd try to find out how
> > Enigmail is built on Debian (i.e. download the Enigmail source package
> > of Debian) and follow the way it's done there.
> 
> Yeah, i've looked at that.  It looks like they ship a snapshot of a
> pruned mozilla build tree along with all the ipc source, so that they
> can unpack into it and rebuild in there.  Seems like a kind of messy way
> to do things, and "courtesy copies" of external code are discouraged by
> debian policy anyway these days.

Yes, we ship the mozilla build system; also we do that in quite a
hacky way - mostly because i supported building against mozilla and
thunderbird from the same tree.

BTW, its not a problem to ship that copy in debian. It doesnt conflict
with policy either imo, because the copied code is really just used at
build time and so there are no duplicated security risks (which is the
main reason why policy discourages that).

Anyway, I agree that we should do something finally.

We (the ubuntu mozillateam) have an effort to ease the way xulapps are
built. While extensions or individual components are not exactly the
same, most issues should match and I always wanted to ensure that
components and extensions can also benefit from this.

The current approach is shipping the build system as part of the
xulrunner sdk. This hasn't landed upstream yet and there definitly is
work left before that can happen, but upstream has signalled that they
would like something like that in the xulrunner sdk, so it seems the
way to go.

If you want to join our efforts, feel free to lurk on
#ubuntu-mozillateam. Me (asac) and fta are the right contacts to get
things started.

The other point (not ipc) is that there are thunderbird/mailnews
specific headers required for enigmail. We should also work on either
getting that code moved to xulrunner sdk or poke thunderbird devs
about officially providing a thunderbird sdk.


 - Alexander


From classpath at arcor.de  Thu Mar 19 17:06:07 2009
From: classpath at arcor.de (Morten Gulbrandsen)
Date: Fri, 20 Mar 2009 01:06:07 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C0D5A5.9070709@mozilla-enigmail.org>
References: <49C0C998.9010400@mozillamessaging.com>	<49C0D3EE.30603@mozilla-enigmail.org>	<49C0D4F2.9020405@mozillamessaging.com>
	<49C0D5A5.9070709@mozilla-enigmail.org>
Message-ID: <49C2DDEF.2070502@arcor.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick Brunschwig wrote:
> Ludovic Hirlimann wrote:
>> On 3/18/09 11:58 AM, Patrick Brunschwig wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>> Ludovic Hirlimann wrote:
>>>
>>>> I was wondering if the Solaris build offered for download was also
>>>> available on the sun4u platform - ie Sparc powered Solaris ?
>>>>
>>> Did you check here:<http://enigmail.mozdev.org/download/index.php>  ?
>>>
>> I did - it says Solaris doesn't say if it's sparc or x86 ....
> 
> if you look at the download link, it says:
> http://www.mozilla-enigmail.org/download/release/0.95/enigmail-0.95.1-sunos5-sparc.xpi
> 
> i.e. Sparc :-)
> 
> -Patrick

Dear Mr. Brunschwig

I'd like to see it for NetBSD 4.0 AMD64,
please?



Sincerely  Yours

Morten





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: For keyID and its URL see the OpenPGP message header

iEYEARECAAYFAknC3e8ACgkQ9ymv2YGAKVQI0ACgjd5UO7mUxaRwVAgXOmY+Y2Bk
mdoAoMKf74maMHnU/dYu0Akm4R5nyssV
=eCcE
-----END PGP SIGNATURE-----

From olav at mozilla-enigmail.org  Thu Mar 19 17:12:39 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Fri, 20 Mar 2009 01:12:39 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C2DDEF.2070502@arcor.de>
References: <49C0C998.9010400@mozillamessaging.com>	<49C0D3EE.30603@mozilla-enigmail.org>	<49C0D4F2.9020405@mozillamessaging.com>	<49C0D5A5.9070709@mozilla-enigmail.org>
	<49C2DDEF.2070502@arcor.de>
Message-ID: <49C2DF77.9080306@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Mr. Gulbrandsen,

> I'd like to see it for NetBSD 4.0 AMD64,please?

Unfortunately, we cannot provide builds for all platforms. if you can't find it
at http://www.mozilla-enigmail.org/download/release/0.95/ , nobody contributed
such a build yet. Please feel free to try yourself following the instructions
on http://enigmail.mozdev.org/download/source.php

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: http://privat.seyfarth.de/olav/schluessel.html

iEYEAREIAAYFAknC33YACgkQL/NBt8fdKe3gCQCgsr11JRCqkmZS50+Mvf0rb6YS
5bQAn1TQRRNGw7sjYiRTGfYRWmWmM7xA
=SKvK
-----END PGP SIGNATURE-----

From patrick at mozilla-enigmail.org  Fri Mar 20 02:25:22 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Fri, 20 Mar 2009 10:25:22 +0100
Subject: [Enigmail] Solaris Sparc builds ?
In-Reply-To: <49C2DDEF.2070502@arcor.de>
References: <49C0C998.9010400@mozillamessaging.com>	<49C0D3EE.30603@mozilla-enigmail.org>	<49C0D4F2.9020405@mozillamessaging.com>	<49C0D5A5.9070709@mozilla-enigmail.org>
	<49C2DDEF.2070502@arcor.de>
Message-ID: <49C36102.2020001@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Morten Gulbrandsen wrote:
> Patrick Brunschwig wrote:
>> Ludovic Hirlimann wrote:
>>> On 3/18/09 11:58 AM, Patrick Brunschwig wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>>
>>>> Ludovic Hirlimann wrote:
>>>>
>>>>> I was wondering if the Solaris build offered for download was also
>>>>> available on the sun4u platform - ie Sparc powered Solaris ?
>>>>>
>>>> Did you check here:<http://enigmail.mozdev.org/download/index.php>  ?
>>>>
>>> I did - it says Solaris doesn't say if it's sparc or x86 ....
>> if you look at the download link, it says:
>> http://www.mozilla-enigmail.org/download/release/0.95/enigmail-0.95.1-sunos5-sparc.xpi
> 
>> i.e. Sparc :-)
> 
>> -Patrick
> 
> Dear Mr. Brunschwig
> 
> I'd like to see it for NetBSD 4.0 AMD64,
> please?

I'm sorry, but I cannot provide builds for every possible combination of
hardware and operating systems -- I simply don't have the environment
nor the time for it. Don't forget that nobody working on Enigmail does
it as part of their job, we are all doing this in our free time. We are
ready to host any kind of build that we receive, but the builds need to
be contributed by volunteers.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBScNhAXcOpHodsOiwAQi+rgf6A7SY5YDqegkNUa1+n00eLzGF/z3FrEKr
hndUcSt8989X+WmN7Er2ZrfqyxY7M5qUCDhca4aitKYGL4xVqKrj52AcKXjhJk2c
45vrkaODhU9lEwfc8X4qhsl8n6lt6sBxLZdldCW1Ce1Gt8o3S5qszJA/TFX4IaY5
XmsClLiM3VG04OVRi92fG2E+uJUyfl4OEf3GOyywKr5PXyhBFuOmZekO+XmpHH08
+qG6f0NZFanHs4ygD5r3KUZ1G6QRaJsBnFbk7zOJpqjA6WLOT5suUHcnTiwiZ8nD
yz0mom6LGXEBdfFcA9NuxDfx4xp3iLuSITVgPrf+tp1NAdldmvQOew==
=5SMf
-----END PGP SIGNATURE-----

From cmeek at ocii.com  Thu Mar 19 17:50:47 2009
From: cmeek at ocii.com (Chet Meek)
Date: Thu, 19 Mar 2009 18:50:47 -0600
Subject: [Enigmail] Request for Help Testing Encryption in Enigmail using
 Thunderbird in WinXP
Message-ID: <49C2E867.10407@ocii.com>

Hi Enigmail list members,

I have sent a signed plaintext message to Adele,
and got a response back from their robot that
my signature was Ok. So I am signing this
inquiry too. My public key is on file
at |pool.sks-keyservers.net |and I am attaching it
to this message in case it is needed here too.

Now I would like to test sending and receiving
signed and encrypted messages.

Is there somebody on this list who is willing
to engage in exchanging a few trial messages?
If so. please send me a note, and tell me if
I should reply personally, or to the list, or what.

In case it helps ...
I am a retiree who wants greater confidentiality
in some email messages and to be able to decrypt
and reply to encrypted messages from others
using OpenPGP. I use Thunderbird under Windows XP
(with OpenPGP just installed); and I am right
at the limit of my computer literacy with this
installation, checkout, etc. I am not very confident
that it has all been done right.

Any help would be appreciated. And thank you.
And sorry for any inconvenience if this is not
the way to ask. I am very green.


  - Chet.

-- 
-----------------------------------------------------
Dorothy and Chet Meek          Voice:  780 + 433-6577
E-mail  Addresses: cdmeek at shaw.ca  OR  cmeek at ocii.com
On World Wide Web:              http://www.GoChet.ca/
... ...       and:     http://members.shaw.ca/cdmeek/
... ...       and:   http://internet.ocii.com/~cmeek/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xC0AEEE45.asc
Type: application/pgp-keys
Size: 1688 bytes
Desc: not available
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090319/b35e41c7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090319/b35e41c7/attachment-0001.bin>

From alaric at metrocast.net  Fri Mar 20 11:31:37 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Fri, 20 Mar 2009 14:31:37 -0400
Subject: [Enigmail] Request for Help Testing Encryption in Enigmail
 using Thunderbird in WinXP
In-Reply-To: <49C2E867.10407@ocii.com>
References: <49C2E867.10407@ocii.com>
Message-ID: <49C3E109.5050005@metrocast.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Chet Meek wrote:
> Hi Enigmail list members,
> 
> I have sent a signed plaintext message to Adele,
> and got a response back from their robot that
> my signature was Ok. So I am signing this
> inquiry too. My public key is on file
> at |pool.sks-keyservers.net |and I am attaching it
> to this message in case it is needed here too.
> 
> Now I would like to test sending and receiving
> signed and encrypted messages.
> 
> Is there somebody on this list who is willing
> to engage in exchanging a few trial messages?
> If so. please send me a note, and tell me if
> I should reply personally, or to the list, or what.


Well, to start with, I could not verify your signature:


OpenPGP Security Info

Error - signature verification failed

gpg command line and output:
/usr/bin/gpg --charset utf8  --batch --no-tty --status-fd 2 --verify
gpg: Signature made Thu Mar 19 20:50:52 2009 EDT using DSA key ID C0AEEE45
gpg: requesting key C0AEEE45 from hkp server wwwkeys.nl.pgp.net
gpg: key C0AEEE45: public key "Chet Meek <cmeek at ocii.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: BAD signature from "Chet Meek <cmeek at ocii.com>"



Are you CERTAIN you uploaded the correct key to the keyservers?



- --
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric at caerllewys.net   alaric at metrocast.net   phil at co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAknD4QkACgkQ0DfOju+hMknDeACgnCQ10EsLk3wPRH9Cda49Jztj
z24AoLEIwf54NDerJGkjMU4A8LDqdEao
=XDB8
-----END PGP SIGNATURE-----

From dkg at fifthhorseman.net  Fri Mar 20 21:16:11 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Sat, 21 Mar 2009 00:16:11 -0400
Subject: [Enigmail] xulrunner-ipc leaves file descriptors open in child
	process?
Message-ID: <49C46A0B.1040407@fifthhorseman.net>

Hi folks--

I've made significant progress in getting xulrunner-ipc to build cleanly
with a relatively simple makefile, to the point where i've event gotten
firegpg 0.7.5 working on GNU/linux on the powerpc(!)  I hope to publish
a bit of my revised build process soon, as i'd like it to be useful to
people other than myself.

I've been exploring its behavior, though, and i'm finding that the
spawned child process appears to retain a copy of all of the file
descriptors of the parent process.  Is this intentional?

Here's an example that i caught during a long-running child process
(this is firegpg creating a key):

> dkg at clam:~$ lsof -p 4333
> COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
> gpg     4333  dkg  cwd    DIR  254,3     4096  31746 /home/dkg
> gpg     4333  dkg  rtd    DIR    3,3     1024      2 /
> gpg     4333  dkg  txt    REG  254,2   940384  18117 /usr/bin/gpg
> gpg     4333  dkg  mem    REG    3,3   248532  81615 /lib/libncurses.so.5.7
> gpg     4333  dkg  mem    REG    3,3  1475220  81585 /lib/libc-2.9.so
> gpg     4333  dkg  mem    REG    3,3    39968  81489 /lib/libusb-0.1.so.4.4.4
> gpg     4333  dkg  mem    REG    3,3    13896  81594 /lib/libdl-2.9.so
> gpg     4333  dkg  mem    REG    3,3   255792  81446 /lib/libreadline.so.5.2
> gpg     4333  dkg  mem    REG    3,3    78760 148208 /lib/libbz2.so.1.0.4
> gpg     4333  dkg  mem    REG  254,2    86440  65892 /usr/lib/libz.so.1.2.3.3
> gpg     4333  dkg  mem    REG    3,3    83728  81607 /lib/libresolv-2.9.so
> gpg     4333  dkg  mem    REG    3,3   133784  81443 /lib/ld-2.9.so
> gpg     4333  dkg  mem    REG  254,2  1316224  66851 /usr/lib/locale/locale-archive
> gpg     4333  dkg    0r  FIFO    0,6      0t0 396833 pipe
> gpg     4333  dkg    1w  FIFO    0,6      0t0 396834 pipe
> gpg     4333  dkg    2w  FIFO    0,6      0t0 396835 pipe
> gpg     4333  dkg    3r   CHR    1,9      0t0    911 /dev/urandom
> gpg     4333  dkg    4r   CHR    1,8      0t0    905 /dev/random
> gpg     4333  dkg    6w   REG  254,3        0  32853 /home/dkg/.mozilla/firefox/jevgkzsj.default/.parentlock
> gpg     4333  dkg    7w   REG  254,3        0  32853 /home/dkg/.mozilla/firefox/jevgkzsj.default/.parentlock
> gpg     4333  dkg    8r  FIFO    0,6      0t0 396732 pipe
> gpg     4333  dkg    9r   CHR    1,9      0t0    911 /dev/urandom
> gpg     4333  dkg   10r  FIFO    0,6      0t0 396730 pipe
> gpg     4333  dkg   11r   CHR    1,9      0t0    911 /dev/urandom
> gpg     4333  dkg   12w  FIFO    0,6      0t0 396730 pipe
> gpg     4333  dkg   14w  FIFO    0,6      0t0 396732 pipe
> gpg     4333  dkg   15r   REG  254,2   142439   3147 /usr/share/iceweasel/chrome/en-US.jar
> gpg     4333  dkg   17r   REG  254,2  1910570   3149 /usr/share/iceweasel/chrome/browser.jar
> gpg     4333  dkg   19r   REG  254,2   332551   3036 /usr/share/xulrunner-1.9/chrome/en-US.jar
> gpg     4333  dkg   20r   REG  254,2   399489   3041 /usr/share/xulrunner-1.9/chrome/classic.jar
> gpg     4333  dkg   21r   REG  254,2  1931358   3037 /usr/share/xulrunner-1.9/chrome/toolkit.jar
> gpg     4333  dkg   23r   REG  254,2    39553   3162 /usr/share/iceweasel/chrome/reporter.jar
> gpg     4333  dkg   24r   REG  254,2   548457  69831 /usr/lib/mozilla-extensions/firegpg/chrome/firegpg.jar
> gpg     4333  dkg   25r   REG  254,2   178319   3151 /usr/share/iceweasel/chrome/classic.jar
> gpg     4333  dkg   27w  FIFO    0,6      0t0 396735 pipe
> gpg     4333  dkg   32u   REG  254,3     8468  32877 /home/dkg/.mozilla/firefox/jevgkzsj.default/Cache/_CACHE_MAP_
> gpg     4333  dkg   33r  FIFO    0,6      0t0 396738 pipe
> gpg     4333  dkg   34w  FIFO    0,6      0t0 396738 pipe
> gpg     4333  dkg   38u   REG  254,3     7310  32878 /home/dkg/.mozilla/firefox/jevgkzsj.default/Cache/_CACHE_001_
> gpg     4333  dkg   39u   REG  254,3    19264  32879 /home/dkg/.mozilla/firefox/jevgkzsj.default/Cache/_CACHE_002_
> gpg     4333  dkg   40u   REG  254,3     4096  32880 /home/dkg/.mozilla/firefox/jevgkzsj.default/Cache/_CACHE_003_
> gpg     4333  dkg   42u  IPv4 396823      0t0    TCP clam.lair.fifthhorseman.net:53191->yo-in-f113.google.com:www (CLOSE_WAIT)
> gpg     4333  dkg   48r  FIFO    0,6      0t0 396752 pipe
> gpg     4333  dkg   49w  FIFO    0,6      0t0 396752 pipe
> dkg at clam:~$ 

It seems like most of the open file descriptors are *not* file
descriptors that GnuPG would have opened on its own.  So i can only
assume that the file descriptors are inherited from the parent process.

This seems potentially sloppy -- what if there were three network
connections opened by the parent, and the child process was to start
manipulating them?  What about writing to the cache or adjusting the
already-open files somehow?  Wouldn't it make more sense to close all
file descriptors except the pipes before execing the child process?

Or is there some reason that the child process in xulrunner-ipc should
really have access to all of the parent's file descriptors?

Regards,

	--dkg


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090321/2ff2af0a/attachment.bin>

From bblackmoor at blackgate.net  Fri Mar 20 21:20:03 2009
From: bblackmoor at blackgate.net (Brandon Blackmoor)
Date: Sat, 21 Mar 2009 00:20:03 -0400
Subject: [Enigmail] Request for Help Testing Encryption in Enigmail
 using Thunderbird in WinXP
In-Reply-To: <49C2E867.10407@ocii.com>
References: <49C2E867.10407@ocii.com>
Message-ID: <49C46AF3.6070901@secure.blackgate.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Welcome, Chet! This list is very welcoming to newcomers.

I would be happy to exchange test messages with you.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknEavMACgkQAGkWiMCbp27TAwCgucAh9dE3ZuAQco5Cf5rUZzHX
7vkAoIZGbzON+8KrZxHiQmRzg0ckWw3Y
=mYMo
-----END PGP SIGNATURE-----

From alex_tremayne at gmx.com  Sun Mar 22 07:48:58 2009
From: alex_tremayne at gmx.com (Dr. Alex Tremayne)
Date: Sun, 22 Mar 2009 14:48:58 +0000
Subject: [Enigmail] Request for Help Testing Encryption in Enigmail
 using Thunderbird in WinXP
In-Reply-To: <49C2E867.10407@ocii.com>
References: <49C2E867.10407@ocii.com>
Message-ID: <49C64FDA.8090205@gmx.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Chet,

seems to be working to me.

Regards,
Alex

Chet Meek wrote:
> Hi Enigmail list members,
> 
> I have sent a signed plaintext message to Adele,
> and got a response back from their robot that
> my signature was Ok. So I am signing this
> inquiry too. My public key is on file
> at |pool.sks-keyservers.net |and I am attaching it
> to this message in case it is needed here too.
> 
> Now I would like to test sending and receiving
> signed and encrypted messages.
> 
> Is there somebody on this list who is willing
> to engage in exchanging a few trial messages?
> If so. please send me a note, and tell me if
> I should reply personally, or to the list, or what.
> 
> In case it helps ...
> I am a retiree who wants greater confidentiality
> in some email messages and to be able to decrypt
> and reply to encrypted messages from others
> using OpenPGP. I use Thunderbird under Windows XP
> (with OpenPGP just installed); and I am right
> at the limit of my computer literacy with this
> installation, checkout, etc. I am not very confident
> that it has all been done right.
> 
> Any help would be appreciated. And thank you.
> And sorry for any inconvenience if this is not
> the way to ask. I am very green.
> 
> 
>   - Chet.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknGT9kACgkQAFYnzXfo4NgTswCeKraMxkBwFxAiouIXvR9jL0GC
l+gAnjFMnhpe4yaPFFiZmfehZCVZnJYR
=KM5i
-----END PGP SIGNATURE-----

From patrick at mozilla-enigmail.org  Mon Mar 23 01:58:12 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Mon, 23 Mar 2009 09:58:12 +0100
Subject: [Enigmail] xulrunner-ipc leaves file descriptors open in child
 process?
In-Reply-To: <49C46A0B.1040407@fifthhorseman.net>
References: <49C46A0B.1040407@fifthhorseman.net>
Message-ID: <49C74F24.10209@mozilla-enigmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Daniel Kahn Gillmor wrote:
> Hi folks--
> 
> I've made significant progress in getting xulrunner-ipc to build cleanly
> with a relatively simple makefile, to the point where i've event gotten
> firegpg 0.7.5 working on GNU/linux on the powerpc(!)  I hope to publish
> a bit of my revised build process soon, as i'd like it to be useful to
> people other than myself.
> 
> I've been exploring its behavior, though, and i'm finding that the
> spawned child process appears to retain a copy of all of the file
> descriptors of the parent process.  Is this intentional?
> 
> Here's an example that i caught during a long-running child process
> (this is firegpg creating a key):
> 
>> dkg at clam:~$ lsof -p 4333
[...]
> 
> It seems like most of the open file descriptors are *not* file
> descriptors that GnuPG would have opened on its own.  So i can only
> assume that the file descriptors are inherited from the parent process.
> 
> This seems potentially sloppy -- what if there were three network
> connections opened by the parent, and the child process was to start
> manipulating them?  What about writing to the cache or adjusting the
> already-open files somehow?  Wouldn't it make more sense to close all
> file descriptors except the pipes before execing the child process?
> 
> Or is there some reason that the child process in xulrunner-ipc should
> really have access to all of the parent's file descriptors?

The problem is that IPC relies on standard Mozilla platform
functionality for executing files. Unfortunately the platform always
passes all file descriptors to the child process and doesn't allow to
specify different behavior. I was already trying to implement
workarounds for it, but I haven't found anything apart from either
fixing Mozilla or re-implementing the complete functionality to execute
files within IPC. Unfortunately I'm not good enough at these low-level
operations, especially as you have to do it differently for Windows,
Unix, and other OSes.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBScdPI3cOpHodsOiwAQjRRQf9HxVY85tyuD4vP8MtW+C6ADKyWJuddzDs
w29ZWqvrEErB1PoZupRwp6bfBbqw6nLovRmsnLjtCgNNHbqRAkLHx8NtlzEYOM6O
BSQtwV9b2NVHX0y0dgmtzJHMpiXXnl+Uy8NBe2sbQ/NkaD1LGwl0HTtEYO/1di4u
s3XlqxAbOozDZjcx0TMvY35pjJQ0dCL+esAhRtI/Q1zKkieKPB7WZ9j6YF8K9tQv
0KfaR6HWn1C1mm8opIyj1CdBXEcYYrO34Z5palvUG/4EpAc3TS31tCegr/xF6zYi
kn2CCi/mTj4rWuTNkUYW5IXPy60lTtMt4KN52jOtzgqeFFq827jSnA==
=MZU3
-----END PGP SIGNATURE-----

From dkg at fifthhorseman.net  Mon Mar 23 07:38:12 2009
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Mon, 23 Mar 2009 10:38:12 -0400
Subject: [Enigmail] xulrunner-ipc leaves file descriptors open in child
 process?
In-Reply-To: <49C74F24.10209@mozilla-enigmail.org>
References: <49C46A0B.1040407@fifthhorseman.net>
	<49C74F24.10209@mozilla-enigmail.org>
Message-ID: <49C79ED4.9010004@fifthhorseman.net>

On 03/23/2009 04:58 AM, Patrick Brunschwig wrote:
> The problem is that IPC relies on standard Mozilla platform
> functionality for executing files. Unfortunately the platform always
> passes all file descriptors to the child process and doesn't allow to
> specify different behavior. I was already trying to implement
> workarounds for it, but I haven't found anything apart from either
> fixing Mozilla or re-implementing the complete functionality to execute
> files within IPC. Unfortunately I'm not good enough at these low-level
> operations, especially as you have to do it differently for Windows,
> Unix, and other OSes.

Yuck.  That does sound like a hairy problem.  I'm glad it's on your
radar, but i'm afraid i don't have any constructive technical approach
to offer (you're way more experienced with this stuff than i am).

Have you raised the concern anywhere in bugzilla?  I'd happily +1 any
relevant bug if you point me to it, for whatever that's worth.

Thanks for all your work on this, Patrick.

Regards,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090323/935dd5a9/attachment.bin>

From jeandavid8 at verizon.net  Mon Mar 23 08:32:06 2009
From: jeandavid8 at verizon.net (Jean-David Beyer)
Date: Mon, 23 Mar 2009 11:32:06 -0400
Subject: [Enigmail] xulrunner-ipc leaves file descriptors open in child
 process?
In-Reply-To: <49C79ED4.9010004@fifthhorseman.net>
References: <49C46A0B.1040407@fifthhorseman.net>
	<49C74F24.10209@mozilla-enigmail.org>
	<49C79ED4.9010004@fifthhorseman.net>
Message-ID: <49C7AB76.8080905@verizon.net>

Daniel Kahn Gillmor wrote:
> On 03/23/2009 04:58 AM, Patrick Brunschwig wrote:
>> The problem is that IPC relies on standard Mozilla platform
>> functionality for executing files. Unfortunately the platform always
>> passes all file descriptors to the child process and doesn't allow to
>> specify different behavior. I was already trying to implement
>> workarounds for it, but I haven't found anything apart from either
>> fixing Mozilla or re-implementing the complete functionality to execute
>> files within IPC. Unfortunately I'm not good enough at these low-level
>> operations, especially as you have to do it differently for Windows,
>> Unix, and other OSes.

For any UNIX platform, perhaps you could put something between the Mozilla
(I assume you do not wish to tinker with Mozilla) and the file you wish to
execute, that you do not wish to tinker with either.

What you could do, I suppose, is write a program that passes all its
arguments to a subprogram, the one Mozilla wants to run. What your program
should do is close all the files you do not wish to pass through (which
would get passed through otherwise), and then execute the processes Mozilla
wants.

Probably what happens in Mozilla is that it does a fork() and an execl() (or
one of its variants). So look up fork() and execl() to see what you need to
do in the intermediate process.
> 
> Yuck.  That does sound like a hairy problem.  I'm glad it's on your
> radar, but i'm afraid i don't have any constructive technical approach
> to offer (you're way more experienced with this stuff than i am).
> 
> Have you raised the concern anywhere in bugzilla?  I'd happily +1 any
> relevant bug if you point me to it, for whatever that's worth.
> 
> Thanks for all your work on this, Patrick.
> 


-- 
   .~.  Jean-David Beyer          Registered Linux User 85642.
   /V\  PGP-Key: 9A2FC99A         Registered Machine   241939.
  /( )\ Shrewsbury, New Jersey    http://counter.li.org
  ^^-^^ 11:20:01 up 7 days, 4:36, 3 users, load average: 4.36, 4.25, 4.30