Re: PGP signing/decoding problem

> O.k., then they all apparently use the same method to pass the
> passphrase via gpgme to gnupg. BTW, how do you use Nautilus with gnupg?

In the Nautillus version I have (2.2.1), contextual menu (right click on 
an icon) shows '(de)crypt' and 'sign' items.  Plain good Debian package.

> The problem is that all Gnome-2 apps use UTF-8 as charset, whereas your
> xterm apparently is set to ISO-8859-15 (or -1).  If you usually use
> Gnome-2 apps, IMHO it would be best to change the passphrase of your key
> from '8859 to utf-8:

I've done it and it seems to work !  :)

> At this point all Gnome-2 apps should accept your passphrase, but of
> course gpg in the xterm doesn't... However, you can change the input in
> the xterm to UTF-8, too, by setting the "utf8", "wideChars" and "font"
> resources properly (see the man page and the Unicode HOWTO for details).
> An additional drawback is that Gnome-1 apps (if you still use some of
> them containing gpg support) may not work any more with the new
> passphrase.

I'll try this, good way to have a better understanding of these charset 
encoding things.

>> What could be the other solutions to this problem ?  Should I report a
>> bug to Seahorse and/or GNU Privacy Assistant ?
> When I now think again about it, IMHO it's not a bug but a feature ;-))
> You just have to decide upon ONE consistent setup of your environment,
> and then it shoud work.

Yes, and thanks to your explanations I understand why.  I'll try to have 
a consistent setup in my environment.  Something to add to the Gnome-1 -> 
Gnome-2 transition manual !

Again, thanks for your help,


PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]