From: Simon Josefsson <jas@extundo.com>
Subject: Re: Third OpenPGP backend: PGG
Date: Wed, 25 Sep 2002 16:58:00 +0200 [thread overview]
Message-ID: <ilu1y7iglqf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <6uit0u1jbc.fsf@zork.zork.net> (Sean Neakums's message of "Wed, 25 Sep 2002 10:59:19 +0100")
Sean Neakums <sneakums@zork.net> writes:
> commence Simon Josefsson quotation:
>
>> I added support for PGG in mml2015.el, and added a top-level directory
>> pgg/ which contains PGG and its dependencies. When copyright
>> assignment have been checked, hopefully files can be moved into lisp/.
>>
>> To use it, just put gnus/pgg into your load-path, Gnus should prefer
>> PGG over gpg.el and Mailcrypt.
>
> I get the following when I try to read an encrypted message. Updated
> from CVS about 20 minutes ago.
>
> Debugger entered--Lisp error: (args-out-of-range 0 0)
> get-text-property(0 gnus-details #<buffer *mm*<10>>)
> byte-code("\bÆ\x19\x1a^[\x1c\x1dÇ\x0e\x1fAÈÆÉ$\x14;\0\x0e ÊË\x1e!\x1e\"\x1e\x1f4\0ÌÍ\x0e\x1f@G\x0e\"\x0e!\x0e\x1f@%+ÎÏ\x0e\x1f\"ÐÑÒ!!\x1e#Ór\x0e#qÔ\f!ÕÖ׶\0r\x0e$qØÉ!\x13Ù\x0e\x1f!\x0e ÊÚ\x1e!\x1e\"\x1e\x1f\x7f\0ÌÍ\x0e\x1f@G\x0e\"\x0e!\x0e\x1f@%+\x0e Û ÜÝÍÛ\v@#Q\x1e!\x1e\"\x1e\x1f¥\0ÌÍ\x0e\x1f@G\x0e\"\x0e!\x0e\x1f@%+\v@<°\0\v²\0\vC)Ó\0\x0e ÊÞ\x1e!\x1e\"\x1e\x1f
Ò\0ÌÍ\x0e\x1f@G\x0e\"\x0e!\x0e\x1f@%+.\b" [mml2015-result-buffer decrypt-status result handles child pgg-errors-buffer nil mm-find-part-by-type "application/octet-stream" t gnus-info "Corrupted" put-text-property 0 throw error get-buffer-create generate-new-buffer-name " *temp*" ((byte-code "Á\b!\n\0Â\b!Á" [temp-buffer buffer-name kill-buffer] 2)) mm-insert-part err (byte-code "Âed\"r\bqà )\x11" [mml2015-result-buffer decrypt-status pgg-decrypt-region buffer-string] 3) ((error ...) (quit ...)) mm-dissect-buffer mm-destroy-parts "OK" gnus-details "\n" get-text-property "Failed" handle mm-security-handle value parameter temp-buffer pgg-output-buffer] 9)
> mml2015-pgg-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil nil ("attachment") nil nil nil) (#<killed buffer> ("application/octet-stream") nil nil ("inline" ...) nil nil nil)) (#("multipart/encrypted" 0 19 (gnus-info "OK" from "leklund@tastytronic.net" buffer #<buffer *mm*<5>> boundary "/9DWx/yDrRhgMJTb" protocol "application/pgp-encrypted")) (protocol . "application/pgp-encrypted") (boundary . "/9DWx/yDrRhgMJTb")))
Could you do M-x load-library RET mml2015.el RET and get a new backtrace?
next prev parent reply other threads:[~2002-09-25 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 14:45 Simon Josefsson
2002-09-24 19:31 ` Jesper Harder
2002-09-24 19:49 ` Kai Großjohann
2002-09-24 21:05 ` Jesper Harder
2002-09-24 19:52 ` Andi Hechtbauer
2002-09-24 19:56 ` Frank Schmitt
2002-09-25 13:50 ` Andreas Fuchs
2002-09-25 9:59 ` Sean Neakums
2002-09-25 14:58 ` Simon Josefsson [this message]
2002-09-26 9:42 ` Sean Neakums
2002-09-26 16:18 ` Simon Josefsson
2002-09-26 2:31 ` Katsumi Yamaoka
2002-09-26 3:27 ` tsuchiya
2002-09-26 3:55 ` Simon Josefsson
2002-09-26 4:05 ` Katsumi Yamaoka
2002-10-01 12:07 ` hird " Marco Lonsing
2002-10-01 12:45 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilu1y7iglqf.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).