From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: ding@gnus.org, "Frank Küster" <frank@kuesterei.ch>
Subject: Re: default-enable-multibyte-characters in pgg-gpg
Date: Wed, 29 Mar 2006 15:31:23 +0200 [thread overview]
Message-ID: <v9k6ad74yc.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <fbadf291-3e4a-421e-9c82-f7c00feecdbb@well-done.deisui.org> (Daiki Ueno's message of "Wed, 29 Mar 2006 20:59:04 +0900")
On Wed, Mar 29 2006, Daiki Ueno wrote:
>>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> As your patch just reverts this patch, I'd guess that it will
>> reintroduce the problem the other patch tried to solve.
>
> Ah, I understand why this was necessary at that time.
>
> When the patch was introduced, pgg-gpg used synchronous code and sent
> a passphrase together with data on a temp buffer: [...]
Yes, revision 6.17 (in Gnus CVS) had this code.
> So I think setting default-enable-multibyte-characters is no longer
> necessary because we switched to use asynchronous code and passphrases
> are sent separately.
Thank you for this explanation. I think we should clarify this in
the ChangeLog as follows:
--8<---------------cut here---------------start------------->8---
2006-03-29 Daiki Ueno <ueno@unixuser.org>
* pgg-gpg.el (pgg-gpg-start-process): Don't bind
default-enable-multibyte-characters. This reverts the change from
revision 6.17 which is no longer necessary because the passphrase
is sent separately now. GnuPG messages are unreadable under
multibyte locales with default-enable-multibyte-characters set to
nil.
--8<---------------cut here---------------end--------------->8---
For testing, I changed my pass-phrase to start with `ä' (#x8e4,
U+00E4, LATIN SMALL LETTER A DIAERESIS) which I can enter using
MultiKey-a [1]. When sending a signed message I get (both, with and
without default-enable-multibyte-characters):
--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (error "Attempt to change byte length of a string")
fillarray("\x8e4[...]" 0)
pgg-gpg-status-BAD_PASSPHRASE(#<process pgg-gpg<2>> "BAD_PASSPHRASE E222255A3C6B854E")
pgg-gpg-process-filter(#<process pgg-gpg<2>> "[GNUPG:] BAD_PASSPHRASE E222255A3C6B854E\n")
accept-process-output(#<process pgg-gpg<2>> 1)
pgg-gpg-wait-for-status(#<process pgg-gpg<2>> ("GOOD_PASSPHRASE"))
pgg-gpg-sign-region(1 256 nil nil)
funcall(pgg-gpg-sign-region 1 256 nil nil)
apply(funcall pgg-gpg-sign-region (1 256 nil nil))
pgg-invoke("sign-region" gpg 1 256 nil nil)
pgg-sign-region(1 256)
mml2015-pgg-sign((part (sign . "pgpmime") (tag-location . 1492) (contents . "[...]")))
mml2015-sign((part (sign . "pgpmime") (tag-location . 1492) (contents . "[...]")))
mml-generate-mime()
message-encode-message-body()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
--8<---------------cut here---------------end--------------->8---
Bye, Reiner.
[1] xmodmap -e 'keysym a = a A adiaeresis Adiaeresis'
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-03-29 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 5:51 Daiki Ueno
2006-03-29 11:24 ` Reiner Steib
2006-03-29 11:59 ` Daiki Ueno
2006-03-29 13:31 ` Reiner Steib [this message]
2006-03-29 15:16 ` Simon Josefsson
2006-03-29 19:59 ` PGG: byte length problem in pass-phrase (was: default-enable-multibyte-characters in pgg-gpg) Reiner Steib
2006-03-30 0:41 ` PGG: byte length problem in pass-phrase Daiki Ueno
2006-03-30 8:59 ` 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=v9k6ad74yc.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=frank@kuesterei.ch \
/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).