On Wed, 19 Jul 2006 13:52, Benjamin Donnachie said:
> Is this a problem which gpg-agent could be modified to solve, perhaps?
Not with old passphrases.
However the APIs between the GnuPG 1.9 modules do all use utf-8, so in
some future this problem should vanish.
Salam-Shalom,
Werner
Werner Koch wrote:
> We don't know the charset used. In fact, gpg considers the passphrase
> as binary data with the only exception that a null byte or a LF
> termintate that data.
Is this a problem which gpg-agent could be modified to solve, perhaps?
Ben
___
On Tue, 18 Jul 2006 17:47, Patrick Brunschwig said:
> How about some new command line parameters that specify the charset of
> the passphrase provided and/or the charset in which the passphrase is
> stored on the keyring?
We don't know the charset used. In fact, gpg considers the passphrase
as b
Werner Koch wk at gnupg.org wrote on
Tue Jul 18 12:18:45 CEST 2006
>On Mon, 17 Jul 2006 12:27, Karl Kashofer said:
> So, how would I examine the charset talbles ? The UserID and
other >information printed by GnuPG is correctly displayed with all
the >umlauts. How do I find out what character I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch wrote:
> On Mon, 17 Jul 2006 12:27, Karl Kashofer said:
>
>> So, how would I examine the charset talbles ? The UserID and other
>> information
>> printed by GnuPG is correctly displayed with all the umlauts. How do I find
>> out what ch
Werner Koch wrote:
> You need to try. There is no conversion inside gpg and gpg uses
> whatever you type/feed. I see that this is a problem between
> different platforms. However there is no real solution for this
> problem because it would break all non-ASCII pasphrases currently in
> use.
Per
On Mon, 17 Jul 2006 12:27, Karl Kashofer said:
> So, how would I examine the charset talbles ? The UserID and other
> information
> printed by GnuPG is correctly displayed with all the umlauts. How do I find
> out what character I have to type to get the umlaut in my passphrase?
You need to tr
just convert everything to utf-8!
Regards,
--sk
>Hi all !
>
>This should be a simple question, but I have failed to find an answer to it.
>
>Is it possible to use german umlauts in the gnupg passphrase?
>
>The reason I ask is that I imported a keypair from my windows keyring when I
>switched my
Hi !
> This is a Charset problem.
Yes, thats what I guessed.
> Two solutions may work:
> -examining the Charset tables, you can find what character should be
> entered and accepted. Example, with my Charsets, this is what I see for a
> user: RÚgis DÚcamps (+ëlÞve ingÚnieur IIE)
> and
It's possible to use non-7-bit-ascii characters for the passphrase, but
there can be issues with character sets when changing from machine to
machine, OS to OS, or on different revs of an OS depending on locale
settings. Personally I'd advice using oe instead of ö just in case, although
if you're c
Hi all !
This should be a simple question, but I have failed to find an answer to it.
Is it possible to use german umlauts in the gnupg passphrase?
The reason I ask is that I imported a keypair from my windows keyring when I
switched my laptop to linux, and now I cant use it as it has umlauts i
11 matches
Mail list logo
