8:43 p.m.
Hello
I have used years ago succesfully gpg with gnus, I then switched to
smime without much problems.
Now under Xemacs 21.5.32 (33) mua gnus I cannot open any gpg encrypted
message (either inline or pgpmime), always pops up an error concerning
missing function create-image.
Since people on this list use gpg and gnus:
Have they every faced this problem?
thanks
Uwe Brauer
Debugger entered--Lisp error: (void-function create-image)
create-image(" redirect.\n" nil t)
mml2015-epg-key-image("AD24CFB593B61FDD")
mml2015-epg-key-image-to-string("AD24CFB593B61FDD")
mml2015-epg-signature-to-string((epg-signature . [good "AD24CFB593B61FDD"
ultimate "5462A967D4B8761A7282AB35815DA2DC" (20941 . 58409) nil 1 2 1 3 nil]))
mapconcat(mml2015-epg-signature-to-string "\n" ((epg-signature . [good
"AD24CFB593B61FDD" ultimate "5462A967D4B8761A7282AB35815DA2DC" ... nil
1 2 1 3 nil])))
mml2015-epg-verify-result-to-string(((epg-signature . [good "AD24CFB593B61FDD"
ultimate "5462A967D4B8761A7282AB35815DA2DC" ... nil 1 2 1 3 nil])))
byte-code("..." [mm-security-handle context handles parameter value handle t
nil mm-find-part-by-type "application/octet-stream" gnus-info
"Corrupted" put-text-property 0 error epg-make-context
epg-context-set-passphrase-callback mml2015-epg-passphrase-callback (byte-code "Ä Å\n!\"Æ" [mml2015-epg-secret-key-id-list plain child context
epg-decrypt-string mm-get-part nil] 5) ((error ...)) get-buffer-create
generate-new-buffer-name " *temp*" ((byte-code "Á!«Â!Á" ... 2))
search-forward "
\n" replace-match "\n" mm-dissect-buffer mm-destroy-parts
epg-context-result-for verify "OK\n" mml2015-epg-verify-result-to-string
"OK" get-text-property gnus-details child plain #:temp-buffer decrypt-status
result inhibit-redisplay mml2015-cache-passphrase] 8)
mml2015-epg-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil
nil ("inline") nil nil nil) (#<killed buffer>
("application/octet-stream") nil nil ("inline") nil nil nil))
("multipart/encrypted" (protocol . "application/pgp-encrypted")
(boundary . "=-=-=")))
mml2015-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil nil
("inline") nil nil nil) (#<killed buffer>
("application/octet-stream") nil nil ("inline") nil nil nil))
("multipart/encrypted" (protocol . "application/pgp-encrypted")
(boundary . "=-=-=")))
mm-possibly-verify-or-decrypt(((#<killed buffer>
("application/pgp-encrypted") nil nil ("inline") nil nil nil)
(#<killed buffer> ("application/octet-stream") nil nil
("inline") nil nil nil)) ("multipart/encrypted" (protocol .
"application/pgp-encrypted") (boundary . "=-=-="))
"oub(a)mat.ucm.es")
mm-dissect-multipart(("multipart/encrypted" (protocol .
"application/pgp-encrypted") (boundary . "=-=-="))
"oub(a)mat.ucm.es")
mm-dissect-buffer(nil t)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(7617 nil)
gnus-summary-display-article(7617)
gnus-summary-next-page(nil)
call-interactively(gnus-summary-next-page)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:03 a.m.
Uwe Brauer writes:
Now under Xemacs 21.5.32 (33) mua gnus I cannot open any gpg
encrypted
message (either inline or pgpmime), always pops up an error concerning
missing function create-image.
That's a GNU-specific API. I started to write a wrapper library, then
gave up when Stallman refused permission to include the documentation
in our manual. (Specifically he refused to relicense the manual under
the documentation license he wrote because it's obsolete.) Maybe I
can find that code and leave it undocumented. :-(
Since people on this list use gpg and gnus:
Have they every faced this problem?
Surely there's a way to turn off those images (they can't be included
on a TTY in any case). Yes, that's a workaround, not a fix.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:27 a.m.
> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Uwe Brauer writes:
> Since people on this list use gpg and gnus:
>
> Have they every faced this problem?
Surely there's a way to turn off those images (they can't be
included
on a TTY in any case). Yes, that's a workaround, not a fix.
I looked into the code of question, indeed a image should be generated
to present the keys, yuck, frankly it is beyond my understanding why
such a feature would be needed or useful for decrypting email.
However I found a workaround: using an older gpg interface:
(setq mml2015-use 'pgg)
is your friend.
Default is now epg which causes this image problem.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:23 p.m.
Uwe Brauer writes:
frankly it is beyond my understanding why such a feature would be
needed or useful for decrypting email.
I believe the images are encrypted and stored with the key. So
when the image comes up you know whose key was used to encrypt or
sign. It's a marginally useful security feature AFAICS.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4164
days inactive
4165
days old
3 comments
2 participants
participants (2)
-
Stephen J. Turnbull -
Uwe Brauer