gmane.comp.mozilla.enigmail.general

Re: gpg agent issue with enigmail / tbird 12

Faramir — 2012-05-23T01:06:16

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

El 22-05-2012 17:14, Patrick Spinler escribió:

  I'd call it layer 8 error, it sounds better. Or maybe an error in
the chair-keyboard interface.

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

iQEcBAEBCAAGBQJPvDgIAAoJEMV4f6PvczxAwpkH+wfJyxEPqXTNn4pOhtyrr6J+
CKAFL+h6oWxySloeJ9iTpeM0QmbtfSpISzfGJasG9GLU49jawTfWTlszFXaMbIl3
gK5s0IXrvOCcHucx7ixcNCP0spdaIr1rHpBccor3jILYJmPDtOmgPGvCHZXcRJ9A
svT2M4SppinuHw1UCSmURerie/1SWCYprzOoxBQMvMVwXWBUHcRsfnJT/GB01jTs
WZaczL2uRVC2jtdYQ1YnKen0sbswG1F7RFOjjqbLlUxJUmCKhctZ6pPC3X5hmgai
MQ1zrapuQtGyf+SqMh/vOTSZjZbiFp8r8P1FEAnNS2YsbM1RzQD3j10GiA9ccCo=
=HE6O
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail< at >mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: gpg agent issue with enigmail / tbird 12

Patrick Spinler — 2012-05-22T21:14:04

Thanks to Charly and Robert.  And my apologies for spamming the list
after figuring out this was a gpg usage error (idiot on keyboard error)
instead of an enigmail issue.

Signing OUT for a few hours.

Charly Avital — 2012-05-22T20:53:36

Hi list,

I'm OUT for a few hours, and apologize for not being able to answer or
react till later on.
Charly

Re: gpg agent issue with enigmail / tbird 12

Charly Avital — 2012-05-22T20:38:09

If you are encrypting a test message to yourself, then you are using
your public key, not your secret key.


There's some confusion here, please see above remark.
[snip]


I checked the above encrypted message:
"gpg: encrypted with ELG key, ID EA927CD8", that's your friend's public
key. Only he can decrypt that message.



That's correct, your friend's secret key is not available to you, only
to him.

Please check the settings in OpenPGP/Edit Per-Recipient Rules.
Also in Tools/Account Settings

Charly

Re: gpg agent issue with enigmail / tbird 12

Robert J. Hansen — 2012-05-22T20:33:24

Then why are you asking on the Enigmail list?  :)

You will have better luck asking on GnuPG-Users.


So, your secret keyring contains one certificate, id 0x0F2E06CC.  As
part of that certificate there's an encryption key, id 0x3673D7D5.


But this message was encrypted for certificate 0xEA927CD8, using
encryption key 0x2253045B.

This is not the same certificate that you have on your secret keyring.
Ask your correspondent to use the correct certificate -- 0x0F2E06CC.

GnuPG is working exactly as intended.  Your correspondent is using the
wrong certificate.  That's all.

Re: gpg agent issue with enigmail / tbird 12

Charly Avital — 2012-05-22T20:17:44

That key is fine:
pub  1024D/0F2E06CC created: 2000-10-20  expires: never   usage: SCA
                     trust:        validity:
sub  2048g/3673D7D5  created: 2000-10-20  expires: never   usage: E
(1). Patrick Spinler <spinler.patrick< at >mayo.edu>


That would point at the possibility that you have installed gpg2 using
MacPorts.
And that might the cause of your problem.


I am afraid that MacPorts is still installing a version of pinentry that
does not work under MacOSX.



You could try to use the following MacGPG2 binary installer written by
Benjamin Donnachie:
<http://cl.ly/3H0X0S1T3U3H0B3K370C> that should download
MacGPG2-2.0.17-9.zip  that you can verify with
md5:    36dec9b2b7f24234a2286d736397d8e9

It will install a native Mac pinentry.

A bit of an overkill, but:
- quit all running applications.
- run the installer
- *restart* your computer
- Launch Terminal and try:
gpg2 --version
then
gpg-agent

In TB, OpenPGP Preferences, you should set the path to the executable:
/usr/local/MacGPG2/bin/gpg2

It's up to you.
Charly
Mac OS X 10.7.4 (11E52) MacBook Intel C2Duo 2GHz
MacGPG2-2.0.17-9
Thunderbird 12.0.1 Enigmail 1.5a1pre (20120521-2224)

Re: gpg agent issue with enigmail / tbird 12

Patrick Spinler — 2012-05-22T20:06:20

Identical results for me on Ubuntu 12.04 using gpg:
pjs11< at >patslinux01 ~ $ gpg --version

gpg: NOTE: old default options file `/home/pjs11/.gnupg/options' ignored
gpg (GnuPG) 1.4.11
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2


And on OSX 10.7.3 using gpg version:

pjs11< at >R0225632 ~ $ gpg --version
gpg (GnuPG) 1.4.12
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2


And also on OSX 10.7.3 using gpg2 version:

pjs11< at >R0225632 ~ $ gpg2 --version
gpg (GnuPG) 2.0.18
libgcrypt 1.5.0
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

On 5/22/12 3:01 PM, Patrick Spinler wrote:

Re: gpg agent issue with enigmail / tbird 12

Patrick Spinler — 2012-05-22T20:01:06

This appears to be something broken in my gpg setup.

I can demonstrate the same behavior with gpg2 and gpg.  Here's an
example using gpg.

I can encrypt something using my secret key, and list my secret key, but
not decrypt something sent to me using my secret key.  Some examples:


pjs11< at >R0225632 ~ $ gpg -K
/Users/pjs11/.gnupg/secring.gpg
-------------------------------
sec   1024D/0F2E06CC 2000-10-20
uid                  Patrick Spinler <spinler.patrick< at >mayo.edu>
uid                  Patrick Spinler <pspinler< at >gmail.com>
ssb   2048g/3673D7D5 2000-10-20


==== Example of encrypting using a friends public key ===

pjs11< at >R0225632 ~ $ gpg -e -r jbroome< at >gmail.com -a -s

You need a passphrase to unlock the secret key for
user: "Patrick Spinler <spinler.patrick< at >mayo.edu>"
1024-bit DSA key, ID 0F2E06CC, created 2000-10-20

gpg: EA927CD8: There is no assurance this key belongs to the named user

pub  1024g/EA927CD8 2003-12-07 John Broome <jbroome< at >gmail.com>
 Primary key fingerprint: F732 72ED A7CC FA67 6A00  B2F6 947D 7436 C01B 27B1
      Subkey fingerprint: C69A 98A4 925C 2915 FDD2  4F37 8A8C 00BE EA92 7CD8

It is NOT certain that the key belongs to the person named
in the user ID.  If you *really* know what you are doing,
you may answer the next question with yes.

Use this key anyway? (y/N) y

testing testing test test test foo.

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.12 (Darwin)

hQEOA4qMAL7qknzYEAQAgvUJgQzNaVfOV1THS64E0pUb6BDeitvQg1dC3eZP8PTB
nTFeJMtMfD+nJc1eNmcdFBfteEP6RixAUlVhJUZd+in2zj0XUQtqv1Tgtcbqyebj
+Gbpw1+z2yK5boe5d7XoAjsfsGPalkOQtRffHP48joYEpq5h3xdD2ZwEoVeSyEED
/iinJ9K/fa0daUq9uEr0+zJ3UJOF8uEro5t5HNacDDuup8KCgtwAMXdfbjM9qVnI
kl7ipHrt7OveV0LFtDw9AKZyaaCqiehPZJb+8uMAPVj6fAzM8v7pzXt44JdAbu+y
4W9WMzPWHIwBIJV55QQLhm2sKtUfKDde98fd4eaNWE1k0p8BkGtNAVOjfRSP5uSF
yIIi93rbbc5Yff1qyLKWGA/d850A5hiI2rIuEVf9pn0zVvWaR5mq1t65o/M//uPx
I4Y1NTtDxN6eXsMOIcHhIchkyeVgAGVSVC8OMwyICgzkGMP1DdPSREGU9I2PxnWR
2RUfX8LnGLAbidIPhEJYSHIGN3AsCDrJdAZqemL2Ihihl0rL7kFb7xC6nay+kRd1
H4Y=
=en+i
-----END PGP MESSAGE-----



=== Trying to decrypt a message from this same friend ===


pjs11< at >R0225632 ~ $ gpg -d
-----BEGIN PGP MESSAGE-----
Charset: ISO-8859-1
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

hQIOA2yYh1giUwRbEAf/X4det1WEG6RL23E1qtMyCJEh3ZsRaoDwNhK+dT0/RLEj
Li+vkw2SdT32GYf2Ucnn8Zm8qgeXL39gHALkn5z/sruBvQJbc+5Yb3CD+TkNc1dU
nnJ73VaTyXmMsAhA482d36TavhSEIHZktqYer/8WXOZRzr+iVSvoynNgapBQiMpW
7WQPiavsYt4Nh5YVYpJl9xKdHbW2aFksnlpStK2OIFcBwTTG/PfioI50oBVjfGnt
Jf3qlmVYy3sn1hShTgnPg5Ax4Qn/5FbNstBTJXd2eJQjST8z4ekRfOmSxe10XkSg
fXMmdjqsaNkjdED8iULePQQq90vFH+w0VaOG7bl+Ywf+KtWRiXRHqeGSo496Uwas
ZIqMZMdspZjFz47d5DclbuCln1emhvth8tds3sNmZ7p4bTTp6vjYDhJmZCFg/cAN
1Os/IHBMelt15e40+5ALIPrrJQtaklqyDNcumpAQtau9Iu22CsdLA8IWwZH3cJqV
N0vWrRmDspkzhTHL/xzrllhzN9P4fpSaByzCuHAWH3V7rTKg5/27nW6dCxuTsGCJ
AUCSnH1RLDG4ii+4Jvnp8SQStP0YmzsRKADsLdWf0hPdBiev7Q+91q/+FsIeC4KK
okfgbBBkLh3XpNJmO33H8ZutHH5Ar0O5V154QIE8TEgHA9sv5oCT1C4o716MPbqO
Q4UBDgOKjAC+6pJ82BAD/1X46I47lKiwFNN+8hZsqcj5gWZmtCjAoU7/TaJ70apt
CgRs08dnQ9EiqMz0h3ily5eIF7liX2VDz8lNrXGy7xXm/YUszdVk+uGhvhVVg2NZ
Sl+ZIH1dqI0qoYjmpn5KMwXNQALQQjuVMP2IYhTBlEegsY9aDcWY0lioX13mW7aS
BACFaTwAR5JP13yuA+bJIw8ZcVBiFTtcZ4sd4xx5aFvFBF8GXyoLjgPfathdg8zH
kMawBadABs4C4MC9ohW+nATvSp5QX+t6VztYV5yfpElmP8uSdnb1KuD4mxoUQy7D
P5rWwjTs86/NXdgqJzmugehIlr8UR7A59oPuqOkAay6VDcl6nfzyzAUPj+wee1ci
e5LOupEh7Tvq7yQZ0azZvpUtXaEHnj0ib2yjFGwcql9LDg4v06CsOl0AOV4g553d
z3rAk2zwSMxkuC0IS6s2w6SIXwZMnIeQ0xZPxAcX8sTFMd0xIbaq93L4aGve3MFE
8EopyfHQ76LGM+NZbfU=
=UMeW
-----END PGP MESSAGE-----

gpg: encrypted with 1024-bit ELG-E key, ID EA927CD8, created 2003-12-07
      "John Broome <jbroome< at >gmail.com>"
gpg: encrypted with ELG-E key, ID 2253045B
gpg: decryption failed: secret key not available



Thoughts, please?  What have I done wrong?

gpg agent issue with enigmail / tbird 12

Patrick Spinler — 2012-05-22T19:27:51

When attempting to encrypt and/or sign a message, I get:


Key 0x0F2E06CC not found or not valid. The (sub-)key might have expired.

gpg command line and output:
/opt/local/bin/gpg2
Error opening terminal: unknown.
gpg-agent[81149]: command get_passphrase failed: End of file
gpg: problem with the agent: End of file
gpg: skipped "0x0F2E06CC": Operation cancelled
gpg: [stdin]: sign+encrypt failed: Operation cancelled


I can, however, manually encrypt and/or sign stuff using the gpg2
command line.

This seems to happen regardless of whether or not I have a gpg-agent
running.

Suggestions, please?

Re: Bugs

Robert J. Hansen — 2012-05-20T00:27:03

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

On 5/19/12 8:17 PM, Papo wrote:

<List moderator hat on>

Let's not be mean.

David is making some very broad and sweeping claims about GnuPG 2 and
Enigmail.  It's okay to challenge him on those claims.  It's even okay
to challenge him vigorously on those claims.  You can beat up an idea,
a proposition, a notion, all that you want.  As soon as you start
beating up on *people*, though, then the list mods break out our
moderator hats.

Let's not be mean.

</List moderator hat>

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iFYEAREIAAYFAk+4OlcACgkQI4Br5da5jhBUygDgguApnoR19qYsVyjS3UDECFwA
idvJIwSrXjMFIQDfXSwWrQpBFRxS3gWGT0AiFhBVfAxDt1N1FrraUw==
=JFaR
-----END PGP SIGNATURE-----

Re: Bugs

Papo — 2012-05-20T00:17:18

<david< at >gbenet.com> wrote in message 
news:mailman.321.1337384433.99783.enigmail< at >mozdev.org...
[snip]
Eh, Mr. David, as indicated by your apparent challenge in correctly 
structuring a simple thread, which most of us can manage without much 
difficulty, it does not take a great deal of imagination to suppose that the 
Enigmail program has proven likewise to be a wee bit more than you can 
muster at this point, don't you think? Now, unless you are ready to admit at 
least that much is true, then I would have to say you are trolling.

Re: Bugs

Robert J. Hansen — 2012-05-19T19:30:56

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

On 05/19/2012 05:47 AM, david< at >gbenet.com wrote:

1.  This is news to thousands of people successfully using Enigmail with
GnuPG-2.x on Linux.

2.  This seems to be a complaint about GnuPG-2.x.  Please take that to
the GnuPG-Users mailing list.  We have no control over GnuPG.


This is not only not true, but 100% whaledreck.


Please take this talk to GnuPG-Users.

(Signed with GnuPG 2.0.17 on Ubuntu 12.04LTS with Enigmail)
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iFYEAREIAAYFAk+39O8ACgkQI4Br5da5jhDmvQDePPRWMFRp+teUJkpT13MXhZro
x1F1rk3vB+3JiQDeI//JI8ZlnFqkF6IquCI1gQT47Wu8oxtKYxGxaQ==
=iB4b
-----END PGP SIGNATURE-----

Re: Bugs

Mike Cardwell — 2012-05-19T12:06:52

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

On 19/05/12 12:34, david< at >gbenet.com wrote:


Everything you've said above is flat out wrong. GnuPG v2 works
*perfectly* under *all* versions of GNU/Linux. You're the only person
that I've seen having these problems. It works absolutely fine with
Thunderbird 12.1 and Enigmail under all GNU/Linux distributions and
all other major operating systems. If it's not working for you, you're
clearly doing something wrong. Do you really think that everyone else
is having these problems and has just kept quiet about it?

- -- 
Mike Cardwell  https://grepular.com/     http://cardwellit.com/
OpenPGP Key    35BC AF1D 3AA2 1F84 3DC3  B0CF 70A5 F512 0018 461F
XMPP OTR Key   8924 B06A 7917 AAF3 DBB1  BF1B 295C 3C78 3EF1 46B4
-----BEGIN PGP SIGNATURE-----

iQGGBAEBAgBwBQJPt4zcMBSAAAAAACAAB3ByZWZlcnJlZC1lbWFpbC1lbmNvZGlu
Z0BwZ3AuY29tcGdwbWltZTgUgAAAAAAVABpwa2EtYWRkcmVzc0BnbnVwZy5vcmdt
aWtlLmNhcmR3ZWxsQGdyZXB1bGFyLmNvbQAKCRCdJiMBwdHnBAUIB/wPV/0pjCH4
ra3TXJxxg6Sor3B2NURj0ajrKJPNbAF12UDJpcMYGmCCQcoaYZkbNnspkvIDP/py
XH7EvLtZ5WKVMo/bDt1VVB1xHeeQ25lGfegR8wc04Yr246mykm/kJqk5t/FL5B1g
/HuSQNaAfNrDNWT7Nm2wk7AhhnoWj+UICv7dOWtZ4ugeljsCwR9ft9AtNKTAV5f+
smtNmNyE17jDbmsyG7wCc3nVsYlwY+kj2QFgMVylgAcMe3BDHBlPzo7vbd6hj0ty
SCdad+LmQMEvCcihCE0m+ienkGkVSRjnVM4WmhbxiSOlv6JUvDy3EGwYzsoxZExj
qaa532Fw0zN3
=FjbM
-----END PGP SIGNATURE-----

Re: bugs-1

Ludwig Hügelschäfer — 2012-05-19T11:57:31

david< at >gbenet.com wrote on 19.05.12 13:41:


You're taking quite a hard statement. Lots of people posting here are
successfully using enigmail, gpg2 and enigmail on different Linux distros.

Please, do not simply state such things where others succeed. There most
probably is some kind of bad setup which prevents the correct function
of gpg2. This can come from the distro's side, from gpg2 side, and from
enigmails side. If you want help to clarify and get a working
configuration, please give more information, but do not rant here.
Ranting will nobody get nowhere.

Ludwig

Re: bugs-1

2012-05-19T11:41:14

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

On 19/05/12 12:19, Patrick Brunschwig wrote:
Hi Patrick,

When using pgp2 - within Openpgp I take out the tick mark to encrypt - and guess what? It
still encrypts the e-mail but never ever to the recipients public key but my private key.
You can delete all your recipient rules because with pgp2 it still encrypts to your private
key.

There is no compatibility with Enigmail/Openpgp and pgp2. I have 3 laptops for testing and
have installed 32/64 bit Linux distros with pgp2 installed correctly. All fail.

David

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPt4baAAoJEOJpqm7flRExX+IH/i0ZSTcNk5jPgDUxn5aYVDDA
lXI6MYPW5WzWywmaTAmfmmHTwuY7rM7Q4IzFSIiz4gGjHovICaiE52yJWzUZgPMh
c/iy1XhmdMjJyEcFwHDZ27klepuZZaajc4haxTXEvYjrqXLo7gjzEr0CTHGYy6Pt
ag+EaGobltEDXyme4vPM1W0FDQIfXZdu1qm+k7e2X4NmG46dEFc7r+O+xAvGu+1R
Lq7IBoXsPICun0vizn/hYBrTlY1pu1RywTARtYSUKhVxYb6fMw7FiJu1bRsTmf11
avh7+XtXldE/GWiFmfSiOouEVTcnCMGvIbzo+ylk7IBKozg2R6u8iMyOsYOB0no=
=lSSv
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail< at >mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: Bugs

2012-05-19T11:34:28

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

On 19/05/12 12:16, Patrick Brunschwig wrote:
Hi Patrick,

All these settings are correct. I am not using the defunct gpg2 - I have tried it with lots
of Linux distros and found it to be useless. I have listed all the errors - and gpg2 knows
where it's files are stored gpg2 -k gpg2 --version I always run these commands when
installing a Linux distro. Gpg2 is incompatible with Linux distros - I've run tests looked
at bug reports - and the weird thing is that gpg2 is unable to sign and encrypt at the  same
time - sounds like Windows :) and Always encrypts to your private key and not someone else's
public key.

I do not recommend the use of pgp2 with Enigmail/Openpgp 1..4 with TB 12.1 it does not
support pgp2. Fact. It crashes freezes and does weird and wonderful things but it does not
provide any signing or encryption functions. It may work on Windows it may work on Macs but
it does not work on any major Linux distros.

David - who's no longer using pgp2!

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPt4U4AAoJEOJpqm7flREx6bcH/RtUx4OxHG9Q70F/Oh6oauFi
MA8mcpEeBLEQTpoAtMrTqBl0ArPZ1dVKQYftUVzkaSRrenYIfKOeg5dgEoBYj5BY
iiQt1oPudJD+L6AWNRg49e8GeVEXGvlBfbLJOrSRVHx+vlgDR6NqcupjwJq7tlMv
sSDcTBCmHTWpahVb1AA0YkOh8ACJyunBTIzAUMBq9/U05DnHh8iLhzsWq7nJSU3u
HIWN1KDEyl3QVztqAJAy4emZ5c6n5O28MnjMAPSOhoaK6TxtBIzY82x3OfgD57Fq
TtyXnNP7HQiDdhdVsi3TgJzoQ27E1PB6KviqyB4Wrcelp7JrxUzSi+3Z9qExIsI=
=Dw7r
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail< at >mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: bugs-1

Patrick Brunschwig — 2012-05-19T11:19:57

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

On 19.05.12 01:38, david< at >gbenet.com wrote:

The definition of per recipient rules is that they apply independently
of how you specify the encryption/signing options.

If you don't want to use the rules for a specific message, you can
turn the rules off using OpenPGP > Ignore Per Recipient Rules. If you
don't want Enigmail to enable or disable encryption automatically,
then don't use per recipient rules.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7eB3Mk25cDiHiw+AQgzagf+P5Oio0RXCiexaM+t5zE1dFtl6HWaqWnO
gYoW1nJ/HjnbPDK9pThVhEWvTCbYDxkK9E1nzcFS73UgNamUVSbUAiIUUhVNioet
jML9CgjLvas0837fLt20LdCXBwREVE8C4ihgFseYDYIGsR224hw9CJD80jzYmmt1
/dBjnSybFmpHUxH8dtipCIiQ90SC7tGKjVp7YJlx+pbmrA556YUcKPFjhWBJ5t+H
/gxifKLDAeIp/+H5IdibVExWAWSPPeiq62OqHCXbf3gxQojfBdt+Lzid3PgfcyHz
TjjTllxlR86Hn8ahLRj2yOKsb/mjz2OZRBlQgHosVHaC7WrnigfVbA==
=sZNz
-----END PGP SIGNATURE-----

Re: Bugs

Patrick Brunschwig — 2012-05-19T11:16:36

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

On 19.05.12 10:52, Andreas Hirsch wrote:

I think you misconfigured Enigmail. gpg-agent cannot be found in
~/.gnupg/options. The path to GnuPG is something like /usr/bin/gpg.
Normally, Enigmail will find gpg and gpg-agent automatically.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBT7eBE8k25cDiHiw+AQiWaQf/WInrOLibHO7cFg34zjQ3oo58yeYwVUyj
VHWMYfb1Mqa7nkrkRjdOEcMo4vFrpeOcKyqTMO97/hqPdMsUwdTRn4UmtkYrUfao
yJjeL1RaK6VRLtFa9TzmN6m+bGKSjeDWyg+VyaLk/eZTltQSGz37I+/KaAY0wrDR
4/nUYAAOX5M7vdWQvUR4D6OH4G1iAzHrEgwH3PoQcNgR8tMhaLrkSqtUxL6dWo3K
ZTrVrSBTuaHiiUEB+5YRR6rH33m/COta1Cv6T8mEUR/ddmcwjJJuBIyu1Jau/Agh
HKLl3ZmBMYeQo4pckXLV0qh013tggjzNFDvjnF0TIANWa5tDQgcdGg==
=X1zj
-----END PGP SIGNATURE-----

Re: Bugs

Mike Cardwell — 2012-05-19T11:01:42


I'm running the following setup:

Ubuntu 12.04
Thunderbird 12.01
GnuPG 2.0.17
Enigmail 1.4.1

I also run the same versions on a Windows 7 machine at work. I also ran
the same sort of configuration (with slightly older versions) on a
Macbook under OSX in the not too distant past.

enigmail encrypts with your private key making it impossible for the
recipient to read the e-mail.

This doesn't happen to me on any of my installations. I have "Add my own
key to the recipients list" ticked, which means it gets encrypted to
both their key and mine.

on how dysfunctional enigmail is.

This doesn't happen to me on any of my installations. I have "use
gpg-agent for passphrases" ticked in the Enigmail prefs. I have also
configured cache times explicitly in my ~/.gnupg/gpg-agent.conf

it freezes up.

This has never happened to me on any of my installations.

and then at a later date take out the tick mark then enigmail still
sends your public key even though there is no selection to do so.

I just tested this be enabling it, sending an email, then disabling it
and sending another email. It correctly attached the key to the first
email, and correctly didn't attach it to the second email.

rule and then write an e-mail - and take out the tick mark to encrypt -
it still encrypts!!

Presumably you have the "Always" option selected for encryption in that
per-recipient rule? In which case, it's doing the expected behaviour.

On the other hand, this also really bugs me. I would like to be able to
set defaults for a recipient, and then to be able to override them
during composition. I believe that would be both the most flexible and
the most user friendly solution.

I would like to see the "Sign", "Encrypt" and "Use PGP/MIME" options
removed from the "OpenPGP" pull down menu of the composition window, and
re-added as check boxes underneath the header fields in the composition
window, and for them to be automatically modified when you enter a
recipient address, but allowing you to manually modify them again before
sending.

Re: Bugs

2012-05-19T10:12:10

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

On 19/05/12 09:31, Charly Avital wrote:
Hello Charly,

The issues are with Linux - but have a good weekend too :)

David

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPt3H5AAoJEOJpqm7flRExjYgIAIh2A08QAHcPfXXGofWapmta
yFVzVLrmY53MlxzMxT58oVmrgE21AZueI3xcwWhu/+VW8qTuMclbdlTWxbCWqYks
ozXzkJ9BdSw+5gAGivPxtBP8UiVgaFBZzBfEZq3QoSnSGzzqg/YlcVc4QL39fWYI
ky980Yv2BDlqEOAz5KRBH7CUn7hN0OIKyVBA3EczzREP72xuoVGxL+EUkuVAdU7c
oycklHnbMIfJJuieb5QTbLH/+QBqHGYoNBVQt/y8xM3NnZ9NsOEceg46glvlYgvH
5Zm67vRalhTRyg8YXmCmCgZNkHeqMeU1W/ttPnIGoDeowRiybMf1/1ftbfJ6DCQ=
=Perk
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail< at >mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail

Re: Bugs

2012-05-19T09:47:52

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

On 19/05/12 09:52, Andreas Hirsch wrote:
I had things like no gpg-agent started - with Ubuntu - but it seems fine now that I've gone
back to 1.4.11 - which works with Openpgp - my Passwords and Keys would not even show my key
let alone anyone else's. I have tested the following Linux distros:

opensuse KDE/Gnome/LXDE - 32/64 bit failed with gpg2
Fedora-16 KDE/Gnome/LXDE 32/64 bit failed with gpg2
Ubuntu KDE/Gnome/LXDE 32/64 bit failed with gpg2
Linux Mint Gnome/LXDE 32/64 bit failed with gpg2

In short do not use gpg2 as it does not work with Linux distros!

Also gpg2 fails to recognise any specific gpg2 commands in the *.conf file and other GUI for
gnupgp may fail with gpg2 or not load or recognise you have a key or any one else's public
key. Also you may be lucky or unlucky in that the gpg-agent fails to run.

The biggest bug is that gpg2 encrypts all outgoing e-mails to your private key by default
and not to any recipients public key. It is also completely unsupported by enigmail -
causing multiple errors freezes and no support for per recipient rules.

I had so many errors with gpg2 on all Linux distros that I realised that gpg2 was totally
incompatible with all Linux Distros.

David

- -- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPt2w6AAoJEOJpqm7flRExi/IIAJ9Jg4q6JTI7aqu1Hn45XI8F
9certTsTLgVCvjdX8XQ+omNuYzHPB/PN9Z3celeBHc8HJNkCc/b4YsUp33JX8SUc
4+ieoiwQtbaapPfPiVPH9BmXg631k0UUG+XnFsK87FbQe8scZggfoFvVSiwZ2Zzy
a3yyi+DCW/XAx8CZA3THZoz4H+dXiO72WV0DmNAXX2mOFSvccPlAQjzO+rhjLpFe
Rc/Xouotc5ABUKQZbqUucRqrj4MYuRS2WzBdxRb2yWQuwBxbN008tG1z6BBnQbB2
lI80jbeegEhDGRiiOYI0IegGpehLw8QuFAjQ8e2GmFe5p1p1UnfssWbjsFe8m3I=
=hhM9
-----END PGP SIGNATURE-----
_______________________________________________
Enigmail mailing list
Enigmail< at >mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail