shavital at mac
Apr 3, 2006, 1:43 AM
Post #1 of 1
(305 views)
Permalink
|
|
GnuPG 1.9.20 on MacOS X - Question about agent
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks to the patches posted by Remco Post in this forum, for libksba
and gnupg 1.9.20, I could have the latter configured for:
Platform: Darwin (powerpc-apple-darwin8.5.0)
OpenPGP: no
S/MIME: yes
Agent: yes
Smartcard: yes
Protect tool: (default)
Default agent: (default)
Default pinentry: (default)
Default scdaemon: (default)
Default dirmngr: (default)
PKITS based tests: no
But 'make' posts the warning:
- ----------
gpgparsemail.c:150: error: static declaration of 'stpcpy' follows
non-static declaration
gpgparsemail.c: In function 'parse_message':
gpgparsemail.c:603: warning: pointer targets in passing argument 2 of
'rfc822parse_insert' differ in signedness
make[1]: *** [gpgparsemail.o] Error 1
make: *** [check-recursive] Error 1
- ----------------
and of course 'sudo make install' warns:
- -------
then mv -f ".deps/gpgparsemail.Tpo" ".deps/gpgparsemail.Po"; else rm -f
".deps/gpgparsemail.Tpo"; exit 1; fi
gpgparsemail.c:150: error: static declaration of 'stpcpy' follows
non-static declaration
gpgparsemail.c: In function 'parse_message':
gpgparsemail.c:603: warning: pointer targets in passing argument 2 of
'rfc822parse_insert' differ in signedness
make[1]: *** [gpgparsemail.o] Error 1
make: *** [install-recursive] Error 1
- ---------------
Running MacOS X 10.4.5, gpg 1.4.2.2, S/MIME works correctly,
But when I enable the use of agent in gpg.conf and in the MUA
(Thunderbird 1.5+enigmail 0.94.0) I get a warning that the passphrase is
not correct.
Is this because of the 'parse_message' error, and if so, how could I remedy?
Thanks, and sorry for cross posting
Charly
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: GnuPG for Privacy
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRDDgO269XHxycyfPAQjMGA/+PQ8Tjm/rydR5LTI4yyg8Hl0vQmZYsBL2
3oex/R3aZwCSI6whG+D3x8YVQ/evyD0yAAuKhqD5SeYBXeEvi71/vteAeKtXvgVG
8YG4iuF/Ld4smhQnZlOtoSVyGJbZE2hfkQ/PCOnP8rRm2/vZCfitAISMbi2AnL6D
3tqASibokmDMePzlUSeMw5lWmlm0a1Aw53fo0dYGMDF/p4R6eISEq9iTeJFLEqp7
Z3NXuuBRccd20LBNLz3ROIY7yeWHZZ26TmWm3BgY8L2CqxV9WHjoF/OUsDI98+3r
Vd1Ug/ZyGtKhsiPXnEA1qSemEZVCc8oJWEDYSrjYklOXSCxvpkaEDM25tndpaWND
JRYuHfbHtanMgdqzgwbbcUfSZ4+Tg94OHG9UJgt0+jyyXd0hc1z05QiXy+31KqNn
7l8JwVkbgQngFXYO9RkhXU0VI0lccvz5lfr7/GpkFohJgPnl+ScFz6L9FPgMOWS0
FQUvjBngqG5OFzzbdZKF3Ly1io4X+b0kYFLItuv4BQ869h+UZ1ATiuZUZ1ScQSu7
eQVud3yku0JlSCWTDylNtw+idtCmSQlw9xZ/bA3a9Abbgh3EcejDWrdHMTU+0ofx
z+g2ffoPg6FvFnkMpJUVOK9ViL9mcoYlkcLE6hkp05q6J/0YAicCi1DtQ+3jd01J
ZlR8zfd2EWk=
=Cx5G
-----END PGP SIGNATURE-----
_______________________________________________
Gnupg-users mailing list
Gnupg-users[at]gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
|
