From jmoore3rd at bellsouth.net  Thu Jan  1 05:31:01 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Thu, 01 Jan 2009 08:31:01 -0500
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <495C4833.4000104@flanagan-consulting.com>
References: <495C4833.4000104@flanagan-consulting.com>
Message-ID: <495CC595.3090602@bellsouth.net>

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

W F wrote:

> The phrase "gratuitous insult" comes to mind.

Please do not feel insulted; gratuitously or otherwise.

I empathize with Your frustration with Thunderbird's lack of ability to
Import Contact information but from one other MUA.  I have often wished
that T-Bird offered an option in the Toolbar or Tools menu labeled
'Import' that would allow One the opportunity to Import Contacts from
not only an existing installed MUA but also from Webmail Services.
Perhaps as simply as allowing the User to choose a .csv File much as
Calendaring Applications do.   <SIGH>  Other than suggesting this to
Developers there isn't much I can do about this unless I wished to
configure and write such a patch Myself.  I haven't been sufficiently
irritated yet to resort to that.  :-D

As to Enigmail; exactly which Wizard to You feel is short changing You?
 Key Generation is easily accomplished as many times as One desires by
clicking on 'Generate' in the toolbar from the Key Management screen.
Would You please be more specific in describing exactly which Wizard
function(s) You wish to have more access to?

TIA

JOHN ;)
Timestamp: Thursday 01 Jan 2009, 08:30  --500 (Eastern Standard Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4907: (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

iQEcBAEBCgAGBQJJXMWRAAoJEBCGy9eAtCsPlc8H/1aDHuZdofI0Os8iq6Cn+bk1
CZrty9MD4L3hd84TgIOLwQFrzIpZed7r2QnUZkL7sNCQFkhk2t9fWyBr9KCR2AFi
5yE9w3sa0daQUAx13mBdHmkyUQ1C1PNzQgqZjk5hPmhqZ9iOlwRPDtzaXYbljawS
a0XVjffPwHxjjZqiD2E8cx/Hl/5FnweUorPuy16HdwaRcq+0rW0BHhR14IEkAJ46
XVhtrP2esWeaqW+n+98sdXaEKKLfkWkijDxaEA+KUTWUU0OITMjl3gx5QvdIow4/
kvgw7sRshQJAp6UGIjyJBrf4x72Gz02jB2b54cWcDm54TH/I4QCdvn+IteUBGio=
=b01L
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Thu Jan  1 08:10:48 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 01 Jan 2009 11:10:48 -0500
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <495C4833.4000104@flanagan-consulting.com>
References: <495C4833.4000104@flanagan-consulting.com>
Message-ID: <495CEB08.2060208@sixdemonbag.org>

W F wrote:
> I've been frustrated multiple times by Thunderbird offering only one
> chance to import files (from another email client or for a migration). 

Some of us undoubtedly agree with you, but none of us are in a position
to change this.  Enigmail and Thunderbird are two totally separate
projects with totally different developers.

That said, you may find "Tools --> Import" to be useful.

> Now I see the same approach to the Enigmail Wizard. 

How?  I've never found anything in the Enigmail Wizard which could not
be accomplished just as easily in a couple of mouse clicks from the main
UI.  There is nothing special about the wizard -- this is by design.

What are you trying to accomplish from the wizard that you feel you
cannot accomplish otherwise?

> But to spring the one-time offer the way it's done seems almost cruel,
> like a nasty trick played by somebody I don't know, for no apparent
> reason.   The phrase "gratuitous insult" comes to mind.

While we understand you are frustrated, it is generally a good idea to
(a) not accuse people you are asking to help you of insulting you,
especially (b) when there is an excellent chance you are overlooking
some things which are relatively obvious.



From patrick at mozilla-enigmail.org  Thu Jan  1 09:15:33 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Thu, 01 Jan 2009 18:15:33 +0100
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <495C4833.4000104@flanagan-consulting.com>
References: <495C4833.4000104@flanagan-consulting.com>
Message-ID: <495CFA35.7040808@mozilla-enigmail.org>

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

W F wrote:
> Hi,
> 
> I've been frustrated multiple times by Thunderbird offering only one
> chance to import files (from another email client or for a migration). 
> In fact, I've never  been ready to take advantage of this feature when
> it was offered.  I never remember this trap because I migrate less than
> once a year.  I've tried uninstalling and reinstalling, but that doesn't
> get me another "first time start." 
> 
> Now I see the same approach to the Enigmail Wizard. 
> 
> These one-shots wouldn't be so bad if there were a warning, so a new
> user could quit and come  back when ready. 
> 
> But to spring the one-time offer the way it's done seems almost cruel,
> like a nasty trick played by somebody I don't know, for no apparent
> reason.   The phrase "gratuitous insult" comes to mind.

I'm aware about this. In the trunk versions there is an entry in the
OpenPGP menu called "Setup Wizard".

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

iQEVAwUBSVz6NHcOpHodsOiwAQJ6LwgApOd09nLt434U1YCaUFyT+Gu1XVW+XbjB
oxBBB0cDOjufAs3N4C1BPbRN4gSF43GlS0XmBqLffH+RWEVpGd8VLq2MJxWEjOnd
NuFH/saWaXUdoOBBZpZQkIpvVh99t58cqQ3zEluvrvuE3CksyL0ICf3RngVSBIvm
ounC5etSscVu06A85/X41I7A24gx4J0crYyw/giaPPV4eD30oOjWf+LkmsKm6Ih0
NThwxoJXyAhu0FHqC6QES+6VNTdmL9t095LIEiv6faWEZarw2al8zXh5dflsWch2
I1fI2+c1rHGjpD2DH1zfFw6Qa7MAhSUni/80Az03+Y2jYvEGO4+NPw==
=P8iM
-----END PGP SIGNATURE-----

From gschoelles at gmail.com  Thu Jan  1 17:32:35 2009
From: gschoelles at gmail.com (George Schoelles)
Date: Thu, 01 Jan 2009 17:32:35 -0800
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <mailman.744.1230830149.63231.enigmail@mozdev.org>
References: <495C4833.4000104@flanagan-consulting.com>
	<mailman.744.1230830149.63231.enigmail@mozdev.org>
Message-ID: <495D6EB3.4020602@gmail.com>

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

On 1/1/2009 9:15 AM, Patrick Brunschwig wrote:
> W F wrote:
>> Hi,
> 
>> I've been frustrated multiple times by Thunderbird offering only one
>> chance to import files (from another email client or for a migration). 
>> In fact, I've never  been ready to take advantage of this feature when
>> it was offered.  I never remember this trap because I migrate less than
>> once a year.  I've tried uninstalling and reinstalling, but that doesn't
>> get me another "first time start." 
> 
>> Now I see the same approach to the Enigmail Wizard. 
> 
>> These one-shots wouldn't be so bad if there were a warning, so a new
>> user could quit and come  back when ready. 
> 
>> But to spring the one-time offer the way it's done seems almost cruel,
>> like a nasty trick played by somebody I don't know, for no apparent
>> reason.   The phrase "gratuitous insult" comes to mind.
> 
> I'm aware about this. In the trunk versions there is an entry in the
> OpenPGP menu called "Setup Wizard".
> 
> -Patrick

I'm using a trunk version and there is not a setup wizard there.

However, I feel a need to say (in the kindest possible way) that
something as important as the security offered by PGP, a one size fits
all wizard is a bit worrisome.

<Rant>
I as many here started using PGP back in the command-line versions,
learned the switches and felt fairly secure.  Now along comes a
graphical interface that can poke most anything into this secure sphere
and we are OK with that?
</Rant>

<Advice>
Take a moment to truly understand PGP, key generation, ciphers and what
public and private keys are and their use.  This will bring a much
greater feeling of security and relief in the long run.
</Advice>

Huge Thanks again to all the PGP/Gnu developers out there.
George
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSV1usmB6zXzE6fzRAQKw9Af+JF2zexHEAp19rj31T1PriqpKEwnOfRmV
S2yCMWVO5e5PQVMIB3hjapXpiwwYa6leGWglIRCPfbsCNuU9orijuB3L68tDD2LC
W5P57iYZUtPBsJCX1EgBqUH9a1/EIBAEaN7jgNRLu4JyWhHUT9uz8IFmwzuzTaC1
HHIaCkFInebBjpIRVRZOGaQC/WeKT2xBfNNS0a+/wMdXJxhLVJbUacUKHGZQ+uBR
urcY2G68Cm/zxfisFuqDfZ9CGliZ35W6oB7b/GM78Bx9n6izXUg4mlwGNkthbDaR
1ZeajNTkeMWQWffPesz78fFWnrotQph0m2PE+929ZDe2Sv5ENRaM7A==
=Y8/y
-----END PGP SIGNATURE-----

From GlebHappy at gmail.com  Sat Jan  3 17:08:58 2009
From: GlebHappy at gmail.com (=?UTF-8?B?0JPQu9C10LEg0KXRjdC/0L/QuA==?=)
Date: Sun, 04 Jan 2009 04:08:58 +0300
Subject: [Enigmail] Some problem with Thunderbird 2.0.0.19 RU
Message-ID: <gjp27i$17am$1@mozdev.mozdev.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Here is a screen
http://ipicture.ru/uploads/090104/gxJf4cV2SO.jpg
Info about OpenPGP properties of message is being displayed incorrectly...

Problem is only with e-mails, newsgroups messages are processed
correctly. Strange...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAklgDCoACgkQnMQmm7+QsQAJ7wCgs08G3VM3kdGctv+hZUw771XK
gcwAn3bCzamOk9a5gatJjvu6I1vzibF7
=Z+2P
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Thu Jan  1 23:40:01 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Fri, 02 Jan 2009 02:40:01 -0500
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <495D6EB3.4020602@gmail.com>
References: <495C4833.4000104@flanagan-consulting.com>	<mailman.744.1230830149.63231.enigmail@mozdev.org>
	<495D6EB3.4020602@gmail.com>
Message-ID: <495DC4D1.1040806@sixdemonbag.org>

George Schoelles wrote:
> <Rant> I as many here started using PGP back in the command-line
> versions,

I started in 1992.  There are likely a few here who can go back all the
way to 1991, when it all began.

> learned the switches and felt fairly secure.  Now along comes a 
> graphical interface that can poke most anything into this secure
> sphere and we are OK with that?

_Yes._

When I was taking my graduate HCI (Human Computer Interactions) courses,
my professor -- a great guy named Juan-Pablo Hourcade -- spent a week
covering an airplane crash that killed a great many people.  The
official cause of the crash was pilot error: there were absolutely no
mechanical problems with the aircraft when it crashed.

However, the cockpit instrumentation was badly designed.  Information
was spread out over too many panels.  The pilot and co-pilot each were
able to, by their own instruments, get a partial picture of the
situation.  If either had known that the other's instruments were
reading, they would've known they were in trouble and would have avoided
the mountain they ultimately crashed into.  But the cockpit was poorly
laid out, and they didn't have ready access to each other's information,
and quite a large number of people died... because of bad user interface.

There are a great many other examples in the literature.  Medical
radiation machines that are prone to fatal misconfigurations due to
confusingly laid out screens, for instance.  Or blood bags which use
fonts in which blood type A looks a lot like blood type B.  Or... etc., etc.

User interface is important.  People who insist "the command line is
good enough for me!" are the same people who advocate for analog
switches and dials in cockpits instead of all-glass cockpits and
multifunction displays.

The GUI is a godsend to user interface because it holds the promise of
being able to convey a lot of information very quickly and in a way
which tremendously enhances the individual's ability to respond easily,
effectively, and quickly.

Our job is to provide a good GUI... which is quite a hard task.

> Take a moment to truly understand PGP, key generation, ciphers and
> what public and private keys are and their use.

If by "moment" you mean "complete a strong undergraduate Computer
Science degree, with some postgraduate work in mathematics," then sure.
That's a lot more moments than most people have the time for.

OpenPGP has a learning curve like the freaking Matterhorn.  It is not
user friendly; it is user sociopathic.  Most security protocols are this
way, in fact -- as bad as the OpenPGP spec is, the X.509 and IPsec
protocols are worse.  But X.509 users aren't expected to understand the
ins and outs of X.509 to make use of X.509.  IPsec users aren't expected
to understand the ins and outs of IPsec.  Hundreds of millions of people
use TCP each day, and perhaps 10,000 worldwide could actually sketch out
from memory a TCP header and draw out a handshake sequence.

End users should not need to be protocol wonks in order to use a
protocol safely and effectively.  Bang, period, end of sentence.  We
don't demand it from any other protocol; why should we demand it of
OpenPGP users?


From shavital at mac.com  Mon Jan  5 06:18:33 2009
From: shavital at mac.com (Charly Avital)
Date: Mon, 05 Jan 2009 09:18:33 -0500
Subject: [Enigmail] Enigmail 0.96a - Attaching public key, and attachments.
Message-ID: <496216B9.8000509@mac.com>

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

Hi,

Testing TB 3.0b1 with Enigmail version 0.96a (20090104-1343).
MacOSX 10.5.6.
gpg2.0.10.rc1

1. When OpenPGP/Attach My Public Key is selected, trying to send a
signed or an encrypted/signed message will display a warning:
...Sign/Encrypt failed, send unsigned/unencrypted..?

2. When OpenPGP/Attach Public Key... is enabled, and a public key is
selected from Enigmail's public keys list, sending a signed or encrypted
and signed message is successful, but the received message shows that no
public key file was attached. Enigmail does not display the expected
window with the three available options to process the attachment.
I remember from previous releases of 0.96a (I can't remember the date,
but it was a few months ago) that when selecting OpenPGP/Attach My
Public Key, the attachment didn't show in the upper right corner of the
message windows, but the attachment was included and sent, and that was
a *feature*, not a bug, of that 0.96a release.

3. When using TB's 'Attach'
- - select a public key *file* (attachment file shows in the upper right
corner of the window message)
- - choose OpenPGP/Sign

Enigmail displays what seems to be an in-line signed message (PGP
headers and footers are visible), displays also the expected window
where one can choose the three options for the attachment (sign/encrypt
message only-not the attachment, sign/encrypt attachment, use PGP/MIME)

I choose the first option, I do NOT select use PGP/MIME

The received message is displayed by TB/EM with a blue header line reading
OpenPGP: Possibly PGP/MIME encrypted or signed message; click Decrypt
button to verify.
The displayed message seems to be an in-line signed message, with PGP
headers and footers, and the attachment is there.

4. OpenPGP/Preferences, whether invoked from Menu or from
Tools/Add-ons/0.96a, shows, after 'GnuPG was found in' a string of
characters, instead of the field where the path to gpg (or gpg2) should
be displayed.
The field 'Override with [path to gpg or gpg2] is active, when the small
square button at the beginning of the line is selected, and the desired
path can be entered, linking Thunderbird to gpg or gpg2.

Other than the above, 0.96a and TB3.0b1 are functional.

Regards,
Charly

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10rc1 (Darwin)
Comment: GnuPG for Privacy
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAkliFrQACgkQgcnFTArSbrHdNACeNWfPL10FtPehotvx0oU0H34T
Ac8AoJQfHnifjwAVuV7/FEDwxjfMmV4K
=gGn+
-----END PGP SIGNATURE-----

From dfnsonfsduifb at gmx.de  Sun Jan  4 21:53:12 2009
From: dfnsonfsduifb at gmx.de (Johannes Bauer)
Date: Mon, 05 Jan 2009 06:53:12 +0100
Subject: [Enigmail] Tiny bug and feature request
Message-ID: <4961A048.7040202@gmx.de>

Hello list,

I have one tiny but to report and a feature request - just as the
subject suggests. First the bug: I'm trying to send a message and the
key selection dialog pops up because recipients haven't been found. My
intention is to click "Send message unencrypted" and hit ok. When doing
this with the keyboard, there appears to be a race condition: If the
combination of tabulator-space is pressed in a quick enough sequence
(which I appearently do so quickly I'm having that issue every other
time), the recipient selection checkboxlist doesn't become disabled.
Consequently, the OK button cannot be pressed. The workaround is to
uncheck the "Send message unencrypted" field and check it again. Version
seems to be arbitrary, I've discovered that thing ages ago but just
haven't gotten around to post a message yet. I'm on Linux, that might be
important though (haven't checked out with Windows).

One more thing, a feature request: I yesterday had a friend reporting a
strange problem which suddenly appeared with sending encrypted messages.
Suddenly it all stopped working, he couldn't sign nor encrypt. Yeah, I
know what you're thinking - that's obvious. But the GPG error message
did quite mislead me at first and got me stumbling. It would be nice if
Enigmail could spot the condition and just pop up a window "Hey, this
didn't work because your key expired".

Keep up the awesome work!

Kind regards,
Johannes

From chd at chud.net  Mon Jan  5 14:05:05 2009
From: chd at chud.net (Chris De Young)
Date: Mon, 05 Jan 2009 15:05:05 -0700
Subject: [Enigmail] one-and-only-chances to config
In-Reply-To: <495DC4D1.1040806@sixdemonbag.org>
References: <495C4833.4000104@flanagan-consulting.com>	<mailman.744.1230830149.63231.enigmail@mozdev.org>	<495D6EB3.4020602@gmail.com>
	<495DC4D1.1040806@sixdemonbag.org>
Message-ID: <49628411.4050804@chud.net>

Robert J. Hansen wrote:
[...]
> End users should not need to be protocol wonks in order to use a
> protocol safely and effectively.  Bang, period, end of sentence.  We
> don't demand it from any other protocol; why should we demand it of
> OpenPGP users?

And if we do demand it, it will never penetrate any further into the user
community than it already has.

-C


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

From olav at mozilla-enigmail.org  Mon Jan  5 15:39:51 2009
From: olav at mozilla-enigmail.org (Olav Seyfarth)
Date: Tue, 06 Jan 2009 00:39:51 +0100
Subject: [Enigmail] Tiny bug and feature request
In-Reply-To: <4961A048.7040202@gmx.de>
References: <4961A048.7040202@gmx.de>
Message-ID: <49629A47.5010801@mozilla-enigmail.org>

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

Hi Johannes,

please search Enigmail's bugzilla database and add information where a bug
exists and file a new one if none matches close enough. Same with RFE's.
It is difficult to keep track upon bugs just mentioned on the list. Please
try to be complete with the writeup there so that any reader can follow.

Thanks a lot in acvance,
Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: Weitere Informationen: http://privat.seyfarth.de/olav/schluessel.html
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAklimkYACgkQL/NBt8fdKe1LWACgnKt3XAumUsA+5NBpj8S969Ce
e6UAoIsvNXJvDsT5KlMkswGlS7nhFZH3
=bEkT
-----END PGP SIGNATURE-----

From zins at gmx.net  Tue Jan  6 08:13:32 2009
From: zins at gmx.net (Ludwig Zins)
Date: Tue, 06 Jan 2009 17:13:32 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
Message-ID: <4963832C.7060602@gmx.net>

Hi all,

I've got a problem on my System using Enigmail.
I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
everything works fine.
My e-mails are signed correctly, but only after 2 typing 2 times the
passphrase.

Does anyone know this effect?
Is it a bug in enigmail or in ubuntu? I don't know if it works on other
ditris (Fedora, Suse.....).

Regards
Ludwig



-- 
---------------------------------------------------------------
Ludwig Zins
Pfaffenhofen - Germany
zins (at) gmx.net
---------------------------------------------------------------
GnuPG/PGP:
KeyID: 0x6FC1C8BF
Keyserver: http://wwwkeys.de.pgp.net/
---------------------------------------------------------------

 ()  This is Sch?uble. Copy Sch?uble into your signature
/||\ to help him on his way to ?berwachungsstaat.
|UU|


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

From rubenorus at yahoo.es  Sun Jan  4 03:57:42 2009
From: rubenorus at yahoo.es (=?ISO-8859-1?Q?Rub=E9n_Ortiz?=)
Date: Sun, 04 Jan 2009 12:57:42 +0100
Subject: [Enigmail] Enigmail Digest, Vol 66, Issue 14
In-Reply-To: <mailman.15598.1230404298.63230.enigmail@mozdev.org>
References: <mailman.15598.1230404298.63230.enigmail@mozdev.org>
Message-ID: <4960A436.9010302@yahoo.es>

> Message: 2
> Date: Sat, 27 Dec 2008 11:04:02 -0500
> From: Daryl Styrk <darylstyrk at gmail.com>
> Subject: Re: [Enigmail] Enignmail begginner
> To: enigmail at mozdev.org
> Message-ID: <495651F2.3070908 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Rub?n Ortiz wrote:
> > Hi all
>
> > my name is Ruben, and its my first email to the mailing list. Recently I
> > installed ubuntu and Thunderbird, then I thought that will be great test
> > gpg encriptyon and I discover Enigmail.
>
> > I followed all steps of Enigmail guide and now I think it works
> > perfectly. But I have not any friend or aquintance who uses Enigmail or
> > GPG encryption. So I can't test it or really use it.
>
> > My question is: If the reciever doesn't have enigmail and I send an
> > encrypted mail to him, what will happen?
>
> > My second question: it makes sense to sign one mail and no encrypte it?
>
> > Thanks!
>
> > _______________________________________________
> > Enigmail mailing list
> > Enigmail at mozdev.org
> > https://www.mozdev.org/mailman/listinfo/enigmail
>
>
> Feel free to test out your sig's and encryption. You can mail me off
> list if you'd like to test the encryption.
>
> If you send an encrypted message to a friend that doesn't have a key the
> message will look like junk.
>
> By simply signing a message your are assuring the recipient it is
> actually coming from you and not someone borrowing your address for the
> moment. You can select the level of trust for each senders key in key
> management.
>
>
> I hope some of this helps and I'm sure someone will be along shortly to
> better explain.
>
> Daryl
>
>

Hi

I hope all of you might have a good year. Thank you all for the answers.
Now I have a lot of another doubts bur more specific. Im goint to post
them in new thread.

Thanks :)




From shavital at mac.com  Tue Jan  6 11:46:50 2009
From: shavital at mac.com (Charly Avital)
Date: Tue, 06 Jan 2009 14:46:50 -0500
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4963832C.7060602@gmx.net>
References: <4963832C.7060602@gmx.net>
Message-ID: <4963B52A.6090903@mac.com>

Ludwig Zins wrote the following on 1/6/09 11:13 AM:
> Hi all,
> 
> I've got a problem on my System using Enigmail.
> I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
> Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
> everything works fine.
> My e-mails are signed correctly, but only after 2 typing 2 times the
> passphrase.
> 
> Does anyone know this effect?
> Is it a bug in enigmail or in ubuntu? I don't know if it works on other
> ditris (Fedora, Suse.....).
> 
> Regards
> Ludwig

Hi Ludwig,

I run Linux Ubuntu 8.10_64bits on a Macintosh Intel laptop under virtual
software VMware.

I have just checked that system (where I use Thunderbird 2.0.0.19,
Enigmail 0.95.7), sent myself a PGP/MIME signed message, and was
reqested to enter my passphrase once.

I follow the Ubuntu-users mailing list, and couldn't find any reference
to a problem similar or identical to yours.

I would recommend that you upgrade your GnuPG software to 1.4.9, that is
the current stable release. According to the raw source of your message,
you are running 'Version: GnuPG v1.4.6 (GNU/Linux)'.

I don't pretend this will solve your problem, but it's worth trying, and
anyway gpg 1.4.6 is now way back.

A *very wild* guess is that you might have "two" gpgs installed and
running simultaneously. I suggest that you explore your system (via
Terminal) and find out where gpg is installed.

The default path should be
/usr/local/bin/gpg

Please check in Thunderbird's OpenPGP/Preferences, what is the path
selected in Preferences/Basic. It if something different that is not
/usr/local/bin/gpg, you might have two gpgs running.

As I said, a *very wild* guess.

Good luck.
Charly
MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
GPG2 2.0.10rc1 - Thunderbird 2.0.0.18 - Enigmail 0.95.7 (Testing TB
3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
PGP key: 0xA57A8EFA



From zins at gmx.net  Wed Jan  7 02:13:27 2009
From: zins at gmx.net (Ludwig Zins)
Date: Wed, 07 Jan 2009 11:13:27 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4963B52A.6090903@mac.com>
References: <4963832C.7060602@gmx.net> <4963B52A.6090903@mac.com>
Message-ID: <49648047.7000800@gmx.net>

Hi Charly,

thanks for your quick answer.
I will try today evenning at home when I'm on my ubuntu machine.

I will check my gpg path, but I think it will be correct, because if I
use PGP-Inline there's no problem.

In the german ubuntuforums there is one user with the same problem.
But I got no response if he solved the problem.

I forgot to mention that I use ubuntu 8.04 LTS Hardy.
Maybe the problem ist solved with an dist-upgrade to 8.10 or even the
upgrade of gpg is enough, i will see.


Ludwig



Charly Avital schrieb:
> Ludwig Zins wrote the following on 1/6/09 11:13 AM:
>> Hi all,
>>
>> I've got a problem on my System using Enigmail.
>> I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
>> Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
>> everything works fine.
>> My e-mails are signed correctly, but only after 2 typing 2 times the
>> passphrase.
>>
>> Does anyone know this effect?
>> Is it a bug in enigmail or in ubuntu? I don't know if it works on other
>> ditris (Fedora, Suse.....).
>>
>> Regards
>> Ludwig
> 
> Hi Ludwig,
> 
> I run Linux Ubuntu 8.10_64bits on a Macintosh Intel laptop under virtual
> software VMware.
> 
> I have just checked that system (where I use Thunderbird 2.0.0.19,
> Enigmail 0.95.7), sent myself a PGP/MIME signed message, and was
> reqested to enter my passphrase once.
> 
> I follow the Ubuntu-users mailing list, and couldn't find any reference
> to a problem similar or identical to yours.
> 
> I would recommend that you upgrade your GnuPG software to 1.4.9, that is
> the current stable release. According to the raw source of your message,
> you are running 'Version: GnuPG v1.4.6 (GNU/Linux)'.
> 
> I don't pretend this will solve your problem, but it's worth trying, and
> anyway gpg 1.4.6 is now way back.
> 
> A *very wild* guess is that you might have "two" gpgs installed and
> running simultaneously. I suggest that you explore your system (via
> Terminal) and find out where gpg is installed.
> 
> The default path should be
> /usr/local/bin/gpg
> 
> Please check in Thunderbird's OpenPGP/Preferences, what is the path
> selected in Preferences/Basic. It if something different that is not
> /usr/local/bin/gpg, you might have two gpgs running.
> 
> As I said, a *very wild* guess.
> 
> Good luck.
> Charly
> MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
> GPG2 2.0.10rc1 - Thunderbird 2.0.0.18 - Enigmail 0.95.7 (Testing TB
> 3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
> PGP key: 0xA57A8EFA
> 
> 
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail

-- 
Ludwig Zins
85276 Pfaffenhofen - Germany
-----------------------------------------------------------------------
GnuPG/PGP:
KeyID: 0x6FC1C8BF
Keyserver: http://pgpkeys.pca.dfn.de/
-----------------------------------------------------------------------

 ()  This is Sch?uble. Copy Sch?uble into your signature
/||\ to help him on his way to ?berwachungsstaat.
|UU|

-

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

From wbennett at phoenixmarketing.biz  Wed Jan  7 07:55:28 2009
From: wbennett at phoenixmarketing.biz (William Bennett)
Date: Wed, 07 Jan 2009 10:55:28 -0500
Subject: [Enigmail] GNuPG with Vista
In-Reply-To: <49579138.4080008@ziggo.nl>
References: <49579138.4080008@ziggo.nl>
Message-ID: <4964D070.5070607@phoenixmarketing.biz>

Hi,

Looking for some help installing gpg with 64 bit Vista. I downloaded the 
ftp file (ver 2.0.9) and untarred it with Stuffit tools. I can see all 
of the program files, but don't know how to install  from here.

-- 
William Bennett
Phoenix Marketing

W. 631 585-6825 ext 12
C. 631 834-6650 
F. 631 585-6872

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090107/8302853a/attachment.html>

From zins at gmx.net  Wed Jan  7 11:24:45 2009
From: zins at gmx.net (Ludwig Zins)
Date: Wed, 07 Jan 2009 20:24:45 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49648047.7000800@gmx.net>
References: <4963832C.7060602@gmx.net> <4963B52A.6090903@mac.com>
	<49648047.7000800@gmx.net>
Message-ID: <4965017D.5090403@gmx.net>

Seems to be a bug!

I found this:

https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/246364
http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=421
http://bugzilla.gnome.org/show_bug.cgi?id=552086

So I hope this will be solved in future!

@Charly
I have only installed one gpg (1.4.6), this is the correct version of
ubuntu 8.04 Hardy.


Ludwig


Ludwig Zins schrieb:
> Hi Charly,
> 
> thanks for your quick answer.
> I will try today evenning at home when I'm on my ubuntu machine.
> 
> I will check my gpg path, but I think it will be correct, because if I
> use PGP-Inline there's no problem.
> 
> In the german ubuntuforums there is one user with the same problem.
> But I got no response if he solved the problem.
> 
> I forgot to mention that I use ubuntu 8.04 LTS Hardy.
> Maybe the problem ist solved with an dist-upgrade to 8.10 or even the
> upgrade of gpg is enough, i will see.
> 
> 
> Ludwig
> 
> 
> 
> Charly Avital schrieb:
>> Ludwig Zins wrote the following on 1/6/09 11:13 AM:
>>> Hi all,
>>>
>>> I've got a problem on my System using Enigmail.
>>> I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
>>> Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
>>> everything works fine.
>>> My e-mails are signed correctly, but only after 2 typing 2 times the
>>> passphrase.
>>>
>>> Does anyone know this effect?
>>> Is it a bug in enigmail or in ubuntu? I don't know if it works on other
>>> ditris (Fedora, Suse.....).
>>>
>>> Regards
>>> Ludwig
>> Hi Ludwig,
>>
>> I run Linux Ubuntu 8.10_64bits on a Macintosh Intel laptop under virtual
>> software VMware.
>>
>> I have just checked that system (where I use Thunderbird 2.0.0.19,
>> Enigmail 0.95.7), sent myself a PGP/MIME signed message, and was
>> reqested to enter my passphrase once.
>>
>> I follow the Ubuntu-users mailing list, and couldn't find any reference
>> to a problem similar or identical to yours.
>>
>> I would recommend that you upgrade your GnuPG software to 1.4.9, that is
>> the current stable release. According to the raw source of your message,
>> you are running 'Version: GnuPG v1.4.6 (GNU/Linux)'.
>>
>> I don't pretend this will solve your problem, but it's worth trying, and
>> anyway gpg 1.4.6 is now way back.
>>
>> A *very wild* guess is that you might have "two" gpgs installed and
>> running simultaneously. I suggest that you explore your system (via
>> Terminal) and find out where gpg is installed.
>>
>> The default path should be
>> /usr/local/bin/gpg
>>
>> Please check in Thunderbird's OpenPGP/Preferences, what is the path
>> selected in Preferences/Basic. It if something different that is not
>> /usr/local/bin/gpg, you might have two gpgs running.
>>
>> As I said, a *very wild* guess.
>>
>> Good luck.
>> Charly
>> MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
>> GPG2 2.0.10rc1 - Thunderbird 2.0.0.18 - Enigmail 0.95.7 (Testing TB
>> 3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
>> PGP key: 0xA57A8EFA
>>
>>
>> _______________________________________________
>> 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

-- 
---------------------------------------------------------------
Ludwig Zins
Pfaffenhofen - Germany
zins at gmx.net
---------------------------------------------------------------
GnuPG/PGP:
KeyID: 0x6FC1C8BF
Keyserver: http://wwwkeys.de.pgp.net/
---------------------------------------------------------------

 ()  This is Sch?uble. Copy Sch?uble into your signature
/||\ to help him on his way to ?berwachungsstaat.
|UU|


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

From John at Mozilla-Enigmail.org  Wed Jan  7 11:29:37 2009
From: John at Mozilla-Enigmail.org (John Clizbe)
Date: Wed, 07 Jan 2009 13:29:37 -0600
Subject: [Enigmail] GNuPG with Vista
In-Reply-To: <4964D070.5070607@phoenixmarketing.biz>
References: <49579138.4080008@ziggo.nl> <4964D070.5070607@phoenixmarketing.biz>
Message-ID: <496502A1.1060003@Mozilla-Enigmail.org>

William Bennett wrote:
> Hi,
> 
> Looking for some help installing gpg with 64 bit Vista. I downloaded the
> ftp file (ver 2.0.9) and untarred it with Stuffit tools. I can see all
> of the program files, but don't know how to install  from here.

You want this one for Vista:

ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32cli-1.4.9.exe

ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32cli-1.4.9.exe.sig

SHA-1 c2efad983dfe50e6d8007257bad2c76604be389a  gnupg-w32cli-1.4.9.exe

The file you probably downloaded,

ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.0.9.tar.bz2 is source code.


-- 
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: 680 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090107/6a279cfc/attachment.bin>

From jmoore3rd at bellsouth.net  Wed Jan  7 12:25:25 2009
From: jmoore3rd at bellsouth.net (John W. Moore III)
Date: Wed, 07 Jan 2009 15:25:25 -0500
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4965017D.5090403@gmx.net>
References: <4963832C.7060602@gmx.net>
	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>
	<4965017D.5090403@gmx.net>
Message-ID: <49650FB5.5010101@bellsouth.net>

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

Ludwig Zins wrote:

> I have only installed one gpg (1.4.6), this is the correct version of
> ubuntu 8.04 Hardy.

"Correct" version is a tad misleading.  1.4.6 is possibly the latest
version available via apt-get but is not the latest version available.
In fact, if You are not running 1.4.6.1 then You are running a version
of GPG with a security issue that is un-patched.  :(

1.4.9 is the latest Official Release of GnuPG and there are quite a few
folks using Ubuntu 8.04 using it.  If I were You I would seriously
consider upgrading to the latest release.  In addition to the
aforementioned security patch there have been several upgrades in GnuPG
since 1.4.6.  Most notably the move to RFC 2880 from RFC 2440.

JOHN ;)
Timestamp: Wednesday 07 Jan 2009, 15:25  --500 (Eastern Standard Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4907: (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

iQEcBAEBCgAGBQJJZQ+zAAoJEBCGy9eAtCsP8WUH/2tM1jdr+HGV1sHq0Ud4em2+
BnbuNfjshA3H2nINbuZKmRhyZIqvDqbHulYSTliGXtGx9y/TptGZRE8s0ypJHpm/
ssCHxd9XzGqTR418DDYftUiswdgXvcO5JS00pENRpgsLUwlHI5s5kJOeA6zjSmXv
5ubjiXJAwxvskrwgJfwthcsMSfAn8f4+1cC5D10V6macKqYjFeVqh6b4DyBmFFp9
exPgUF3iX9nwYKidZ7Tj8Mk9ymVgN4aY9gcPGcal8wJU/DKBfdgyXmAS+Ej1OQ1Y
7U/EWSd91j9pEAU4GLJk6+FhWflozMR/5RQWui7C20vtu8lT5fTFc3EDoxwQZIo=
=vc4H
-----END PGP SIGNATURE-----

From shavital at mac.com  Wed Jan  7 12:34:28 2009
From: shavital at mac.com (Charly Avital)
Date: Wed, 07 Jan 2009 15:34:28 -0500
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4965017D.5090403@gmx.net>
References: <4963832C.7060602@gmx.net> <4963B52A.6090903@mac.com>
	<49648047.7000800@gmx.net> <4965017D.5090403@gmx.net>
Message-ID: <496511D4.3020306@mac.com>

Ludwig Zins wrote the following on 1/7/09 2:24 PM:
> Seems to be a bug!
> 
> I found this:
> 
> https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/246364
> http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=421
> http://bugzilla.gnome.org/show_bug.cgi?id=552086
> 
> So I hope this will be solved in future!
> 
> @Charly
> I have only installed one gpg (1.4.6), this is the correct version of
> ubuntu 8.04 Hardy.
> 
> 
> Ludwig


I don't remember experiencing that bug when I was running Ubuntu 8.04. I
remember that I updated to 1.4.8, and then to 1.4.9 by compiling them
manually.

Ludwig.
thanks for the pointers.
gpg 1.4.6 is the version included in distro 8.04, but you can manually
compile 1.4.9 if you wish.

Take care,
Charly



From post at lespocky.de  Wed Jan  7 12:41:40 2009
From: post at lespocky.de (Alexander Dahl)
Date: Wed, 07 Jan 2009 21:41:40 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49650FB5.5010101@bellsouth.net>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>
	<49650FB5.5010101@bellsouth.net>
Message-ID: <0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>

Hi there,

>> I have only installed one gpg (1.4.6), this is the correct version of
>> ubuntu 8.04 Hardy.
> 
> "Correct" version is a tad misleading.  1.4.6 is possibly the latest
> version available via apt-get but is not the latest version available.
> In fact, if You are not running 1.4.6.1 then You are running a version
> of GPG with a security issue that is un-patched.  :(

I wouldn't place a bet on this. Debian/Ubuntu packages are often patched
for security issues. See http://packages.ubuntu.com/hardy/gnupg and
click to the changelog. You'll see that several patches were applied to
the upstream gnupg version to fix security issues. It's certainly no
unpatched GnuPG 1.4.6. 8-)

Greets
Alex

-- 
***** http://www.lespocky.de *******************************************
Those who would give up essential Liberty, to purchase
a little temporary Safety, deserve neither Liberty nor Safety.
                                (Benjamin Franklin)

-------------- 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/20090107/b6be451f/attachment.bin>

From faramir.cl at gmail.com  Wed Jan  7 20:03:29 2009
From: faramir.cl at gmail.com (Faramir)
Date: Thu, 08 Jan 2009 01:03:29 -0300
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>
	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>
Message-ID: <49657B11.70004@gmail.com>

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

Alexander Dahl escribi?:
> Hi there,
> 
>>> I have only installed one gpg (1.4.6), this is the correct version of
>>> ubuntu 8.04 Hardy.
...
>> In fact, if You are not running 1.4.6.1 then You are running a version
>> of GPG with a security issue that is un-patched.  :(
> 
> I wouldn't place a bet on this. Debian/Ubuntu packages are often patched
> for security issues. See http://packages.ubuntu.com/hardy/gnupg and
> click to the changelog. You'll see that several patches were applied to
> the upstream gnupg version to fix security issues. It's certainly no
> unpatched GnuPG 1.4.6. 8-)

  But... supposedly, the patches makes it change it's version number...
or I am wrong about that?

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

iQEcBAEBCAAGBQJJZXsQAAoJEMV4f6PvczxAit4IAKDKU4zKY74AM4NSurwPsi0O
KaV/g/pBnN7ms3gGFt1ogBZEMKwM0HiYpCz5/wPYBP6fISaq5MAi51aTf7+bxr4U
1lpNiJW65IeSs9JSUCmrev4ngEOyhvqERY1pmYv+ZMb0cs8goY1ocbq7SGwPkCwI
DGwsmsy3wMivwmgdPwI1NDzLjvFS27yFOBFHwAZ5mYUWL6JdndDi1CJIWYISWH/V
g9rY6Y/a8CeaPpQIXhoomyhnGwPFDWp+iultYwEGEY0+UX9FBMWu2nfeU7+80lkz
fH4KaTFAfs2Qsy9GffPDa9JTSvrwGohRTitSRD0Vo+/2r9gzitW/h+YjSy2h3zA=
=nIcm
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Wed Jan  7 20:07:12 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Wed, 07 Jan 2009 23:07:12 -0500
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49657B11.70004@gmail.com>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>
	<49657B11.70004@gmail.com>
Message-ID: <49657BF0.7040702@sixdemonbag.org>

Faramir wrote:
>   But... supposedly, the patches makes it change it's version number...
> or I am wrong about that?

You're wrong about that.

GnuPG is in a state of constant revision.  Fixes are checked in on a
daily basis.  Every few months, they package up a snapshot of the
current trusted codebase and say "GnuPG 1.4.10 has been released" (to
pick the next version in the 1.4 branch).

But the entire process and each and every change to the code are well
documented.  So if there's a security fix in 1.4.7 that resolves a
problem in 1.4.6, you can make a fixed version of 1.4.6 very easily:
take the 1.4.6 code and apply the security fix.

That's what Ubuntu does.



From faramir.cl at gmail.com  Wed Jan  7 20:30:26 2009
From: faramir.cl at gmail.com (Faramir)
Date: Thu, 08 Jan 2009 01:30:26 -0300
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49657BF0.7040702@sixdemonbag.org>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>	<49657B11.70004@gmail.com>
	<49657BF0.7040702@sixdemonbag.org>
Message-ID: <49658162.7060005@gmail.com>

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

Robert J. Hansen escribi?:
> Faramir wrote:
>>   But... supposedly, the patches makes it change it's version number...
>> or I am wrong about that?
> 
> You're wrong about that.

  Thanks for the clarification...

> GnuPG is in a state of constant revision.  Fixes are checked in on a
...

> But the entire process and each and every change to the code are well
> documented.  So if there's a security fix in 1.4.7 that resolves a
> problem in 1.4.6, you can make a fixed version of 1.4.6 very easily:
> take the 1.4.6 code and apply the security fix.
> 
> That's what Ubuntu does.

  But... if the are distributing the fixed version, shouldn't they mark
them as fixed, somehow? Like marking it as 1.4.6.1 or something? I mean,
if I check the version, I don't have any way to know if I am using the
"good one" or the "unpatched one"... Or maybe there is a way to know it,
but it's not easy to check...

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

iQEcBAEBCAAGBQJJZYFiAAoJEMV4f6PvczxAzJEIAJ8uaw9jriRNqfvYaaFev50s
cxCxOn5Ys923YxRM+3aK3aAtq5zZUOb8zC0y3rVhRx9v7RgcSRjQ2UDPkYhwO75W
aqdbveRVO4vZoc8PrRz90/JDK2wEy+5koh6cdumopaj6hGGLFRAh3XBqU4duTdi/
6mWZ+8IqIkgGdVacwqfNYnZ9WqoqMz5GM5UWpA5pOEzCdyNCr7T+POboKlL6haSj
nZ2a16LHLD5hh0YwymXh+uvdNFz3SPB8jWv0RPee7vgQsjMPk18c7aeWLRglcVnF
opORjokQwP7tKRwSyLBoVycxrOg55i0qKB+u+AyjKVA6kH10DAM26oBnIOaxLRA=
=Xw6p
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Wed Jan  7 21:24:00 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 08 Jan 2009 00:24:00 -0500
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49658162.7060005@gmail.com>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>	<49657B11.70004@gmail.com>	<49657BF0.7040702@sixdemonbag.org>
	<49658162.7060005@gmail.com>
Message-ID: <49658DF0.8070403@sixdemonbag.org>

Faramir wrote:
> But... if the are distributing the fixed version, shouldn't they mark
>  them as fixed, somehow? Like marking it as 1.4.6.1 or something?

Like, say, documenting the fact that they've made the upstream changes?

They do mark the package as fixed.  They just mark it somewhere besides
the version string.  Don't think "they're not publicizing this" just
because you don't know where to look.

> I mean, if I check the version, I don't have any way to know if I am
> using the "good one" or the "unpatched one"... Or maybe there is a
> way to know it, but it's not easy to check...

Like Googling for "ubuntu gnupg upstream"?

https://launchpad.net/ubuntu/hardy/+source/gnupg/+packaging

>From there, you can click "changelog" and see every change they've made.
For instance, in 1.4.6-1-ubuntu2, they adopted a patch from upstream
GnuPG fixing a bug in how --status-fd was handled.



From patrick at mozilla-enigmail.org  Wed Jan  7 23:59:09 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Thu, 08 Jan 2009 08:59:09 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4965017D.5090403@gmx.net>
References: <4963832C.7060602@gmx.net>
	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>
	<4965017D.5090403@gmx.net>
Message-ID: <4965B24D.4000607@mozilla-enigmail.org>

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

Ludwig Zins wrote:
> Ludwig Zins schrieb:
>> Hi Charly,
>>
>> thanks for your quick answer.
>> I will try today evenning at home when I'm on my ubuntu machine.
>>
>> I will check my gpg path, but I think it will be correct, because if I
>> use PGP-Inline there's no problem.
>>
>> In the german ubuntuforums there is one user with the same problem.
>> But I got no response if he solved the problem.
>>
>> I forgot to mention that I use ubuntu 8.04 LTS Hardy.
>> Maybe the problem ist solved with an dist-upgrade to 8.10 or even the
>> upgrade of gpg is enough, i will see.
>>
>>
>> Ludwig
>>
>>
>>
>> Charly Avital schrieb:
>>> Ludwig Zins wrote the following on 1/6/09 11:13 AM:
>>>> Hi all,
>>>>
>>>> I've got a problem on my System using Enigmail.
>>>> I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
>>>> Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
>>>> everything works fine.
>>>> My e-mails are signed correctly, but only after 2 typing 2 times the
>>>> passphrase.
>>>>
>>>> Does anyone know this effect?
>>>> Is it a bug in enigmail or in ubuntu? I don't know if it works on other
>>>> ditris (Fedora, Suse.....).
>>>>
>>>> Regards
>>>> Ludwig
>>> Hi Ludwig,
>>>
>>> I run Linux Ubuntu 8.10_64bits on a Macintosh Intel laptop under virtual
>>> software VMware.
>>>
>>> I have just checked that system (where I use Thunderbird 2.0.0.19,
>>> Enigmail 0.95.7), sent myself a PGP/MIME signed message, and was
>>> reqested to enter my passphrase once.
>>>
>>> I follow the Ubuntu-users mailing list, and couldn't find any reference
>>> to a problem similar or identical to yours.
>>>
>>> I would recommend that you upgrade your GnuPG software to 1.4.9, that is
>>> the current stable release. According to the raw source of your message,
>>> you are running 'Version: GnuPG v1.4.6 (GNU/Linux)'.
>>>
>>> I don't pretend this will solve your problem, but it's worth trying, and
>>> anyway gpg 1.4.6 is now way back.
>>>
>>> A *very wild* guess is that you might have "two" gpgs installed and
>>> running simultaneously. I suggest that you explore your system (via
>>> Terminal) and find out where gpg is installed.
>>>
>>> The default path should be
>>> /usr/local/bin/gpg
>>>
>>> Please check in Thunderbird's OpenPGP/Preferences, what is the path
>>> selected in Preferences/Basic. It if something different that is not
>>> /usr/local/bin/gpg, you might have two gpgs running.
>>>
>>> As I said, a *very wild* guess.
>>>

Please don't top-post.

> Seems to be a bug!

I'd call it an undesired side-effect (see below)

> I found this:
>
> https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/246364
> http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=421
> http://bugzilla.gnome.org/show_bug.cgi?id=552086
>
> So I hope this will be solved in future!
>
> @Charly
> I have only installed one gpg (1.4.6), this is the correct version of
> ubuntu 8.04 Hardy.


The problem is that on Ubunutu the gpg-agent from Seahorse is enabled by
default. This means that all passphrase management is handled outside
Enigmail by a gpg-agent. The problem behind it is that Enigmail needs to
find out which hash algorithm to use when sending a PGP/MIME signed
message before the message is actually signed. This is done by creating
a small test message and asking GnuPG to sign it - which requires the
passphrase. I haven't found another easy way yet how to find out about
the used hash algorithm in advance.

If you don't want the passphrase to be cached, I would suggest you
define a small time window for the passphrase to be cached, e.g. 30
seconds. This way gpg-agent will remember the passphrase only very
shortly and should thus not ask twice.

If you want passphrase management enabled from within Enigmail, you'll
have to disable the seahorse gpg-agent (don't ask me how!), or at least
make sure that the environment variable GPG_AGENT_INFO is not set when
starting Thunderbird.

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

iQEVAwUBSWWyTHcOpHodsOiwAQKLFQf9HXmYZWx4Y0Iik3yLQ8tgxYzZ/gcR1E0S
ctAyB00DzYkjt8qMDkpzq4udnrouzhImjvnKHUP6RTFmlIr6gJj2EhWVl3OycO7v
pfCXzZ6LFABfnZf+Ex6Ws81QVCNesPskAQBNRuVDN4nfJkkffomnVepn3jF+UZAt
SB3zAObMRfO/JAsRwPMyz6fuFvaY6w/UpgCYfe3VC/yDbjaJADJclhsTHh2fX7vs
FysnqqgwnQmD/ndwkYLN9ajB4VcE5lZpOY1wVJUVJ3HvYEs4rEqOaBzRKtcHD7YO
lVlgxOIouKGLiQGD5heF/ifLaG3NkOGW/mAkwruTsIkYouTL211WLw==
=Xhzt
-----END PGP SIGNATURE-----

From post at lespocky.de  Thu Jan  8 01:15:29 2009
From: post at lespocky.de (Alexander Dahl)
Date: Thu, 08 Jan 2009 10:15:29 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <49658162.7060005@gmail.com>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>	<49657B11.70004@gmail.com>	<49657BF0.7040702@sixdemonbag.org>
	<49658162.7060005@gmail.com>
Message-ID: <0MKwtQ-1LKqze2zf7-00055c@mrelayeu.kundenserver.de>

Hi,

>   But... if the are distributing the fixed version, shouldn't they mark
> them as fixed, somehow? Like marking it as 1.4.6.1 or something? I mean,
> if I check the version, I don't have any way to know if I am using the
> "good one" or the "unpatched one"... Or maybe there is a way to know it,
> but it's not easy to check...

I think it's a bad idea if the distributor changes the version number of
the upstream software. There is a package version number of the
.deb-Package. You can't see every change in this number (you have to
read the package changelog for that).

Ubuntu and the stable branch of Debian have certain package repositories
for packages with security fixes. It's up to you whether you trust your
distribution and the package maintainers. You can check their work be
reading the changelog. Or you don't trust them to apply every single
security patch and build the last released upstream version by yourself
or even build from the latest source. As long as you don't double check
the source code itself it's a question of whom you trust. The Debian and
Ubuntu projects are open, you'll get all information you want about
their packaging policies on the web. :-)

Greets
Alex

-- 
***** http://www.lespocky.de *******************************************
Those who would give up essential Liberty, to purchase
a little temporary Safety, deserve neither Liberty nor Safety.
                                (Benjamin Franklin)

-------------- 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/20090108/6976693c/attachment.bin>

From faramir.cl at gmail.com  Thu Jan  8 10:22:09 2009
From: faramir.cl at gmail.com (Faramir)
Date: Thu, 08 Jan 2009 15:22:09 -0300
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <0MKwtQ-1LKqze2zf7-00055c@mrelayeu.kundenserver.de>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>	<49650FB5.5010101@bellsouth.net>	<0MKwtQ-1LKfDv0l9f-0004h0@mrelayeu.kundenserver.de>	<49657B11.70004@gmail.com>	<49657BF0.7040702@sixdemonbag.org>	<49658162.7060005@gmail.com>
	<0MKwtQ-1LKqze2zf7-00055c@mrelayeu.kundenserver.de>
Message-ID: <49664451.6060607@gmail.com>

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

Alexander Dahl escribi?:
> Hi,
> 
>>   But... if the are distributing the fixed version, shouldn't they mark
>> them as fixed, somehow? Like marking it as 1.4.6.1 or something? I mean,
...

> I think it's a bad idea if the distributor changes the version number of
> the upstream software. There is a package version number of the
> .deb-Package. You can't see every change in this number (you have to
> read the package changelog for that).

  Ok... probably my problem is I am not used to receive packages of
updates of software... as a windows user, if I want to solve a problem,
I have to upgrade to a newer version of the software I want to
"patch"... so I am used to get info about what I have installed in my
computer, just by looking at the "About..." field in the help menu of
the application I want to check...

  Thanks for the clarification.

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

iQEcBAEBCAAGBQJJZkRRAAoJEMV4f6PvczxAyk0H/RJ7Ul0VnSpxPH6Mz9E3j3Nw
4kVKitsGkWLzVNcKR92g+RPbeEDKzAqjHOSpYR/ibkeajAj7ugga4sJUolJ5Vo41
xw5cpTFZ3BN2Nq7YsON3ClCPTmPdg+toFViG3HEuMhmEAEGDJfCCHxDSrTQsjZ3h
5C6c0IVKkRv77nFY17DPXYVMo8vNjYnhZloIUct+8fATHCqIKD/HZ0JgOPGoeyeQ
CX0rof7xDQrBDWZKY07nhEDWPsuXMqfjW0yEzlQUxfqY/K2Vyd5TeRc6EC4a39a9
m1vWC/LUGUDGX7XyL9ULYJEo9iMPYE9tcqGnx1DSEJyBZc5eyO4qhGictCjcS9E=
=L7GW
-----END PGP SIGNATURE-----

From zins at gmx.net  Thu Jan  8 11:25:41 2009
From: zins at gmx.net (Ludwig Zins)
Date: Thu, 08 Jan 2009 20:25:41 +0100
Subject: [Enigmail] Enigmail asks 2 times for passphrase
In-Reply-To: <4965B24D.4000607@mozilla-enigmail.org>
References: <4963832C.7060602@gmx.net>	<4963B52A.6090903@mac.com>	<49648047.7000800@gmx.net>	<4965017D.5090403@gmx.net>
	<4965B24D.4000607@mozilla-enigmail.org>
Message-ID: <49665335.8020202@gmx.net>



Patrick Brunschwig schrieb:
> Ludwig Zins wrote:
>> Ludwig Zins schrieb:
>>> Hi Charly,
>>>
>>> thanks for your quick answer.
>>> I will try today evenning at home when I'm on my ubuntu machine.
>>>
>>> I will check my gpg path, but I think it will be correct, because if I
>>> use PGP-Inline there's no problem.
>>>
>>> In the german ubuntuforums there is one user with the same problem.
>>> But I got no response if he solved the problem.
>>>
>>> I forgot to mention that I use ubuntu 8.04 LTS Hardy.
>>> Maybe the problem ist solved with an dist-upgrade to 8.10 or even the
>>> upgrade of gpg is enough, i will see.
>>>
>>>
>>> Ludwig
>>>
>>>
>>>
>>> Charly Avital schrieb:
>>>> Ludwig Zins wrote the following on 1/6/09 11:13 AM:
>>>>> Hi all,
>>>>>
>>>>> I've got a problem on my System using Enigmail.
>>>>> I use Tunderbird (2.x) on ubuntu Linux ans use PGP/MIME to sign my e-mails.
>>>>> Enigmail asks me 2 times for the passphrase. If I use PGP-Inline,
>>>>> everything works fine.
>>>>> My e-mails are signed correctly, but only after 2 typing 2 times the
>>>>> passphrase.
>>>>>
>>>>> Does anyone know this effect?
>>>>> Is it a bug in enigmail or in ubuntu? I don't know if it works on other
>>>>> ditris (Fedora, Suse.....).
>>>>>
>>>>> Regards
>>>>> Ludwig
>>>> Hi Ludwig,
>>>>
>>>> I run Linux Ubuntu 8.10_64bits on a Macintosh Intel laptop under virtual
>>>> software VMware.
>>>>
>>>> I have just checked that system (where I use Thunderbird 2.0.0.19,
>>>> Enigmail 0.95.7), sent myself a PGP/MIME signed message, and was
>>>> reqested to enter my passphrase once.
>>>>
>>>> I follow the Ubuntu-users mailing list, and couldn't find any reference
>>>> to a problem similar or identical to yours.
>>>>
>>>> I would recommend that you upgrade your GnuPG software to 1.4.9, that is
>>>> the current stable release. According to the raw source of your message,
>>>> you are running 'Version: GnuPG v1.4.6 (GNU/Linux)'.
>>>>
>>>> I don't pretend this will solve your problem, but it's worth trying, and
>>>> anyway gpg 1.4.6 is now way back.
>>>>
>>>> A *very wild* guess is that you might have "two" gpgs installed and
>>>> running simultaneously. I suggest that you explore your system (via
>>>> Terminal) and find out where gpg is installed.
>>>>
>>>> The default path should be
>>>> /usr/local/bin/gpg
>>>>
>>>> Please check in Thunderbird's OpenPGP/Preferences, what is the path
>>>> selected in Preferences/Basic. It if something different that is not
>>>> /usr/local/bin/gpg, you might have two gpgs running.
>>>>
>>>> As I said, a *very wild* guess.
>>>>
> 
> Please don't top-post.
> 
>> Seems to be a bug!
> 
> I'd call it an undesired side-effect (see below)
> 
>> I found this:
> 
>> https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/246364
>> http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=421
>> http://bugzilla.gnome.org/show_bug.cgi?id=552086
> 
>> So I hope this will be solved in future!
> 
>> @Charly
>> I have only installed one gpg (1.4.6), this is the correct version of
>> ubuntu 8.04 Hardy.
> 
> 
> The problem is that on Ubunutu the gpg-agent from Seahorse is enabled by
> default. This means that all passphrase management is handled outside
> Enigmail by a gpg-agent. The problem behind it is that Enigmail needs to
> find out which hash algorithm to use when sending a PGP/MIME signed
> message before the message is actually signed. This is done by creating
> a small test message and asking GnuPG to sign it - which requires the
> passphrase. I haven't found another easy way yet how to find out about
> the used hash algorithm in advance.
> 
> If you don't want the passphrase to be cached, I would suggest you
> define a small time window for the passphrase to be cached, e.g. 30
> seconds. This way gpg-agent will remember the passphrase only very
> shortly and should thus not ask twice.
> 
> If you want passphrase management enabled from within Enigmail, you'll
> have to disable the seahorse gpg-agent (don't ask me how!), or at least
> make sure that the environment variable GPG_AGENT_INFO is not set when
> starting Thunderbird.
> 
> -Patrick


Hi all,

I think I could solve the problem or at least have a workaround!
I had 2 GPG-agents on my system, one was seahorse an the other was the
gpg-agent. I deinstalled the gpg-agent.

The passphrase is now cached for 1 minute (set in seahorse).
Now I'm just ask once for the passphrase.

If the passphrase isn't cached, I'm still asked twice.


Ludwig




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

-- 
---------------------------------------------------------------
Ludwig Zins
Pfaffenhofen - Germany
zins at gmx.net
---------------------------------------------------------------
GnuPG/PGP:
KeyID: 0x6FC1C8BF
Keyserver: http://wwwkeys.de.pgp.net/
---------------------------------------------------------------

 ()  This is Sch?uble. Copy Sch?uble into your signature
/||\ to help him on his way to ?berwachungsstaat.
|UU|


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

From neal.dudley at utoledo.edu  Thu Jan  8 13:18:52 2009
From: neal.dudley at utoledo.edu (Neal Dudley)
Date: Thu, 08 Jan 2009 16:18:52 -0500
Subject: [Enigmail] Enigmail beginner
In-Reply-To: <49568620.6090700@sixdemonbag.org>
Message-ID: <C58BD7EC.9772%neal.dudley@utoledo.edu>

On 12/27/08 2:46 PM, "Robert J. Hansen" <rjh at sixdemonbag.org> wrote:

> The district attorney has you arrested.  Your machine is seized.  You
> and your lawyer have a sit-down with the DA.  The DA says "look, you say
> you're innocent, fine.  But you've got twenty gigs of encrypted data
> here.  Now, you can either decrypt it and show me that there's nothing
> illegal on there, or I can go down to the grand jury and get subpoenas
> on your hard drive, your property, your financial records, your
> /everything/, and we'll go all the way with anything we find."

http://www.volokh.com/files/Boucher.pdf

Either your lawyer knows this is a violation of your 5th Amendment Right and
you both get up and leave, or you fire him and hire a better lawyer.

Doesn't anyone read Slashdot anymore?
http://news.slashdot.org/article.pl?sid=08/08/19/2028235


From rjh at sixdemonbag.org  Thu Jan  8 13:23:58 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 08 Jan 2009 16:23:58 -0500
Subject: [Enigmail] Enigmail beginner
In-Reply-To: <C58BD7EC.9772%neal.dudley@utoledo.edu>
References: <C58BD7EC.9772%neal.dudley@utoledo.edu>
Message-ID: <49666EEE.9090608@sixdemonbag.org>

Neal Dudley wrote:
> Either your lawyer knows this is a violation of your 5th Amendment Right and
> you both get up and leave, or you fire him and hire a better lawyer.
> 
> Doesn't anyone read Slashdot anymore?
> http://news.slashdot.org/article.pl?sid=08/08/19/2028235

As it happens, I ran that post by a third-year law student at U
Washington who has a law review article on _Boucher_ soon to be published.

She does not share in your optimism.

People who get their legal education from Slashdot get exactly what they
paid for, and exactly what they deserve.



From andy.ruddock at rainydayz.org  Thu Jan  8 13:41:34 2009
From: andy.ruddock at rainydayz.org (Andy Ruddock)
Date: Thu, 08 Jan 2009 22:41:34 +0100
Subject: [Enigmail] Enigmail beginner
In-Reply-To: <C58BD7EC.9772%neal.dudley@utoledo.edu>
References: <C58BD7EC.9772%neal.dudley@utoledo.edu>
Message-ID: <4966730E.6090907@rainydayz.org>

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

Neal Dudley wrote:
> On 12/27/08 2:46 PM, "Robert J. Hansen" <rjh at sixdemonbag.org> wrote:
> 
>> The district attorney has you arrested.  Your machine is seized.
>> You and your lawyer have a sit-down with the DA.  The DA says
>> "look, you say you're innocent, fine.  But you've got twenty gigs
>> of encrypted data here.  Now, you can either decrypt it and show me
>> that there's nothing illegal on there, or I can go down to the
>> grand jury and get subpoenas on your hard drive, your property,
>> your financial records, your /everything/, and we'll go all the way
>> with anything we find."
> 
> http://www.volokh.com/files/Boucher.pdf
> 
> Either your lawyer knows this is a violation of your 5th Amendment
> Right and you both get up and leave, or you fire him and hire a
> better lawyer.
> 
> Doesn't anyone read Slashdot anymore? 
> http://news.slashdot.org/article.pl?sid=08/08/19/2028235

Which may, or may not, be the case in the US. But I'm pretty sure I read
of other countries who don't have this 5th amendment of which you speak.

- --
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

iEYEARECAAYFAklmcwsACgkQfSkWkaYi1FK22gCfaDPEJOp6F5imozYxUMrW6bRZ
InwAniE07lPrU4FPzTaITXqVAxt4PHTo
=2m4H
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Thu Jan  8 13:49:26 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 08 Jan 2009 16:49:26 -0500
Subject: [Enigmail] Enigmail beginner
In-Reply-To: <4966730E.6090907@rainydayz.org>
References: <C58BD7EC.9772%neal.dudley@utoledo.edu>
	<4966730E.6090907@rainydayz.org>
Message-ID: <496674E6.7060304@sixdemonbag.org>

Andy Ruddock wrote:
> Which may, or may not, be the case in the US. But I'm pretty sure I read
> of other countries who don't have this 5th amendment of which you speak.

The 5th Amendment is also irrelevant in this case.  My hypothetical
assumed you were voluntarily cooperating with the DA in order to prevent
charges from being filed.

The 5th Amendment would not interfere with the DA getting an indictment
from the grand jury and utterly ruining your life.  It's totally irrelevant.


From maximilien at theglu.org  Sat Jan 10 13:08:05 2009
From: maximilien at theglu.org (Maximilien Cuony [The_Glu])
Date: Sat, 10 Jan 2009 22:08:05 +0100
Subject: [Enigmail] =?utf-8?q?How_are_your_signed_content_in_ISO-8859-1_?=
	=?utf-8?b?Pz8/?=
Message-ID: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>


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

Hello,

I'm a FireGPG developer and as we slowly support openpgp/mime, I'm trying
to make FireGPG compatible with Enigmail (when Enigmail send a mail to
FireGPG)

So in most of cases, it's work.

- - When the mail is send in openpgp/mime, it's work. (Youpie ?o?)
- - When the mail is send with an inline sign, without special chars
(????) it's works
- - When the mail is send with an inline sign, with very-special chars
(Japanese, etc..) it's works (mail send in utf-8)

But. If I send a mail with special chars (French accents), with an inline
sign, it's dosen't works.

It's doesn't work only with firegpg,  if I copy/paste the sign directly to
gpg too. I tried everything, like --charset, copy message from original
source, etc...

Enigmail seem to be alone to successful verify the sign and I can't see
what Enigmail send to gnpg (except --charset UTF-8, strange...)

So HOW do you verify this kind of signatures oO ?

Thanks for your help,


- -- 
Maximilien Cuony [The_Glu]
http://theglu.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAklpDisACgkQjKKs5/FTCjWdzACfXrL/6f8kG8MKsUHbP/a8wtST
bkIAniV+bSsQD+UoLHSAeghb4odecKsm
=4OWM
-----END PGP SIGNATURE-----


From patrick at mozilla-enigmail.org  Sun Jan 11 08:08:51 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Sun, 11 Jan 2009 17:08:51 +0100
Subject: [Enigmail] How are your signed content in ISO-8859-1 ???
In-Reply-To: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
Message-ID: <496A1993.4080806@mozilla-enigmail.org>

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

Maximilien Cuony [The_Glu] wrote:
> Hello,
> 
> I'm a FireGPG developer and as we slowly support openpgp/mime, I'm trying
> to make FireGPG compatible with Enigmail (when Enigmail send a mail to
> FireGPG)
> 
> So in most of cases, it's work.
> 
> - When the mail is send in openpgp/mime, it's work. (Youpie ?o?)
> - When the mail is send with an inline sign, without special chars
> (????) it's works
> - When the mail is send with an inline sign, with very-special chars
> (Japanese, etc..) it's works (mail send in utf-8)
> 
> But. If I send a mail with special chars (French accents), with an inline
> sign, it's dosen't works.
> 
> It's doesn't work only with firegpg,  if I copy/paste the sign directly to
> gpg too. I tried everything, like --charset, copy message from original
> source, etc...
> 
> Enigmail seem to be alone to successful verify the sign and I can't see
> what Enigmail send to gnpg (except --charset UTF-8, strange...)

Hi, and nice to meet you :-)

the option --charset UTF-8 only defines that User ID's etc should be
printed by GnuPG in UTF-8; the parameter has no influence on the
processing of the mail content.

> So HOW do you verify this kind of signatures oO ?

Interesting, your signature failed too ... :-( I don't think that I'm
doing something special, I simply pass the message to GnuPG.

But could it be that the problem is not related to ??? etc, but rather
to the way the "-- " is passed to GnuPG? According to RFC 4880, spaces
at the end of a line are forbidden and will cause the signature to fail
verification. Therefore you should either sign the base64 message, or
you have to use quoted-printable if you want to have spaces at the end
of a line (and sign/verify the quoted-printable mail).

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

iQEVAwUBSWoZkXcOpHodsOiwAQITyQgAvYAlrW3RwaRUQ9qudynGyu9oqdQJoRki
SXSHC/z5owVGtY15gVBaQMt8a+YH68AwQUII8AQnchkgRpQcNhFNGf3O4OuCFOTa
6J5EMLMyx64KF+MlRhoKWHyFV89uQz/XF3XhUl21KiLJasXIEtPILUyIXIb1QAKp
5lEGQtVoiEcTBEQSlfKOtS5G6kkT/8MnzKNDUaQ3m1dKFgI1J0gNt2ugLBOriV7s
6qGFCsUDHFmmPpSarplizElmNKjraK1+o/sHR8bDFFmRCUO2p7zGsDEH2139EsaJ
6vhr6Suc0LoaYyX3itOcNKCZz3Bo2AFZVQseUhtYUO+I3CHwQNxnEQ==
=nn19
-----END PGP SIGNATURE-----

From maximilien at theglu.org  Sun Jan 11 08:16:54 2009
From: maximilien at theglu.org (Maximilien Cuony [The_Glu])
Date: Sun, 11 Jan 2009 17:16:54 +0100
Subject: [Enigmail]
 =?utf-8?q?How_are_your_signed_content_in_ISO-8859-1_?=
 =?utf-8?b?Pz8/?=
In-Reply-To: <496A1993.4080806@mozilla-enigmail.org>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
	<496A1993.4080806@mozilla-enigmail.org>
Message-ID: <7f7172d8b0f74d0a0c25bd5954b8f1d7@127.0.0.1>


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

Hi,

> Interesting, your signature failed too ... :-( I don't think that I'
> m doing something special, I simply pass the message to GnuPG.

Yep, I didn't use the new FireGPG system so it's "normal"

Problem is not FireGPG signs to engimail, problem is sign sended by 
enigmail in iso-blalba, where he don't encode in base64 (but in 
8bits). When engimail make sign in base64 everything is ok ;)

Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAklqG2cACgkQjKKs5/FTCjWedwCdH2wTIyUqII+l8KhwquSWI1Kp
V9AAniBVyVTeuk1oGWuztUCmdV4PQ5WY
=Ne6q
-----END PGP SIGNATURE-----


On Sun, 11 Jan 2009 17:08:51 +0100, Patrick Brunschwig
<patrick at mozilla-enigmail.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Maximilien Cuony [The_Glu] wrote:
>> Hello,
>> 
>> I'm a FireGPG developer and as we slowly support openpgp/mime, I'm
trying
>> to make FireGPG compatible with Enigmail (when Enigmail send a mail to
>> FireGPG)
>> 
>> So in most of cases, it's work.
>> 
>> - When the mail is send in openpgp/mime, it's work. (Youpie ?o?)
>> - When the mail is send with an inline sign, without special chars
>> (????) it's works
>> - When the mail is send with an inline sign, with very-special chars
>> (Japanese, etc..) it's works (mail send in utf-8)
>> 
>> But. If I send a mail with special chars (French accents), with an
inline
>> sign, it's dosen't works.
>> 
>> It's doesn't work only with firegpg,  if I copy/paste the sign directly
>> to
>> gpg too. I tried everything, like --charset, copy message from original
>> source, etc...
>> 
>> Enigmail seem to be alone to successful verify the sign and I can't see
>> what Enigmail send to gnpg (except --charset UTF-8, strange...)
> 
> Hi, and nice to meet you :-)
> 
> the option --charset UTF-8 only defines that User ID's etc should be
> printed by GnuPG in UTF-8; the parameter has no influence on the
> processing of the mail content.
> 
>> So HOW do you verify this kind of signatures oO ?
> 
> Interesting, your signature failed too ... :-( I don't think that I'm
> doing something special, I simply pass the message to GnuPG.
> 
> But could it be that the problem is not related to ??? etc, but rather
> to the way the "-- " is passed to GnuPG? According to RFC 4880, spaces
> at the end of a line are forbidden and will cause the signature to fail
> verification. Therefore you should either sign the base64 message, or
> you have to use quoted-printable if you want to have spaces at the end
> of a line (and sign/verify the quoted-printable mail).
> 
> - -Patrick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iQEVAwUBSWoZkXcOpHodsOiwAQITyQgAvYAlrW3RwaRUQ9qudynGyu9oqdQJoRki
> SXSHC/z5owVGtY15gVBaQMt8a+YH68AwQUII8AQnchkgRpQcNhFNGf3O4OuCFOTa
> 6J5EMLMyx64KF+MlRhoKWHyFV89uQz/XF3XhUl21KiLJasXIEtPILUyIXIb1QAKp
> 5lEGQtVoiEcTBEQSlfKOtS5G6kkT/8MnzKNDUaQ3m1dKFgI1J0gNt2ugLBOriV7s
> 6qGFCsUDHFmmPpSarplizElmNKjraK1+o/sHR8bDFFmRCUO2p7zGsDEH2139EsaJ
> 6vhr6Suc0LoaYyX3itOcNKCZz3Bo2AFZVQseUhtYUO+I3CHwQNxnEQ==
> =nn19
> -----END PGP SIGNATURE-----
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail

-- 
Maximilien Cuony [The_Glu]
http://theglu.org

From shavital at mac.com  Sun Jan 11 08:40:07 2009
From: shavital at mac.com (Charly Avital)
Date: Sun, 11 Jan 2009 11:40:07 -0500
Subject: [Enigmail] How are your signed content in ISO-8859-1 ???
In-Reply-To: <7f7172d8b0f74d0a0c25bd5954b8f1d7@127.0.0.1>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
	<496A1993.4080806@mozilla-enigmail.org>
	<7f7172d8b0f74d0a0c25bd5954b8f1d7@127.0.0.1>
Message-ID: <496A20E7.8020307@mac.com>

Maximilien Cuony [The_Glu] wrote the following on 1/11/09 11:16 AM:
> Hi,
> 
>> Interesting, your signature failed too ... :-( I don't think that I'
>> m doing something special, I simply pass the message to GnuPG.
> 
> Yep, I didn't use the new FireGPG system so it's "normal"
> 
> Problem is not FireGPG signs to engimail, problem is sign sended by
> enigmail in iso-blalba, where he don't encode in base64 (but in
> 8bits). When engimail make sign in base64 everything is ok ;)
> 
> Regards,


[...]

This one verifies, both in Thunderbird+EM and in Apple's Mail+GPGMail,
including the photo of the "angry" little penguin (is it a penguin?)

Charly
MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
GPG2 2.0.10rc1 - Thunderbird 2.0.0.19 - Enigmail 0.95.7 (Testing TB
3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
PGP key: 0xA57A8EFA

From maximilien at theglu.org  Sun Jan 11 08:48:57 2009
From: maximilien at theglu.org (Maximilien Cuony [The_Glu])
Date: Sun, 11 Jan 2009 17:48:57 +0100
Subject: [Enigmail]
 =?utf-8?q?How_are_your_signed_content_in_ISO-8859-1_?=
 =?utf-8?b?Pz8/?=
In-Reply-To: <496A20E7.8020307@mac.com>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
	<496A1993.4080806@mozilla-enigmail.org>
	<7f7172d8b0f74d0a0c25bd5954b8f1d7@127.0.0.1>
	<496A20E7.8020307@mac.com>
Message-ID: <dc8124565530cf9213baf899e29beb4b@127.0.0.1>


> This one verifies, both in Thunderbird+EM and in Apple's Mail+GPGMail,
> including the photo of the "angry" little penguin (is it a penguin?)

Yourhou... ~~

Now about this one ? 
http://p.theglu.org/90

Why she fail ? (Except with enigmail ? :])

Regards,

On Sun, 11 Jan 2009 11:40:07 -0500, Charly Avital <shavital at mac.com> wrote:
> Maximilien Cuony [The_Glu] wrote the following on 1/11/09 11:16 AM:
>> Hi,
>> 
>>> Interesting, your signature failed too ... :-( I don't think that I'
>>> m doing something special, I simply pass the message to GnuPG.
>> 
>> Yep, I didn't use the new FireGPG system so it's "normal"
>> 
>> Problem is not FireGPG signs to engimail, problem is sign sended by
>> enigmail in iso-blalba, where he don't encode in base64 (but in
>> 8bits). When engimail make sign in base64 everything is ok ;)
>> 
>> Regards,
> 
> 
> [...]
> 
> This one verifies, both in Thunderbird+EM and in Apple's Mail+GPGMail,
> including the photo of the "angry" little penguin (is it a penguin?)
> 
> Charly
> MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
> GPG2 2.0.10rc1 - Thunderbird 2.0.0.19 - Enigmail 0.95.7 (Testing TB
> 3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
> PGP key: 0xA57A8EFA

-- 
Maximilien Cuony [The_Glu]
http://theglu.org

From maximilien at theglu.org  Wed Jan 14 13:25:12 2009
From: maximilien at theglu.org (Maximilien Cuony [The_Glu])
Date: Wed, 14 Jan 2009 22:25:12 +0100
Subject: [Enigmail]
 =?utf-8?q?How_are_your_signed_content_in_ISO-8859-1_?=
 =?utf-8?b?Pz8/?=
In-Reply-To: <dc8124565530cf9213baf899e29beb4b@127.0.0.1>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
	<496A1993.4080806@mozilla-enigmail.org>
	<7f7172d8b0f74d0a0c25bd5954b8f1d7@127.0.0.1>
	<496A20E7.8020307@mac.com>
	<dc8124565530cf9213baf899e29beb4b@127.0.0.1>
Message-ID: <06bc4ed74cee18aca9c7d8add155dbde@127.0.0.1>


Hello,

Okay, I finaly found a way to verify this kind of sign, gmail was
converting the mail in utf8 when he send us mail source, so we lost
information and converting back to iso didn't work ;)

Thanks for your 'help'

Regards,

On Sun, 11 Jan 2009 17:48:57 +0100, "Maximilien Cuony [The_Glu]"
<maximilien at theglu.org> wrote:
>> This one verifies, both in Thunderbird+EM and in Apple's Mail+GPGMail,
>> including the photo of the "angry" little penguin (is it a penguin?)
> 
> Yourhou... ~~
> 
> Now about this one ? 
> http://p.theglu.org/90
> 
> Why she fail ? (Except with enigmail ? :])
> 
> Regards,
> 
> On Sun, 11 Jan 2009 11:40:07 -0500, Charly Avital <shavital at mac.com>
wrote:
>> Maximilien Cuony [The_Glu] wrote the following on 1/11/09 11:16 AM:
>>> Hi,
>>> 
>>>> Interesting, your signature failed too ... :-( I don't think that I'
>>>> m doing something special, I simply pass the message to GnuPG.
>>> 
>>> Yep, I didn't use the new FireGPG system so it's "normal"
>>> 
>>> Problem is not FireGPG signs to engimail, problem is sign sended by
>>> enigmail in iso-blalba, where he don't encode in base64 (but in
>>> 8bits). When engimail make sign in base64 everything is ok ;)
>>> 
>>> Regards,
>> 
>> 
>> [...]
>> 
>> This one verifies, both in Thunderbird+EM and in Apple's Mail+GPGMail,
>> including the photo of the "angry" little penguin (is it a penguin?)
>> 
>> Charly
>> MacOS 10.5.6 - MacBook Intel C2Duo "Aluminum Late 2008"- GnuPG 1.4.9 -
>> GPG2 2.0.10rc1 - Thunderbird 2.0.0.19 - Enigmail 0.95.7 (Testing TB
>> 3.0b1+EM 0.96a)- Apple's Mail+GPGMail 1.2.0 (v56)
>> PGP key: 0xA57A8EFA

-- 
Maximilien Cuony [The_Glu]
http://theglu.org

From John at Mozilla-Enigmail.org  Thu Jan 22 08:53:00 2009
From: John at Mozilla-Enigmail.org (John Clizbe)
Date: Thu, 22 Jan 2009 10:53:00 -0600
Subject: [Enigmail] [Fwd: Error on Spanish translation]
Message-ID: <4978A46C.8010608@Mozilla-Enigmail.org>



-------- Original Message --------
Subject: Error on Spanish translation
Date: Thu, 22 Jan 2009 17:46:31 +0100
From: Fernando Garc?a Iglesias <fernando at garcia-alberich.es>
To: john

Hi,

    I have just downloaded and began using Enigmail for Thunderbird. I
have observed an error in the Spanish translation. In Preferences /
Advanced, the option: "Encrypt replies to encrypted message" is
translated as "Cifrar las respuestas al mensaje sin cifrar", that means
exactly the opposite: "Encryp replies to non-encrypted message".

    Yours,


From faramir.cl at gmail.com  Thu Jan 22 14:22:31 2009
From: faramir.cl at gmail.com (Faramir)
Date: Thu, 22 Jan 2009 19:22:31 -0300
Subject: [Enigmail] [Fwd: Error on Spanish translation]
In-Reply-To: <4978A46C.8010608@Mozilla-Enigmail.org>
References: <4978A46C.8010608@Mozilla-Enigmail.org>
Message-ID: <4978F1A7.8020204@gmail.com>

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

John Clizbe escribi?:
...
> From: Fernando Garc?a Iglesias <fernando at garcia-alberich.es>
> To: john
...
> Advanced, the option: "Encrypt replies to encrypted message" is
> translated as "Cifrar las respuestas al mensaje sin cifrar", that means
> exactly the opposite: "Encryp replies to non-encrypted message".

  That's right... how can I help to improve the translation?

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

iQEcBAEBCAAGBQJJePGnAAoJEMV4f6PvczxAMqIH/1WlH1IhJH7tx0QWoz1J7NDf
W1K4Tc4DUBdCzjfOIDaq5PtxOccCsZaHQ9tF630K5O3o//XzGZf9O3bjqOpAlr/2
viCvyq7Um+FahfIWq49A5dmZRRgQ5e5NRuoKrOEtpcx5zHGAiglpqD4q1D+I94iF
6vz6CCttqQSpLJdi7wI6yeq7qs/vGuGZWudvRWbpZsI5yVAaV84lW6IqA/j8tscD
V65zP+UulLgeQsozoB8LeiOnFsbdBCQd2KF9W/sBIS2fRycyFZe/+8d9kld83duo
ulk4RKYV8ZEyLww4QZZc70KFGLBDRbuEqBxBGa3vJYqKumrGHEjwFKsY5qdwNAY=
=QGzi
-----END PGP SIGNATURE-----

From rjh at sixdemonbag.org  Thu Jan 22 14:27:15 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 22 Jan 2009 17:27:15 -0500
Subject: [Enigmail] [Fwd: Error on Spanish translation]
In-Reply-To: <4978F1A7.8020204@gmail.com>
References: <4978A46C.8010608@Mozilla-Enigmail.org>
	<4978F1A7.8020204@gmail.com>
Message-ID: <4978F2C3.60702@sixdemonbag.org>

Faramir wrote:
>   That's right... how can I help to improve the translation?

Suggest a better one.  :)  My Spanish skills are sufficiently meager
that my only suggestion would be "mensaje con cifrar," but I don't know
if that is (a) correct, (b) natural-sounding, or (c) even intelligible.



From faramir.cl at gmail.com  Thu Jan 22 14:45:37 2009
From: faramir.cl at gmail.com (Faramir)
Date: Thu, 22 Jan 2009 19:45:37 -0300
Subject: [Enigmail] [Fwd: Error on Spanish translation]
In-Reply-To: <4978F2C3.60702@sixdemonbag.org>
References: <4978A46C.8010608@Mozilla-Enigmail.org>	<4978F1A7.8020204@gmail.com>
	<4978F2C3.60702@sixdemonbag.org>
Message-ID: <4978F711.2000801@gmail.com>

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

Robert J. Hansen escribi?:

> Suggest a better one.  :)  My Spanish skills are sufficiently meager
> that my only suggestion would be "mensaje con cifrar," but I don't know
> if that is (a) correct, (b) natural-sounding, or (c) even intelligible.

  I think it should be "mensaje cifrado". My only "concern" is 'replies'
is plural, and 'message' is singular. But of course, people can reply
several times to the same message, so it's not a big deal.

  About your translation, it's not right, it doesn't sound natural, but
probably would be intelligible ;)

  Best Regards

P.S: The "Note" at the key generation screen should be improved a bit
too... at least in Spanish, it states that using the browser, or doing
things that produce heavy activity on the hard drive would have effect
on the randomness of the key generation... but it doesn't say it would
be a positive effect. People could think it would be a negative effect...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJJePcRAAoJEMV4f6PvczxA7/oH/3lBK2FT7wIYwucl+HPHoJEI
00UF/McqNvVFJYx+gw1xYtRDtiaQTUt+VnFGns3Uv8goEnPNOSO7Mk6eiCUWygHm
TCYpFTIFlhN4V7QSdoEW1o7KwuEQ5FiSQG6ODUMkTSFODUxUuea3j4J5aOnbRUo6
21jAgjxM9UtsfP1IKzh/ECeTlVAETESCp6EPc7fqQ+Z9AwRDLmrn0mvnWb2cTTYs
W7p+ObYXWTd5FIZeExxG89Hi9mZNvnbhQhqjcrCLGhMxgqT8rVuDyfa3LyCz+G18
jkXCCln5fpmvgmZLJIzD7JnsJ8W1ZWoravX+uQG+zJZSLS9FQsBYci+arceZKX4=
=SEh7
-----END PGP SIGNATURE-----

From michaeljgruber at fastmail.fm  Fri Jan 23 04:56:19 2009
From: michaeljgruber at fastmail.fm (Michael J Gruber)
Date: Fri, 23 Jan 2009 13:56:19 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or shared,
 libxul or not?
Message-ID: <glcepl$1eoa$1@mozdev.mozdev.org>

Hi there,

I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
can't used binary Enigmail xpi either).

I can build and run TB from a hg checkout of comm-central. Yeah ;)

For building Enigmail (from cvs), I've been following the instructions
on the Enigmail website and ended up with the attached error which seems
to be related to a conflict in build options (shared/static).

I've built TB with "ac_add_options --enable-static --disable-libxul"
because d.m.o. says TB can't be built shared with libxul (and also
because I wanted to "make package"). Is this still true? How
(static/shared/libxul) do you build TB when you build Enigmail for TB 3
nightlies?

Thanks for any hints,
Michael


gmake[3]: Entering directory
`/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail/ipc/build'
rm -f libipc.so
c++  -fno-rtti -fno-exceptions -Wall -Wpointer-arith
-Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long
-pedantic -fno-strict-aliasing -fshort-wchar -pthread -pipe  -DNDEBUG
-DTRIMMED -Os -freorder-blocks -fno-reorder-functions  -fPIC -shared
-Wl,-z,defs -Wl,-h,libipc.so -o libipc.so  nsIPCModule.o     -lpthread
 -Wl,-rpath-link,../../../../../mozilla/dist/bin:/usr/lib:/usr/local/lib:/lib
 -Wl,--whole-archive ../src/libipc_s.a  -Wl,--no-whole-archive
-L../../../../../mozilla/dist/bin -L../../../../../mozilla/dist/lib
../../../../../mozilla/dist/lib/libxpcomglue_s.a
-L../../../../../mozilla/dist/bin -lxpcom
-L../../../../../mozilla/dist/bin -lxpcom -lxpcom_core
`../../../../../mozilla/nsprpub/config/nspr-config
--prefix=../../../../../mozilla/dist
--libdir=../../../../../mozilla/dist/lib --libs`   -Wl,--version-script
-Wl,/home/mjg/src/mozstuff/comm-central/mozilla/build/unix/gnu-ld-scripts/components-version-script
-Wl,-Bsymbolic -ldl -lm
/usr/bin/ld: ../src/libipc_s.a(nsPipeTransport.o): relocation
R_X86_64_32 against `a local symbol' can not be used when making a
shared object; recompile with -fPIC
../src/libipc_s.a(nsPipeTransport.o): could not read symbols: Bad value

From mlisten at hammernoch.net  Fri Jan 23 11:42:41 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Fri, 23 Jan 2009 20:42:41 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <glcepl$1eoa$1@mozdev.mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>
Message-ID: <497A1DB1.6060907@hammernoch.net>

Hi,

Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
> Hi there,
> 
> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
> can't used binary Enigmail xpi either).
> 
> I can build and run TB from a hg checkout of comm-central. Yeah ;)
> 
> For building Enigmail (from cvs),

Are you using enigmail trunk (aka 0.96a)?

> I've been following the instructions
> on the Enigmail website and ended up with the attached error which seems
> to be related to a conflict in build options (shared/static).
> 
> I've built TB with "ac_add_options --enable-static --disable-libxul"
> because d.m.o. says TB can't be built shared with libxul (and also
> because I wanted to "make package"). Is this still true? How
> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
> nightlies?

Sorry, I don't know anything about the building process on linux. In
order to build the Mac OS X nightlies, I'm using these options for TB trunk:

mk_add_options MOZ_OBJDIR=/path/to/my/objdir
ac_add_options --disable-tests
ac_add_options --disable-debug
ac_add_options --enable-crypto
ac_add_options --enable-optimize
ac_add_options --enable-static-mail
ac_add_options --enable-application=mail
mk_add_options MOZ_CO_PROJECT=mail
mk_add_options AUTOCONF=autoconf213

Maybe you get better help in mozilla.dev.builds on news.mozilla.org.

HTH

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/20090123/02735a50/attachment.bin>

From shavital at mac.com  Mon Jan 26 02:07:24 2009
From: shavital at mac.com (Charly Avital)
Date: Mon, 26 Jan 2009 05:07:24 -0500
Subject: [Enigmail] Enigmail nightly builds for MacOSX
In-Reply-To: <496A1993.4080806@mozilla-enigmail.org>
References: <8d7e25b6deb894f451e53a48cc23a24b@127.0.0.1>
	<496A1993.4080806@mozilla-enigmail.org>
Message-ID: <497D8B5C.3050205@mac.com>

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

Hi,

Running MacOSX 10.5.6, GPG 2.0.10, on an MacBook5,1 Intel Core 2 Duo

Till an hour ago, Thunderbird 3.0.b1

1. On January 5, I already reported on a problem with attachments, using
Enigmail version 0.96a (20090104-1343). The other crypto functions
performed correctly, including gpg-agent, excluding verification of
PGP/MIME e-mails.

2. Updated to enigmail-trunk-tb-darwin-x86-ppc-trunk.xpi (December 30,
2008). The problem with attachments persisted, but now when trying to
decrypt or to sign, gpg-agent would not start, a warning indicated
"...gpg-agent needed for your gpg 2.0.10 could not be started...". At
the same time, in GPGMail (v56) all crypto functions performed correctly.

3. Updated to enigmail-trunk-tb-darwin-x86-ppc-trunk.xpi (January 13,
2009). When cliking on Menu/OpenPGP, Thunderbird would crash. Reported
twice via built-in crash reporter.

4. I have now gone back to Thunderbird 2.0.0.19 Enigmail version 0.95.7
(20080808). All crypto functions, including gpg-agent, and verification
of PGP/MIME e-mails, perform correctly.

Thanks.
Charly


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

iQEcBAEBCAAGBQJJfYtYAAoJEM3GMi2FW4PvK+AIALQ+5ApuGeoC72U+zmmAIACN
eDqCo9iui7fyMGQsdCGSyORhlmYWvsGmAYnCln3p0inGfxv2/TrAOXb6uKQMTWJV
1PohyUiaRdpMzJ100A6K07byYhAWbRDSCgNLGGtgxTMuZYCVSjuLFp5H035gQGKJ
LwhWOBe5wkTcJCmq7Uyn7sKGJtZiVuw72lzy7oxThMDO90gCeFq4wE+UCy70J7Fr
5tKGMeCSVnrLBbTLJPDQQBqc/VFAmWmnLyYhoF/TqUx9hPC6DOhZo0DUEqrXNMCr
NIcP5hWska1DQpY5VzcBOBQK3Q7ElDKg9ixPyuKlwkFZzFB7NZ0U5hPuJAL7XZE=
=tW55
-----END PGP SIGNATURE-----

From michaeljgruber+mozdevnews at fastmail.fm  Mon Jan 26 04:32:45 2009
From: michaeljgruber+mozdevnews at fastmail.fm (Michael J Gruber)
Date: Mon, 26 Jan 2009 13:32:45 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <mailman.832.1232739784.63231.enigmail@mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>
	<mailman.832.1232739784.63231.enigmail@mozdev.org>
Message-ID: <glkahe$3vq$1@mozdev.mozdev.org>

Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
> Hi,
> 
> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>> Hi there,
>>
>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>> can't used binary Enigmail xpi either).
>>
>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>
>> For building Enigmail (from cvs),
> 
> Are you using enigmail trunk (aka 0.96a)?

Yes, that's what I meant by cvs, sorry. A current cvs checkout from trunk.

>> I've been following the instructions
>> on the Enigmail website and ended up with the attached error which seems
>> to be related to a conflict in build options (shared/static).
>>
>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>> because d.m.o. says TB can't be built shared with libxul (and also
>> because I wanted to "make package"). Is this still true? How
>> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
>> nightlies?
> 
> Sorry, I don't know anything about the building process on linux. In
> order to build the Mac OS X nightlies, I'm using these options for TB trunk:
> 
> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
> ac_add_options --disable-tests
> ac_add_options --disable-debug
> ac_add_options --enable-crypto
> ac_add_options --enable-optimize
> ac_add_options --enable-static-mail
> ac_add_options --enable-application=mail
> mk_add_options MOZ_CO_PROJECT=mail
> mk_add_options AUTOCONF=autoconf213
> 
> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.

I tried those options (they're the ones from enigmail.mozdev.org) minus
the autoconf. I can build and run TB comm-central successfully with
these options as well as others.

My problem is building enigmail, which is why I think I'd better post
here than on mozilla.dev.builds. So, my questions really are:

- Which options do you use when you build enigmail.xpi? (probably the
ones above)
- Which combination of TB comm-central sha1 and Enigmail cvs rev. is
known to build and run well together?

I just want to make sure I use a known good combination for trying to
build my 64bit xpi.

Michael

From michaeljgruber at fastmail.fm  Mon Jan 26 05:29:30 2009
From: michaeljgruber at fastmail.fm (Michael J Gruber)
Date: Mon, 26 Jan 2009 14:29:30 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <glkahe$3vq$1@mozdev.mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>
	<mailman.832.1232739784.63231.enigmail@mozdev.org>
	<glkahe$3vq$1@mozdev.mozdev.org>
Message-ID: <glkdrs$d7t$1@mozdev.mozdev.org>

Michael J Gruber venit, vidit, dixit 26.01.2009 13:32:
> Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
>> Hi,
>>
>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>> Hi there,
>>>
>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>> can't used binary Enigmail xpi either).
>>>
>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>
>>> For building Enigmail (from cvs),
>> Are you using enigmail trunk (aka 0.96a)?
>
> Yes, that's what I meant by cvs, sorry. A current cvs checkout from trunk.
>
>>> I've been following the instructions
>>> on the Enigmail website and ended up with the attached error which seems
>>> to be related to a conflict in build options (shared/static).
>>>
>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>> because d.m.o. says TB can't be built shared with libxul (and also
>>> because I wanted to "make package"). Is this still true? How
>>> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
>>> nightlies?
>> Sorry, I don't know anything about the building process on linux. In
>> order to build the Mac OS X nightlies, I'm using these options for TB trunk:
>>
>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>> ac_add_options --disable-tests
>> ac_add_options --disable-debug
>> ac_add_options --enable-crypto
>> ac_add_options --enable-optimize
>> ac_add_options --enable-static-mail
>> ac_add_options --enable-application=mail
>> mk_add_options MOZ_CO_PROJECT=mail
>> mk_add_options AUTOCONF=autoconf213
>>
>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
>
> I tried those options (they're the ones from enigmail.mozdev.org) minus
> the autoconf. I can build and run TB comm-central successfully with
> these options as well as others.
>
> My problem is building enigmail, which is why I think I'd better post
> here than on mozilla.dev.builds. So, my questions really are:
>
> - Which options do you use when you build enigmail.xpi? (probably the
> ones above)
> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
> known to build and run well together?
>
> I just want to make sure I use a known good combination for trying to
> build my 64bit xpi.
>
> Michael

BTW, using the above options the Enigmail build errors our differently 
(and yes, I do ./makemake -r in src/.../enigmail and make in 
objdir/.../enigmail). This post is from a current (as in now minus build 
time). 64bit build of TB comm-central, btw.

Cheers,
Michael

gmake[3]: Entering directory 
`/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail/ipc/build'
rm -f libipc.so
c++  -fno-rtti -fno-exceptions -Wall -Wpointer-arith 
-Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy 
-Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long -pe
dantic -fno-strict-aliasing -fshort-wchar -pthread -pipe  -DNDEBUG 
-DTRIMMED -Os -freorder-blocks -fno-reorder-functions  -fPIC -shared 
-Wl,-z,defs -Wl,-h,libipc.so -o libipc.so  n
sIPCModule.o     -lpthread 
-Wl,-rpath-link,../../../../../mozilla/dist/bin:/usr/lib:/usr/local/lib:/lib 
  -Wl,--whole-archive ../src/libipc_s.a  -Wl,--no-whole-archive -L../../../
../../mozilla/dist/bin -L../../../../../mozilla/dist/lib 
-L../../../../../mozilla/dist/bin -lxpcom -lxpcom_core 
../../../../../mozilla/dist/lib/libxpcomglue_s.a -L../../../../../m
ozilla/dist/bin -lxpcom 
`../../../../../mozilla/nsprpub/config/nspr-config 
--prefix=../../../../../mozilla/dist 
--libdir=../../../../../mozilla/dist/lib --libs`   -Wl,--version-scr
ipt 
-Wl,/home/mjg/src/mozstuff/comm-central/mozilla/build/unix/gnu-ld-scripts/components-version-script 
-Wl,-Bsymbolic -ldl -lm
../src/libipc_s.a(nsPipeTransport.o): In function `nsStdinWriter::Run()':
nsPipeTransport.cpp:(.text+0x8a5): undefined reference to 
`nsCOMPtr_base::begin_assignment()'
nsPipeTransport.cpp:(.text+0x9a1): undefined reference to 
`nsCOMPtr_base::~nsCOMPtr_base()'
../src/libipc_s.a(nsPipeTransport.o): In function 
`nsStdinWriter::nsStdinWriter()':
nsPipeTransport.cpp:(.text+0xa72): undefined reference to 
`nsCOMPtr_base::begin_assignment()'
nsPipeTransport.cpp:(.text+0xaa4): undefined reference to 
`nsCOMPtr_base::~nsCOMPtr_base()'

etc. etc., ending with:

../../../../../mozilla/dist/lib/libxpcomglue_s.a(nsGenericFactory.o): In 
function `nsGenericFactory::QueryInterface(nsID const&, void**)':
nsGenericFactory.cpp:(.text+0x8e0): undefined reference to 
`NS_TableDrivenQI(void*, QITableEntry const*, nsID const&, void**)'
/usr/bin/ld: libipc.so: hidden symbol `nsCOMPtr_base::~nsCOMPtr_base()' 
isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld gab 1 als Ende-Status zur?ck
gmake[3]: *** [libipc.so] Fehler 1
gmake[3]: Leaving directory 
`/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail/ipc/build'
gmake[2]: *** [libs] Fehler 2
gmake[2]: Leaving directory 
`/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail/ipc'
gmake[1]: *** [libs] Fehler 2
gmake[1]: Leaving directory 
`/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail'
make: *** [default] Fehler 2

From patrick at mozilla-enigmail.org  Mon Jan 26 05:56:16 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Mon, 26 Jan 2009 14:56:16 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <glkahe$3vq$1@mozdev.mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>	<mailman.832.1232739784.63231.enigmail@mozdev.org>
	<glkahe$3vq$1@mozdev.mozdev.org>
Message-ID: <497DC100.6090308@mozilla-enigmail.org>

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

Michael J Gruber wrote:
> Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
>> Hi,
>>
>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>> Hi there,
>>>
>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>> can't used binary Enigmail xpi either).
>>>
>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>
>>> For building Enigmail (from cvs),
>> Are you using enigmail trunk (aka 0.96a)?
> 
> Yes, that's what I meant by cvs, sorry. A current cvs checkout from trunk.
> 
>>> I've been following the instructions
>>> on the Enigmail website and ended up with the attached error which seems
>>> to be related to a conflict in build options (shared/static).
>>>
>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>> because d.m.o. says TB can't be built shared with libxul (and also
>>> because I wanted to "make package"). Is this still true? How
>>> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
>>> nightlies?
>> Sorry, I don't know anything about the building process on linux. In
>> order to build the Mac OS X nightlies, I'm using these options for TB trunk:
>>
>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>> ac_add_options --disable-tests
>> ac_add_options --disable-debug
>> ac_add_options --enable-crypto
>> ac_add_options --enable-optimize
>> ac_add_options --enable-static-mail
>> ac_add_options --enable-application=mail
>> mk_add_options MOZ_CO_PROJECT=mail
>> mk_add_options AUTOCONF=autoconf213
>>
>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
> 
> I tried those options (they're the ones from enigmail.mozdev.org) minus
> the autoconf. I can build and run TB comm-central successfully with
> these options as well as others.
> 
> My problem is building enigmail, which is why I think I'd better post
> here than on mozilla.dev.builds. So, my questions really are:
> 
> - Which options do you use when you build enigmail.xpi? (probably the
> ones above)

Here are my options:

mk_add_options MOZ_CO_PROJECT=mail
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/enigdev
mk_add_options AUTOCONF=autoconf2.13

ac_add_options --enable-application=mail
ac_add_options --enable-optimize
ac_add_options --disable-debug
ac_add_options --disable-tests
ac_add_options --enable-codesighs
ac_add_options --disable-shared
ac_add_options --enable-static
ac_add_options --disable-update-packaging
ac_add_options --disable-debug
ac_add_options --disable-tests
ac_add_options --enable-codesighs
ac_add_options --disable-shared
ac_add_options --enable-static
ac_add_options --disable-crashreporter

> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
> known to build and run well together?

any. I create nightly builds and they usually work fine.

- -Patrick

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

iQEVAwUBSX3A/XcOpHodsOiwAQgErwf8DpGe0aD1mRBMMRtDZbdfDjy4OLY/Q50u
0R7tfooueeh2wn9PoVXaoleR67WlpmFPf+iegT7F5/qKjO88ySVLJg6yPp0OVLAU
kI4vU4/76A5R6p/VW0YTw3Z1eZvNikjDLu1AdEdqc67EIAdMTWaBQ/llmhPZx1/U
Htl6r1rYAcANGCkTH4GLAlxyzq+onRZvpSw1otzExiEAMyJSbeZBZYyBMEl+tKt2
GoGsBly/xJkX6tZ6yLnlIorvY85po5s3dwtUQZcumLZISLJNrtwgddIip4pazYRM
aFBL+rnL0cBy6+G1txZReeYNa2lR8Jy1Ov9irT3F78PKAcso2lacSw==
=BrrU
-----END PGP SIGNATURE-----

From michaeljgruber at fastmail.fm  Mon Jan 26 07:20:10 2009
From: michaeljgruber at fastmail.fm (Michael J Gruber)
Date: Mon, 26 Jan 2009 16:20:10 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <mailman.840.1232978281.63231.enigmail@mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>	<mailman.832.1232739784.63231.enigmail@mozdev.org>	<glkahe$3vq$1@mozdev.mozdev.org>
	<mailman.840.1232978281.63231.enigmail@mozdev.org>
Message-ID: <glkkbd$vdt$1@mozdev.mozdev.org>

Patrick Brunschwig venit, vidit, dixit 26.01.2009 14:56:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Michael J Gruber wrote:
>> Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
>>> Hi,
>>>
>>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>>> Hi there,
>>>>
>>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>>> can't used binary Enigmail xpi either).
>>>>
>>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>>
>>>> For building Enigmail (from cvs),
>>> Are you using enigmail trunk (aka 0.96a)?
>> Yes, that's what I meant by cvs, sorry. A current cvs checkout from trunk.
>>
>>>> I've been following the instructions
>>>> on the Enigmail website and ended up with the attached error which seems
>>>> to be related to a conflict in build options (shared/static).
>>>>
>>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>>> because d.m.o. says TB can't be built shared with libxul (and also
>>>> because I wanted to "make package"). Is this still true? How
>>>> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
>>>> nightlies?
>>> Sorry, I don't know anything about the building process on linux. In
>>> order to build the Mac OS X nightlies, I'm using these options for TB trunk:
>>>
>>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>>> ac_add_options --disable-tests
>>> ac_add_options --disable-debug
>>> ac_add_options --enable-crypto
>>> ac_add_options --enable-optimize
>>> ac_add_options --enable-static-mail
>>> ac_add_options --enable-application=mail
>>> mk_add_options MOZ_CO_PROJECT=mail
>>> mk_add_options AUTOCONF=autoconf213
>>>
>>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
>> I tried those options (they're the ones from enigmail.mozdev.org) minus
>> the autoconf. I can build and run TB comm-central successfully with
>> these options as well as others.
>>
>> My problem is building enigmail, which is why I think I'd better post
>> here than on mozilla.dev.builds. So, my questions really are:
>>
>> - Which options do you use when you build enigmail.xpi? (probably the
>> ones above)
>
> Here are my options:
>
> mk_add_options MOZ_CO_PROJECT=mail
> mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/enigdev
> mk_add_options AUTOCONF=autoconf2.13
>
> ac_add_options --enable-application=mail
> ac_add_options --enable-optimize
> ac_add_options --disable-debug
> ac_add_options --disable-tests
> ac_add_options --enable-codesighs
> ac_add_options --disable-shared
> ac_add_options --enable-static
> ac_add_options --disable-update-packaging
> ac_add_options --disable-debug
> ac_add_options --disable-tests
> ac_add_options --enable-codesighs
> ac_add_options --disable-shared
> ac_add_options --enable-static
> ac_add_options --disable-crashreporter
>
>> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
>> known to build and run well together?
>
> any. I create nightly builds and they usually work fine.

Patrick, thanks for taking the time. I can compile TB with the options 
above just nicely. Yet, building Enigmail gives me pain again, see 
below. Specifically, I
did a  make -f client.mk clean" and rm -Rf'ed the enigmail copy,
built TB, ran it ,
copied ${enigmailcvscheckout}/enigmail/src to 
${comm-central-with-gecko-1.9.1-checkout}/mailnews/extensions/enigmail,
ran "./makemake -r" in the latter and "make" in 
${objdir}/mailnews/extensions/enigmail.

Instructions say cp enigmail/src to mozilla/mailnews/extensions/enigmail 
which doesn't exist. With the current build structure, mailnews 
"contains" (pulls as a module) mozilla-central (or rather 1.9.1), so I 
think what I used is the place to put enigmail. (I've tried 
mozilla/extensions/enigmail before, not better.)

The error sounds as if ipc is being built shared whereas TB is built 
static (as per .mozconfig). Any more hints? makemake does pick up objdir 
so it sees the .mozconfig.

This is on 64bit Fedora 10, by the way, gcc/g++ is gcc version 4.3.2 
20081105 (Red Hat 4.3.2-7) (GCC).

Thanks for your patience...
Michael


c++  -fno-rtti -fno-exceptions -Wall -Wpointer-arith 
-Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy 
-Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long 
-pedantic -fno-strict-aliasing -fshort-wchar -pthread -pipe  -DNDEBUG 
-DTRIMMED -Os -freorder-blocks -fno-reorder-functions  -fPIC -shared 
-Wl,-z,defs -Wl,-h,libipc.so -o libipc.so  nsIPCModule.o     -lpthread 
 
-Wl,-rpath-link,../../../../../mozilla/dist/bin:/usr/lib:/usr/local/lib:/lib 
  -Wl,--whole-archive ../src/libipc_s.a  -Wl,--no-whole-archive 
-L../../../../../mozilla/dist/bin -L../../../../../mozilla/dist/lib 
-L../../../../../mozilla/dist/bin -lxpcom -lxpcom_core 
../../../../../mozilla/dist/lib/libxpcomglue_s.a 
-L../../../../../mozilla/dist/bin -lxpcom 
`../../../../../mozilla/nsprpub/config/nspr-config 
--prefix=../../../../../mozilla/dist 
--libdir=../../../../../mozilla/dist/lib --libs`   -Wl,--version-script 
-Wl,/home/mjg/src/mozstuff/comm-central/mozilla/build/unix/gnu-ld-scripts/components-version-script 
-Wl,-Bsymbolic -ldl -lm
/usr/bin/ld: ../src/libipc_s.a(nsPipeTransport.o): relocation 
R_X86_64_32 against `a local symbol' can not be used when making a 
shared object; recompile with -fPIC
../src/libipc_s.a(nsPipeTransport.o): could not read symbols: Bad value
collect2: ld gab 1 als Ende-Status zur?ck
gmake[3]: *** [libipc.so] Fehler 1

From mlisten at hammernoch.net  Mon Jan 26 11:57:27 2009
From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=)
Date: Mon, 26 Jan 2009 20:57:27 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <glkkbd$vdt$1@mozdev.mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>	<mailman.832.1232739784.63231.enigmail@mozdev.org>	<glkahe$3vq$1@mozdev.mozdev.org>	<mailman.840.1232978281.63231.enigmail@mozdev.org>
	<glkkbd$vdt$1@mozdev.mozdev.org>
Message-ID: <497E15A7.30701@hammernoch.net>

Michael J Gruber wrote on 26.01.2009 16:20 Uhr:

>> any. I create nightly builds and they usually work fine.
> 
> Patrick, thanks for taking the time. I can compile TB with the options
> above just nicely. Yet, building Enigmail gives me pain again, see
> below. Specifically, I
> did a  make -f client.mk clean" and rm -Rf'ed the enigmail copy,
> built TB, ran it ,
> copied ${enigmailcvscheckout}/enigmail/src to
> ${comm-central-with-gecko-1.9.1-checkout}/mailnews/extensions/enigmail,
> ran "./makemake -r" in the latter and "make" in
> ${objdir}/mailnews/extensions/enigmail.
> 
> Instructions say cp enigmail/src to mozilla/mailnews/extensions/enigmail
> which doesn't exist. With the current build structure, mailnews
> "contains" (pulls as a module) mozilla-central (or rather 1.9.1), so I
> think what I used is the place to put enigmail. (I've tried
> mozilla/extensions/enigmail before, not better.)

The instructions on http://enigmail.mozdev.org/download/source.php refer
to the Thunderbird 2.x series, they don't apply to TB3.x.

TB3.x directory structure is different. The mailnews directory resides
in parallel to the "mozilla" directory.

"my" mailnews/extensions looks like:

bayesian-spam-filter
smime
dsn
enigmail
mailviews
Makefile.in
mdn
newsblog
offline-startup
palmsync

if that's where you place enigmail, then it's right.

> The error sounds as if ipc is being built shared whereas TB is built
> static (as per .mozconfig). Any more hints?

Sorry, can't help you there. We'll have to wait for Patrick.

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/20090126/445d2cea/attachment.bin>

From patrick at mozilla-enigmail.org  Mon Jan 26 22:51:35 2009
From: patrick at mozilla-enigmail.org (Patrick Brunschwig)
Date: Tue, 27 Jan 2009 07:51:35 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <glkkbd$vdt$1@mozdev.mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>	<mailman.832.1232739784.63231.enigmail@mozdev.org>	<glkahe$3vq$1@mozdev.mozdev.org>	<mailman.840.1232978281.63231.enigmail@mozdev.org>
	<glkkbd$vdt$1@mozdev.mozdev.org>
Message-ID: <497EAEF7.7050507@mozilla-enigmail.org>

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

Michael J Gruber wrote:
> Patrick Brunschwig venit, vidit, dixit 26.01.2009 14:56:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Michael J Gruber wrote:
>>> Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
>>>> Hi,
>>>>
>>>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>>>> Hi there,
>>>>>
>>>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>>>> can't used binary Enigmail xpi either).
>>>>>
>>>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>>>
>>>>> For building Enigmail (from cvs),
>>>> Are you using enigmail trunk (aka 0.96a)?
>>> Yes, that's what I meant by cvs, sorry. A current cvs checkout from
>>> trunk.
>>>
>>>>> I've been following the instructions
>>>>> on the Enigmail website and ended up with the attached error which
>>>>> seems
>>>>> to be related to a conflict in build options (shared/static).
>>>>>
>>>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>>>> because d.m.o. says TB can't be built shared with libxul (and also
>>>>> because I wanted to "make package"). Is this still true? How
>>>>> (static/shared/libxul) do you build TB when you build Enigmail for
>>>>> TB 3
>>>>> nightlies?
>>>> Sorry, I don't know anything about the building process on linux. In
>>>> order to build the Mac OS X nightlies, I'm using these options for
>>>> TB trunk:
>>>>
>>>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>>>> ac_add_options --disable-tests
>>>> ac_add_options --disable-debug
>>>> ac_add_options --enable-crypto
>>>> ac_add_options --enable-optimize
>>>> ac_add_options --enable-static-mail
>>>> ac_add_options --enable-application=mail
>>>> mk_add_options MOZ_CO_PROJECT=mail
>>>> mk_add_options AUTOCONF=autoconf213
>>>>
>>>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
>>> I tried those options (they're the ones from enigmail.mozdev.org) minus
>>> the autoconf. I can build and run TB comm-central successfully with
>>> these options as well as others.
>>>
>>> My problem is building enigmail, which is why I think I'd better post
>>> here than on mozilla.dev.builds. So, my questions really are:
>>>
>>> - Which options do you use when you build enigmail.xpi? (probably the
>>> ones above)
>>
>> Here are my options:
>>
>> mk_add_options MOZ_CO_PROJECT=mail
>> mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/enigdev
>> mk_add_options AUTOCONF=autoconf2.13
>>
>> ac_add_options --enable-application=mail
>> ac_add_options --enable-optimize
>> ac_add_options --disable-debug
>> ac_add_options --disable-tests
>> ac_add_options --enable-codesighs
>> ac_add_options --disable-shared
>> ac_add_options --enable-static
>> ac_add_options --disable-update-packaging
>> ac_add_options --disable-debug
>> ac_add_options --disable-tests
>> ac_add_options --enable-codesighs
>> ac_add_options --disable-shared
>> ac_add_options --enable-static
>> ac_add_options --disable-crashreporter
>>
>>> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
>>> known to build and run well together?
>>
>> any. I create nightly builds and they usually work fine.
> 
> Patrick, thanks for taking the time. I can compile TB with the options
> above just nicely. Yet, building Enigmail gives me pain again, see
> below. Specifically, I
> did a  make -f client.mk clean" and rm -Rf'ed the enigmail copy,
> built TB, ran it ,
> copied ${enigmailcvscheckout}/enigmail/src to
> ${comm-central-with-gecko-1.9.1-checkout}/mailnews/extensions/enigmail,
> ran "./makemake -r" in the latter and "make" in
> ${objdir}/mailnews/extensions/enigmail.
> 
> Instructions say cp enigmail/src to mozilla/mailnews/extensions/enigmail
> which doesn't exist. With the current build structure, mailnews
> "contains" (pulls as a module) mozilla-central (or rather 1.9.1), so I
> think what I used is the place to put enigmail. (I've tried
> mozilla/extensions/enigmail before, not better.)
> 
> The error sounds as if ipc is being built shared whereas TB is built
> static (as per .mozconfig). Any more hints? makemake does pick up objdir
> so it sees the .mozconfig.
> 
> This is on 64bit Fedora 10, by the way, gcc/g++ is gcc version 4.3.2
> 20081105 (Red Hat 4.3.2-7) (GCC).
> 
> Thanks for your patience...
> Michael

I'm not sure if you will succeed with GCC 4.3.2. I'd suggest you check
<https://www.mozdev.org/bugs/show_bug.cgi?id=20282> and the referenced
Gentoo bug.

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

iQEVAwUBSX6u9ncOpHodsOiwAQgGNggAiztobuT7SEZ1swaW/vNbBA6xPEdMy7uF
keeT/JHCGiMe0Ng27ovPkVIi82FouO4+tzsydmAmzsE0Za7nQ/jG/puxHKh1drTL
ttR+JBhAyH7RC4xNxoaqgT5jFEhf1e9xqi47aeyhWHNR1SQU6XqDwcwn+C3aYNRS
HmaqG+FDw/D1NqWsxVjfqgjrdLvxIQfngZjnxh76B+Okz5raDxDct+QnlZBFQCt2
F94nKigust4Tp1eX1TOEHM8zp2s+Oc5rJCvoNxXyMD1mWWt+LynsZ37L08gOmUIk
1hHVEkHhuL5sB7Au0sL0Vt2oLHwEYLLV9kOPsgDr6YmdVnxPDsy8KQ==
=KMMm
-----END PGP SIGNATURE-----

From michaeljgruber at fastmail.fm  Tue Jan 27 04:45:14 2009
From: michaeljgruber at fastmail.fm (Michael J Gruber)
Date: Tue, 27 Jan 2009 13:45:14 +0100
Subject: [Enigmail] Building Enigmail for TB comm-central: static or
 shared, libxul or not?
In-Reply-To: <mailman.842.1233039118.63231.enigmail@mozdev.org>
References: <glcepl$1eoa$1@mozdev.mozdev.org>	<mailman.832.1232739784.63231.enigmail@mozdev.org>	<glkahe$3vq$1@mozdev.mozdev.org>	<mailman.840.1232978281.63231.enigmail@mozdev.org>	<glkkbd$vdt$1@mozdev.mozdev.org>
	<mailman.842.1233039118.63231.enigmail@mozdev.org>
Message-ID: <glmvks$1o6d$1@mozdev.mozdev.org>

Patrick Brunschwig venit, vidit, dixit 01/27/09 07:51:
> Michael J Gruber wrote:
>> Patrick Brunschwig venit, vidit, dixit 26.01.2009 14:56:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>> Michael J Gruber wrote:
>>>> Ludwig H?gelsch?fer venit, vidit, dixit 01/23/09 20:42:
>>>>> Hi,
>>>>>
>>>>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>>>>> Hi there,
>>>>>>
>>>>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>>>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>>>>> can't used binary Enigmail xpi either).
>>>>>>
>>>>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>>>>
>>>>>> For building Enigmail (from cvs),
>>>>> Are you using enigmail trunk (aka 0.96a)?
>>>> Yes, that's what I meant by cvs, sorry. A current cvs checkout from
>>>> trunk.
>>>>
>>>>>> I've been following the instructions
>>>>>> on the Enigmail website and ended up with the attached error which
>>>>>> seems
>>>>>> to be related to a conflict in build options (shared/static).
>>>>>>
>>>>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>>>>> because d.m.o. says TB can't be built shared with libxul (and also
>>>>>> because I wanted to "make package"). Is this still true? How
>>>>>> (static/shared/libxul) do you build TB when you build Enigmail for
>>>>>> TB 3
>>>>>> nightlies?
>>>>> Sorry, I don't know anything about the building process on linux. In
>>>>> order to build the Mac OS X nightlies, I'm using these options for
>>>>> TB trunk:
>>>>>
>>>>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>>>>> ac_add_options --disable-tests
>>>>> ac_add_options --disable-debug
>>>>> ac_add_options --enable-crypto
>>>>> ac_add_options --enable-optimize
>>>>> ac_add_options --enable-static-mail
>>>>> ac_add_options --enable-application=mail
>>>>> mk_add_options MOZ_CO_PROJECT=mail
>>>>> mk_add_options AUTOCONF=autoconf213
>>>>>
>>>>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
>>>> I tried those options (they're the ones from enigmail.mozdev.org) minus
>>>> the autoconf. I can build and run TB comm-central successfully with
>>>> these options as well as others.
>>>>
>>>> My problem is building enigmail, which is why I think I'd better post
>>>> here than on mozilla.dev.builds. So, my questions really are:
>>>>
>>>> - Which options do you use when you build enigmail.xpi? (probably the
>>>> ones above)
>>> Here are my options:
>>>
>>> mk_add_options MOZ_CO_PROJECT=mail
>>> mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/enigdev
>>> mk_add_options AUTOCONF=autoconf2.13
>>>
>>> ac_add_options --enable-application=mail
>>> ac_add_options --enable-optimize
>>> ac_add_options --disable-debug
>>> ac_add_options --disable-tests
>>> ac_add_options --enable-codesighs
>>> ac_add_options --disable-shared
>>> ac_add_options --enable-static
>>> ac_add_options --disable-update-packaging
>>> ac_add_options --disable-debug
>>> ac_add_options --disable-tests
>>> ac_add_options --enable-codesighs
>>> ac_add_options --disable-shared
>>> ac_add_options --enable-static
>>> ac_add_options --disable-crashreporter
>>>
>>>> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
>>>> known to build and run well together?
>>> any. I create nightly builds and they usually work fine.
>> Patrick, thanks for taking the time. I can compile TB with the options
>> above just nicely. Yet, building Enigmail gives me pain again, see
>> below. Specifically, I
>> did a  make -f client.mk clean" and rm -Rf'ed the enigmail copy,
>> built TB, ran it ,
>> copied ${enigmailcvscheckout}/enigmail/src to
>> ${comm-central-with-gecko-1.9.1-checkout}/mailnews/extensions/enigmail,
>> ran "./makemake -r" in the latter and "make" in
>> ${objdir}/mailnews/extensions/enigmail.
> 
>> Instructions say cp enigmail/src to mozilla/mailnews/extensions/enigmail
>> which doesn't exist. With the current build structure, mailnews
>> "contains" (pulls as a module) mozilla-central (or rather 1.9.1), so I
>> think what I used is the place to put enigmail. (I've tried
>> mozilla/extensions/enigmail before, not better.)
> 
>> The error sounds as if ipc is being built shared whereas TB is built
>> static (as per .mozconfig). Any more hints? makemake does pick up objdir
>> so it sees the .mozconfig.
> 
>> This is on 64bit Fedora 10, by the way, gcc/g++ is gcc version 4.3.2
>> 20081105 (Red Hat 4.3.2-7) (GCC).
> 
>> Thanks for your patience...
>> Michael
> 
> I'm not sure if you will succeed with GCC 4.3.2. I'd suggest you check
> <https://www.mozdev.org/bugs/show_bug.cgi?id=20282> and the referenced
> Gentoo bug.

Thanks for the hint, although they seem to be able to compile enigmail
release version with TB 2.0.0.*. They get crashes during runtime which
are most probably due to the typical Gentoo attitude: building with
-Oas-much-as-possible-though-I-have-no-clue ;) Seriously, they use -O2
which d.m.o. specifically warns against, and -O1 solves their problem.

I have a build problem (with cvs trunk/comm-central-trunk/gecko-1.9.1),
specifically a linker problem which I have no clue about... I'll try a
bit more, or else resort to TB 2.0.0.19 with Remi's Enigmail build. In
fact, his SRPMs should give me some hints...

Michael

From hmeyer at gmx.eu  Thu Jan 29 03:15:00 2009
From: hmeyer at gmx.eu (Henning Meyer)
Date: Thu, 29 Jan 2009 12:15:00 +0100
Subject: [Enigmail] S/MIME and Enigmail
Message-ID: <gls33l$1h4k$1@mozdev.mozdev.org>

Hi all,

maybe an old topic. But anyway. Because some of my contacts use GPG and
some use S/MIME, I'm working with GPG/Enigmail and S/MIME. While in
Enigmail I can setup rules for Contacts, I cannot find a setting for
S/MIME. But I'd like to have a setting which encrypts and signs all
mails for the GPG-Contacts via Enigmail and signs all other mail via S/MIME.
This is not possible for me. Thunderbird want's to sign all mail with
S/MIME, which has to be turned off manually for each GPG-Contact-Mail,
because elsewise the mail won't be signed nor encrypted with GPG.

Any hints?

Henning

From jeandavid8 at verizon.net  Thu Jan 29 04:15:55 2009
From: jeandavid8 at verizon.net (Jean-David Beyer)
Date: Thu, 29 Jan 2009 07:15:55 -0500
Subject: [Enigmail] S/MIME and Enigmail
In-Reply-To: <gls33l$1h4k$1@mozdev.mozdev.org>
References: <gls33l$1h4k$1@mozdev.mozdev.org>
Message-ID: <49819DFB.8050605@verizon.net>

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

Henning Meyer wrote:
| Hi all,
|
| maybe an old topic. But anyway. Because some of my contacts use GPG and
| some use S/MIME, I'm working with GPG/Enigmail and S/MIME. While in
| Enigmail I can setup rules for Contacts, I cannot find a setting for
| S/MIME. But I'd like to have a setting which encrypts and signs all mails
| for the GPG-Contacts via Enigmail and signs all other mail via S/MIME.
| This is not possible for me. Thunderbird want's to sign all mail with
| S/MIME, which has to be turned off manually for each GPG-Contact-Mail,
| because elsewise the mail won't be signed nor encrypted with GPG.
|
| Any hints?
|
If you are in a _compose_ window in Thunderbird and you click (at the top of
the window) on OpenPGP you will get a drop-down menu that has, among other
things, a checkbox that says: "Use PGP/MIME for This Message". I do not
remember what the default is, but all you have to do is uncheck that box and
it will be signed like this one.

Of course this is the default setting and applies to all your e-mails unless
you hit the lower OpenPGP (Icon in my case) and change it for the individual
e-mail. I know of no _automatic_ way to get it to sign one way for some
people and another way for others.

But consider this: Imagine sending a signed e-mail to a mailing list like
this one. Some of the people want in signed inline, some want it signed
PGP/MIME, and some do not want it signed at all. You cannot do that
automatically in any case, since, assuming preferences evenly distributed,
you will offend at least 50% of the recipients (the 1/4 who do not care at
all being 25% of the assumed population).

- --
~  .~.  Jean-David Beyer          Registered Linux User 85642.
~  /V\  PGP-Key: 9A2FC99A         Registered Machine   241939.
~ /( )\ Shrewsbury, New Jersey    http://counter.li.org
~ ^^-^^ 07:05:01 up 7 days, 22:56, 3 users, load average: 4.39, 4.32, 4.20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD4DBQFJgZ37Ptu2XpovyZoRArsxAJYmj6gqO5hMKpKSOHx4X7IS4NUcAJkBIvj1
YrhcXBEQ5l5M4ajFyi3E1A==
=Jk/N
-----END PGP SIGNATURE-----

From alaric at metrocast.net  Thu Jan 29 04:52:40 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Thu, 29 Jan 2009 07:52:40 -0500
Subject: [Enigmail] S/MIME and Enigmail
In-Reply-To: <49819DFB.8050605@verizon.net>
References: <gls33l$1h4k$1@mozdev.mozdev.org> <49819DFB.8050605@verizon.net>
Message-ID: <4981A698.5040503@metrocast.net>

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

Jean-David Beyer wrote:
> But consider this: Imagine sending a signed e-mail to a mailing list like
> this one. Some of the people want in signed inline, some want it signed
> PGP/MIME, and some do not want it signed at all. You cannot do that
> automatically in any case, since, assuming preferences evenly distributed,
> you will offend at least 50% of the recipients (the 1/4 who do not care at
> all being 25% of the assumed population).

"The wonderful thing about standards is that there are so many to choose
from."  (Anon)


- --
  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

iEYEAREIAAYFAkmBppgACgkQ0DfOju+hMknCcwCcDve8hMusRNexMU/WWcg2AC20
cRMAn0RdGWRooKhAvbd3L4SnY9N6Ejly
=4/Mm
-----END PGP SIGNATURE-----

From steffenjan at web.de  Thu Jan 29 12:59:38 2009
From: steffenjan at web.de (Jan Steffen)
Date: Thu, 29 Jan 2009 21:59:38 +0100
Subject: [Enigmail] S/MIME and Enigmail
In-Reply-To: <gls33l$1h4k$1@mozdev.mozdev.org>
References: <gls33l$1h4k$1@mozdev.mozdev.org>
Message-ID: <glt5bb$1rvf$1@mozdev.mozdev.org>

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

Henning Meyer schrieb:
> maybe an old topic. But anyway. Because some of my contacts use GPG and
> some use S/MIME, I'm working with GPG/Enigmail and S/MIME. While in
> Enigmail I can setup rules for Contacts, I cannot find a setting for
> S/MIME. But I'd like to have a setting which encrypts and signs all
> mails for the GPG-Contacts via Enigmail and signs all other mail via S/MIME.
> This is not possible for me. Thunderbird want's to sign all mail with
> S/MIME, which has to be turned off manually for each GPG-Contact-Mail,
> because elsewise the mail won't be signed nor encrypted with GPG.

You mean something like enigmails per-recipient-rules but including the option
to sign with S/MIME instead of OpenPGP?
I'd love to have this too.

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

iEYEAREIAAYFAkmCGLkACgkQSa1Uad4+pFfyzgCePeDU4iDP6TzIsoppM6lSjFe9
CScAn2sWNqrGYdeEdWJjr+/9kBLi+yev
=SRqW
-----END PGP SIGNATURE-----

From fswat at yahoo.com  Thu Jan 29 17:32:49 2009
From: fswat at yahoo.com (Frank Swatland)
Date: Thu, 29 Jan 2009 20:32:49 -0500
Subject: [Enigmail] Initial Setup
Message-ID: <498258C1.1090406@yahoo.com>

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

Hi Enigmail,

First Thank you

I just set up an Enigmal Account in Thunderbird 2.0 and uploaded my
public key.

What I don't understand is how do I send my Public Code to another user?
Do they have to have a Thunderbird Application? So if I send an
encrypted email to fswat at yahoo.com how does that person get my Public
Code and what does he or she have to have or what will he/she have to do
to un-encrypt my email?

Your help will be appreciated.

Again, Thank you

Frank Swatland

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

iEYEARECAAYFAkmCWL4ACgkQ5s3OZKgFWkUeXgCgvlBaRIfP1hPOFuoq7fc6J6mj
kggAoJ266axzsVV6y0ooq10xsgc4MpYN
=jVkK
-----END PGP SIGNATURE-----


From nospam001-lists at jankoh.dyndns.org  Thu Jan 29 17:56:06 2009
From: nospam001-lists at jankoh.dyndns.org (Jan Kohnert)
Date: Fri, 30 Jan 2009 02:56:06 +0100
Subject: [Enigmail] Initial Setup
In-Reply-To: <498258C1.1090406@yahoo.com>
References: <498258C1.1090406@yahoo.com>
Message-ID: <200901300256.16534.nospam001-lists@jankoh.dyndns.org>

Frank Swatland schrieb:
> I just set up an Enigmal Account in Thunderbird 2.0 and uploaded my
> public key.

Wellcome! Your message verified well here, so it seems all went fine. 

> What I don't understand is how do I send my Public Code to another user?

This was already done by uploading your public key to a keyserver. No 
interaction needed anymore.

> Do they have to have a Thunderbird Application? So if I send an
> encrypted email to fswat at yahoo.com how does that person get my Public
> Code and what does he or she have to have or what will he/she have to do
> to un-encrypt my email?

Well, signing and encrypting works a bit different: You sign with your private 
key and verification is done with your public key which is available. 
Encrypting is done with your recipients public key (and most probably also 
your own, if you want to be able to read you sent mail again) and decrypting 
is done with the private key, so one is only able to decrypt mail if the 
recipients private key is available. As long as the private keys are save 
(which we all hope), only the recipient (and you, if you encrypted with your 
key, too) can read the message.

However, it is not mandatory to use Thunderbird, most (at least nearly(?) all 
open source) mail user agents (MUAs) are able to use GnuPG naturally or with 
a plugin like enigmail to be able to verify or decrypt messages.

Feel free to send me an encrypted test message off list to see if it works. 
And keep your private key save. ;)

-- 
MfG Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090130/e0fa70b8/attachment.bin>

From rjh at sixdemonbag.org  Thu Jan 29 18:30:15 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 29 Jan 2009 21:30:15 -0500
Subject: [Enigmail] Initial Setup
In-Reply-To: <498258C1.1090406@yahoo.com>
References: <498258C1.1090406@yahoo.com>
Message-ID: <49826637.6050903@sixdemonbag.org>

Jan's already given you a pretty good answer.  My only objection to it
is that it's too long.  :)  I'll be giving you the same answers in a
much shorter form.

Frank Swatland wrote:
> First Thank you

You're very welcome.  :)

> What I don't understand is how do I send my Public Code to another
> user?

When someone needs your public key, they'll just pull it down from the
keyserver network.

> Do they have to have a Thunderbird Application?

They need to have an email program that can handle OpenPGP.  There are
many out there.

> So if I send an encrypted email to fswat at yahoo.com how does that
> person get my Public Code and what does he or she have to have or
> what will he/she have to do to un-encrypt my email?

Imagine that you're given directions to someone's house.  The person
giving you the directions says, "now, this person lives in the middle of
nowhere, and it'll be dark when you arrive, so you probably won't be
able to find his house unless he's got his porch light on for you."

You might then ask, "How can I be sure he's ready for visitors?"

You might get reminded, "He'll have his porch light on for you.  That
means it's a pretty good guess he's ready for you to stop by."

In a similar vein, you must have your recipient's public key before you
can send them an encrypted email.  If your recipient has a public key,
the odds are very good your recipient already has GnuPG installed and
knows how to use it.  After all -- if they didn't, how could they have
generated their key?  :)


From fswat at yahoo.com  Thu Jan 29 19:11:50 2009
From: fswat at yahoo.com (Frank Swatland)
Date: Thu, 29 Jan 2009 22:11:50 -0500
Subject: [Enigmail] Thank you Jan & Robert for your help
Message-ID: <49826FF6.7040103@yahoo.com>

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

Hi Jan, Hi Robert.

The process is now clear. Do you know if Yahoo.com and Charter .net
support OpenPgP. After writing the question I think I can go there and
find out the answers.

Again thank you both for your help.

I don't use Forums much so I did not understand if I should write to you
directly or respond this way through the Forum.

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

iEYEARECAAYFAkmCb/MACgkQ5s3OZKgFWkWCTACcD567aCQg2E0jW04owItKouPl
WmEAoLUEam3nikw6UkbTqJUrSYH/YKrq
=YnOh
-----END PGP SIGNATURE-----


From rjh at sixdemonbag.org  Thu Jan 29 20:04:40 2009
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 29 Jan 2009 23:04:40 -0500
Subject: [Enigmail] Thank you Jan & Robert for your help
In-Reply-To: <49826FF6.7040103@yahoo.com>
References: <49826FF6.7040103@yahoo.com>
Message-ID: <49827C58.8050409@sixdemonbag.org>

Frank Swatland wrote:
> The process is now clear. Do you know if Yahoo.com and Charter .net
> support OpenPgP. After writing the question I think I can go there and
> find out the answers.

Webmail is often dicey.  Some people have had good luck using FireGPG
with webmail; other people don't.  There are also some security concerns
with webmail which are not present when you're using a regular,
conventional email program.

With respect to regular email that you get through Thunderbird -- yes,
OpenPGP works with any service provider.

> I don't use Forums much so I did not understand if I should write to you
> directly or respond this way through the Forum.

The mailing list is the best way.  If someone has the same questions as
you, they can Google it and find this thread.  If you send it via
private mail, though, there's no Google record made.


From maximilien at theglu.org  Fri Jan 30 01:11:40 2009
From: maximilien at theglu.org (Maximilien Cuony [The_Glu])
Date: Fri, 30 Jan 2009 10:11:40 +0100
Subject: [Enigmail] Thank you Jan & Robert for your help
In-Reply-To: <49827C58.8050409@sixdemonbag.org>
References: <49826FF6.7040103@yahoo.com> <49827C58.8050409@sixdemonbag.org>
Message-ID: <2c5cab5d4042d0da37f1784321532309@127.0.0.1>


Btw I'm planning to add Yahoo support in FireGPG ;)

But as Frank Swatland said, if the web mail want, he can read your
unencrypted mail. But it's should be voluntary (add function to capture
unencrypted mails) (and if it's become public they may have problems ;))-

Regards,

On Thu, 29 Jan 2009 23:04:40 -0500, "Robert J. Hansen"
<rjh at sixdemonbag.org>
wrote:
> Frank Swatland wrote:
>> The process is now clear. Do you know if Yahoo.com and Charter .net
>> support OpenPgP. After writing the question I think I can go there and
>> find out the answers.
> 
> Webmail is often dicey.  Some people have had good luck using FireGPG
> with webmail; other people don't.  There are also some security concerns
> with webmail which are not present when you're using a regular,
> conventional email program.
> 
> With respect to regular email that you get through Thunderbird -- yes,
> OpenPGP works with any service provider.
> 
>> I don't use Forums much so I did not understand if I should write to you
>> directly or respond this way through the Forum.
> 
> The mailing list is the best way.  If someone has the same questions as
> you, they can Google it and find this thread.  If you send it via
> private mail, though, there's no Google record made.
> 
> _______________________________________________
> Enigmail mailing list
> Enigmail at mozdev.org
> https://www.mozdev.org/mailman/listinfo/enigmail

-- 
Maximilien Cuony [The_Glu]
http://theglu.org