From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org, "Frank Küster" <frank@kuesterei.ch>
Subject: Re: default-enable-multibyte-characters in pgg-gpg
Date: Wed, 29 Mar 2006 17:16:34 +0200 [thread overview]
Message-ID: <87ek0lqo19.fsf@latte.josefsson.org> (raw)
In-Reply-To: <v9k6ad74yc.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 29 Mar 2006 15:31:23 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> Thank you for this explanation. I think we should clarify this in
> the ChangeLog as follows:
Done.
> 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):
>
> 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")
After fixing that minor issue, we would probably also have to make it
possible to configure which character set is used for the password
encoding. Perhaps your terminal was using ISO-8859-1 and emacs used
UTF-8, then gpg likely won't accept the password.
Alternatively, gpg should convert the password received from the
terminal-encoded charset to the charset used when setting the
password, or always convert to UTF-8.
next prev parent reply other threads:[~2006-03-29 15:16 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
2006-03-29 15:16 ` Simon Josefsson [this message]
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=87ek0lqo19.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).