Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Daiki Ueno <ueno@unixuser.org>, ding@gnus.org
Subject: Re: PGG: byte length problem in pass-phrase
Date: Thu, 30 Mar 2006 10:59:16 +0200	[thread overview]
Message-ID: <87hd5gpau3.fsf@latte.josefsson.org> (raw)
In-Reply-To: <v9bqvp58eq.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 29 Mar 2006 21:59:41 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Wed, Mar 29 2006, Simon Josefsson wrote:
>
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>> For testing, I changed my pass-phrase to start with `ä' (#x8e4,
>>> U+00E4, LATIN SMALL LETTER A DIAERESIS) [...]
>>> 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.
>
> I didn't have any UTF-8 settings.  (The following setting are from a
> different machine, but I think I have the same locale and Emacs
> settings on both.)
>
> From M-x report-emacs-bug RET:
>
> Important settings:
>   value of $LC_ALL: nil
>   value of $LC_COLLATE: POSIX
>   value of $LC_CTYPE: de_DE@euro
>   value of $LC_MESSAGES: nil
>   value of $LC_MONETARY: nil
>   value of $LC_NUMERIC: nil
>   value of $LC_TIME: nil
>   value of $LANG: en_US
>   locale-coding-system: iso-8859-15
>   default-enable-multibyte-characters: t
>
> Minor modes in effect:
> [...]
>   unify-8859-on-decoding-mode: t
>   unify-8859-on-encoding-mode: t
>   utf-translate-cjk-mode: t
>
> M-x describe-current-coding-system RET:
>
> Coding system for saving this buffer:
>   Not set locally, use the default.
> Default coding system (for new files):
>   1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
>
> Coding system for keyboard input:
>   nil
> Coding system for terminal output:
>   0 -- iso-8859-15 (alias of iso-latin-9)
>
> Defaults for subprocess I/O:
>   decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
>   encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
>
> Do you see anything odd there?

No, Emacs should use ISO-8859-1(5).  Maybe your terminal was UTF-8?

I'm assuming you typed the same password in emacs as in the terminal.



      parent reply	other threads:[~2006-03-30  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29  5:51 default-enable-multibyte-characters in pgg-gpg 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
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 [this message]

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=87hd5gpau3.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    --cc=ueno@unixuser.org \
    /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).