the new svn version is working !
Thanks
1 2009-02-10 10:07:26
Re: Did I lose the firegpg icons/links in Gmail...? (3 replies, posted in Bugs & problems)
2 2009-01-22 13:40:27
Re: Invalid signature (3 replies, posted in Bugs & problems)
MIME-Version: 1.0
Received: by 10.210.52.19 with HTTP; Thu, 22 Jan 2009 03:09:36 -0800 (PST)
Date: Thu, 22 Jan 2009 12:09:36 +0100
Delivered-To: aongenae@gmail.com
Message-ID: <83713a650901220309r6820ce27mf88de5ecb93f34d8@mail.gmail.com>
Subject: Test
From: Arnaud Ongenae <aongenae@gmail.com>
To: Arnaud Ongenae <aongenae@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
---/--BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ceci est un test avec une longue ligne. Je test openpgp/mime
fonctionnalit=E9. J'aime beaucoup FireGPG et je pense qu'il peut
r=E9soudre un des plus gros prob=E8mes de PGP pour les non-geek qui
veulent une interface simple et fonctionnelle sans avoir =E0 se rendre
en console, ci qu'il ne feront pas de toute fa=E7on...
Je veux aussi montrer un bug... contradiction entre la v=E9rification
automatique affich=E9e en dessous du mal et la v=E9rification manuelle...
---/--BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJeFPvAAoJEFgy9SDyxO8hEl0H/iR8JtiE4I4dgTcEdH50b/id
0ClZdxwo/yuQTDze8X/MFQIG+/RylHjKWxKH/OZchNzDzh1i8dWCeHXA3iHPoJQp
xTnizgfOOEmncgeYki4Dg5+wtVo1Qrfo68ghXeblK2K19Ve94vFFWA8pqRaWK/CY
Bz6vMlcaRpZtSN1TLls37sy/jmExf74xIu2Mr4B9F35Rbgh7XQLispJ9kWC3tSqc
bTAi0BnZTRSPvDtKmYWjn6vtwckcmESVhuRTIhHmACTdaCo2krn1fZyNdtTSbSOR
wnN0btVu4wHSideMS4nVxH3fCrlVCR9ltlRHUd6/xSlqTG7LleN2EWzPKjlphNs=3D
=3D6E8i
-----END PGP SIGNATURE-----
Je ne sais pas comment reconnaitre si un message est encodé en bas64 ...
D'un autre coté, cela doit être considéré comme un bug, cela retire le coté simple de la vérification et l'utilisateur devrait recevoir un message d'erreur l'invitant
3 2009-01-22 12:20:15
Topic: Invalid signature (3 replies, posted in Bugs & problems)
Hi, me again... 
I try openpgp/mime feature and the signature was not validated on the Gmail interface (below the mail) but is correct according to the contextual menu and in my terminal...
I made a screenshot to show the problem...
Je ne sais pas si c'est une bonne idée de parler en français, tous les visiteurs ne parlant pas cette langue :s
4 2009-01-22 10:40:17
Re: broken clearsign after sending (7 replies, posted in Bugs & problems)
the_glu wrote:
No
But notice using openpgp/mime sign will never fail, so you don't need to check them
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
'never fails' make me smile , in computer science it's quite
audacious to say this , that make me remember this:
'Les trois grands mensonges de l'informatique :
Ca marche. - C'est compatible. - Ca sort bientôt.'
If you can't trunkate the message , could you add a vertical
line in the text editor at position 60 for example , so I know
when I have to press the 'enter' key ?
Regards
Arnaud
ps: even if it works while sending mail it doesn't work in
this forum
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
iQEcBAEBAgAGBQJJeD5XAAoJEFgy9SDyxO8hxH0H/3B9/wWlldYWQUKotUUstACt
gwEstFRK/HOqS9+CaERl9ip9Oa1P4g3EUoNOSb4UPFsd7zbvs/WRQ2SuOfVyCS9H
hLDV8Pkc/TyiRFXNIvln/6AHn8S/mJj5HHx+/oJih3CR8hZ8rn5O+GtZRJv2w5fr
i2GGCr6NDj4ypkPI7lCL+yykmG5PoEPLwKzGvpkkLXrrNSjRQbDU3xSHOMfrW3L7
OmvZEYowepQPJNVwtNDWcL1sSuSpjn1DltfLlq5DehCHK18/vp4vvH5q9LdT9ZoS
HHrwgugRwLQZZHjWu1C6hQRqzrWG6ch0p7WbqbG3BR4tHcyWZAA+RHmgPrN8GnY=
=v0jZ
-----END PGP SIGNATURE-----
5 2009-01-22 10:01:16
Re: broken clearsign after sending (7 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I know that I can't and I also know that the contextual menu's
clearsign doesn't trunkate the message before signing which get
me back to my original feature request...
Is it possible to trunkate the message before (clear)signing it ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJeDVQAAoJEFgy9SDyxO8hdmcIAKIt2KWP6qN5SrWuVjztbxt/
lwW++CSA3hiOKDg0sLXvdU20d9w49rcaV6fbafjbjrSUA8rTvgpPEvX2wpRkC19G
Z/4+z7wAQGI6eqTwP83Q14Hdxw9txJGqU86qJRRxVHUVN3cTWocSHRD1cvjajGfr
14eElpLAoGeWZxsMeWxiu2yQORfYBYXdEnPrr5leMQsIlo/e3XkVOed96xnk2bPu
PVkMrBJ41kG4BtaOSzfl8GwVSEudn+Bm2FnuehW6GDpt/HE402kCcP3Qg5aVqvs2
FHW6xzhPMPB0qfUNMYfiEDtxLktyIJuDteUaqQ/pRbd+xE0I+HD0PaNLzDhrpZM=
=ZoTY
-----END PGP SIGNATURE-----
6 2009-01-22 09:36:42
Re: broken clearsign after sending (7 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok, it works when I choose "sign" and "inline" option in Gmail interface,
but I want it working outside the gmail interface (eg in this forum).
Moreover, I like to check the signature before sending the mail, I don't
find how to achieve this with the new Gmail's interface
Thank you for your extremely fast answers
Arnaud
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
iQEcBAEBAgAGBQJJeC+GAAoJEFgy9SDyxO8htCEH/0XHAeswatVXn1DPs4Mif+JW
tkrbwLzz2tv4V2Wj/tpP0R18xIwzfeLqCgtVZX+jf1DvPYLmL7GL8i1LVTl4Vd+0
YKQrB7Y0SX7HJv09L/Is+i0punlC6L/gI2qfBi/3EhBxILWi58P0gLR0hZeSzPgz
4B5FZVDjHMvFOxwhgz9ca0sLoc0/jF14v/sV/ZhSbudrPP07XTnvpHmVHDhmnKII
1CMIJjBYpOhAJiYEQTDOhMTCsx+lAygouc5xd1cRwf1BvEAzA3exz917kVS+wn7m
dME4xEDVHE3vtOrb4zEdu+YTCIL0NX0AwE5h5uS+I9/3J2yQaPbzVsYLqaAllao=
=FdmW
-----END PGP SIGNATURE-----
7 2009-01-22 08:41:44
Topic: broken clearsign after sending (7 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I usually encounter a bug which is horrible.
When I write long line in my mail on Gmail, when sending the mail Gmail truncate the mail so the line are never longer than 75 characters (It think).
When I did put a clearsign signature, Gmail add some end-of-line character that compromise the signature. Isn't it not possible to truncate the text before a clearsign ? (maybe with a confirmation from the user... :s )
The problem isn't specific to Gmail but to all interface where the text is modified between the editing pane and the shown result (eg it also occurs on this forum where the half of my signature are not good once the message posted)
Arnaud
ps: maybe it was already pointed out but I didn't find it explicitly
pps: I add some text so Askimet will let me post without being banned 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJeCH+AAoJEFgy9SDyxO8haUoIALD7SarXnafjaPfPgSVCgtmf
U93u8W236CwcAFDIdfYgFxR2fR4iv9EHXnrgckC5EUW9S2UMIavtUnHu2vp7t1mi
gsZ1kv6DPOCgg3HmyoURren+7xGPdSI+5sWwljfW0HpOaOXkqVurUUqfasKFBlcL
WjIb7FWKIK8/mQRmFt+Zr4VYZg2FARC6qUBpNu7Yv5igOQeE823dfNw5NEfhNpS/
EYVWe8sQvEYBGwIvaSy+Fs8zUEApnx8jhHK01Y6kqS54+Q28KeAz5+TpVknGSGWf
6umQYwMALQO9XzdbMnKOGOrZxvRl7de4Lx14iwSK+ZhAxho1kSjzh/SUifnbdKE=
=yNTD
-----END PGP SIGNATURE-----
before the "preview" I get this when I verify the signature:
$gpg --verify mail
gpg: Signature made Thu Jan 22 08:36:30 2009 CET using RSA key ID F2C4EF21
gpg: Good signature from "Arnaud Ongenae (signature only) <aongenae@gmail.com>"
gpg: aka "Arnaud Ongenae (ucl purpose) <arnaud.ongenae@student.uclouvain.be>"
gpg: aka "Arnaud Ongenae <arnaud.ongenae@osmoteam.net>"
gpg: aka "[jpeg image of size 3849]"
after the "preview" I get this:
$gpg --verify mail
gpg: Signature made Thu Jan 22 08:36:30 2009 CET using RSA key ID F2C4EF21
gpg: BAD signature from "Arnaud Ongenae (signature only) <aongenae@gmail.com>"
:'(
8 2009-01-21 23:15:46
Re: No public key list shown! (15 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
One word: Merci !
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJd55QAAoJEFgy9SDyxO8hxxsH/R27m6kppSOmnhxOe4od0Znp
wMiw4V/B62FSjXI1s11B0wPqKA80KcnF7LxsjvOKIMzPGPFbIJV0pIF8LyItkgg9
QNpupn7YWnz60Uul0PehBcH5P95BiJ7crI+Cy2tfbAy2pM5gICLGek7GjzTN+/jy
5v3HU0Ow94g1ouOt8ifgLMm3hdM+H1GUY9ASKQ86+sxpJ3XLlNZg7KYW5X3WTH+f
SXAtSmlz+vAMJQe264FYydtRK5GS4LR3xZqaZHtInIFHvL9rJ/yR5i5ptokCyMDm
upCjNqr/3QEWSml2+9ffFBKZ/ekGTr04rO/JrQONcPdrnRxm9H4ygGw6PEILBN4=
=EONC
-----END PGP SIGNATURE-----
9 2009-01-21 22:49:19
Re: No public key list shown! (15 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You are working on it, you find the bug ?
I update to the svn release 512 which solve the following
bug/request:
2009-01-19 Maximilien Cuony
* FS#201
* FS#202
* FS#198
* FS#194
* FS#193
* FS#188
* FS#197
* FS#199
* FS#22
but not the 195 wich is the one of this topic...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
iQEcBAEBAgAGBQJJd5a6AAoJEFgy9SDyxO8hXl4H/3ZRM20UscLrCyp27D3Tjej7
2YU4X5KITH9fb3SW2BDTMOntKB7i/9n8aZ77YXZNKTEAc6Xqm3AaGT8+tvBF8Vr3
i+8cIGfWiC4dOJuJVouxv5YeH50QqcW95EUDkSY6Kcipa8dDoe25udB7hmPc/VQd
xJKeGZVLK99wCX8gtz6NF1TyQIVRPQfGp2En2gmm6kBblIoRCQcYtJiCqAoAAwzK
9FJSl8jGVHR80OSV+xD3Oabifl1zGmEndu1DSq20JwbKm4VWVTBQtC7o8m6ZTFvA
vmnb/wX763E5tWcD8ggFwPFtUnprBUwl/FYpuhtubsrGs2Goagvxe1pf/5CmF7c=
=d+XM
-----END PGP SIGNATURE-----
10 2009-01-21 08:23:37
Re: back to an old version (7 replies, posted in Requests)
Because the bug that I pointed out with the key manager and gpg2
only appear on the version 0.7
It used to work with the previous version so I wanted to switch back
to give it a try.
I found how to checkout a previous version and to compile it but it
doesn't solve the problem 
I don't understand why even with a
previous version the bug is still present
I'm forced to use gpgv1 :'(
11 2009-01-20 21:19:12
Topic: back to an old version (7 replies, posted in Requests)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
How can I switch back to an old version ?
through svn or ... ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJdjF5AAoJEFgy9SDyxO8h3jIH/0HDX7rK+vKfcVxS04bAJo5k
uGfZMg3UY/K/k7dXhQYlz/J6/Pgm0bCGWU8GzRAfCX1HT9ysZGQ663tzY07SgYkP
kzqgv1V2q2hMnAroKCdz208iDOgsZlj+J2TMFKjj4qx9nUgyv8Y+KIScYpbV4Hd7
MBynuUN3ndU5sNIU31giBKtjp9TByAtbDvv7nlI9TlWRPiF0OlqYhZ212RlG1mfO
hoD99Aaqijl3hRn3q4yPNeGkO0OC/y8dOjlO0/Vh0JR/TKymeeOLO3iuMLmNuFJk
ePYkuBwxvuRvEWXdmKxvMvXIsVkIWIgpCR4XA9JhT19J7wzNG91UD5vbM8p92No=
=rk5C
-----END PGP SIGNATURE-----
12 2009-01-20 17:39:35
Re: No public key list shown! (15 replies, posted in Bugs & problems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I encounter the same issue on osX 10.5.6 FireGPG 0.7
It works (show the key) with gpg1 but not with gpg2 :'(
When I create a new key, it is well created and appear in
$ gpg2 --list-keys
but not in the FireGPG's key manager
Any solution, even hard-coded one ?
Anyway thanks for the HUGE works done, I use FireGPG for years and it's a real pleasure !
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: http://getfiregpg.org
iQEcBAEBAgAGBQJJdf39AAoJEFgy9SDyxO8hm10H/iJpf+NI0rqlvIQxF4x5HUl8
9cnvJbmKo/6WccVFIYhB8J4DzP8PApWsu+ak65KgMmFyHLEnsAh/6Kiye1yTmOsC
FXeuFTZjA5rzFAaFtYaW81IhXEF/BjUS2h16ucO/VFSvXrFzam1xt9wh6J/gdVuc
UnlJlKH7e65G19CmEDXh4LYy72rwUpwtgovCOTalpYkGebdbFnKMEnMN2O1xyIDs
iGPKYKe+FgNbDBJevP2mQ2aqlNIxL3QVsqHt/6HEPz1DdK1LnERKaVg2jbOEJpV9
VeJKC9BFHGxJ/briZ/85XE1UJeZgIAktERcfp5UcNE45vnM4NbraZIqVeT96S/s=
=EhNb
-----END PGP SIGNATURE-----