Topic: No public key list shown!
I have firefox 3.0.5, firegpg (last version) and gpg4win-1.9.13 installed. I created a keypair with GPA. The problem is that no public key list is shown (even my own public key).
Forum for the FireGPG's extention. (!Don't post too links or wait we unban your, akismet is very aggressive)
You are not logged in. Please login or register.
I have firefox 3.0.5, firegpg (last version) and gpg4win-1.9.13 installed. I created a keypair with GPA. The problem is that no public key list is shown (even my own public key).
Errors in console ? FireFTP installed ? Path to GnuPG set ? --home yourpathtoyourgnupgdir in options (command line parameters) at last ?
Path to GnupPG is set to G:\Program Files\GNU\GnuPG\gpg2.exe (no errors), Do I need to install FireFTP and set the --home option? My home directory is used by default, but there is a conversion error in console (when running gpg2.exe), conversion from utf-8 to CP720.
No, don't install FireFTP .
Try to generate a key with FireGPG, does she appar in keys lists ?
No, I did, I even import a key, it was successful, but still not shown. Isn't it a problem of gpg2?
Last edited by momeni (2009-01-11 13:58:40)
Is there any documentation for firegpg configuration?
There was
Do you want I reinstall a wiki ? (in ~4 hours)
The problem solved with GnuGPG 1 but isn't it a bug, that it doesn't work with GnuGPG 2?
-----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-----
Ok, FireGPG (next release) will be gpg2 compatible
-----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-----
-----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-----
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.