Bug 79351

Summary: Character passing error in security/pinentry-qt
Product: Ports & Packages Reporter: Harald Schmalzbauer <harry>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me CC: lofi
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Harald Schmalzbauer 2005-03-30 05:20:03 UTC 
	qt-pinentry can't pass at least the character "§" correctly

How-To-Repeat: 	change your gpg-secret-key passphrase to something which contains "§" and you won't
	be able to use your passphrase with qt-pinentry, you'll get the error that the passphrase
	was incorrect, but it wasn't!
Comment 1 Michael Nottebrock freebsd_committer freebsd_triage 2005-03-30 16:10:58 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->lofi

Over to maintainer.
Comment 2 Michael Nottebrock 2005-03-30 16:51:23 UTC 
I have confirmed the bug and reported it to the upstream developers. There 
seems to be a problem with incompatible encodings of passphrases between 
gpg-agent and gpg.

If you want to use a passphrase containing § with gpg-agent and pinentry, you 
have to set it with gpg-agent and through a pinentry as well.

To salvage and "convert" your current key, do this (make sure gpg-agent is 
running):

1.) env | grep GPG_AGENT_INFO <- save the output of that somewhere.

2.) unsetenv GPG_AGENT_INFO

(unset GPG_AGENT_INFO if you're using bash/sh/zsh)

3.) Run gpg, type passwd. Make sure you do NOT get a pinentry dialog. Change 
your passphrase to something without 'dangerous' characters (i.e., just 
ascii-letters and numbers), type save.

4.) setenv GPG_AGENT_INFO [previous value which you saved in step 1]

(export GPG_AGENT_INFO=[previous value that you saved in step 1] if you're 
using bash/sh/zsh)

5.) Run gpg, type passwd. Make sure you get a pinentry at this point! Change 
your passphrase back to the string containing § in the pinentry dialogs, 
save.

The passphrase should be accepted by all pinentry programs. It will not work 
however in gpg running without agent. If you want to use gpg-agent on an 
on-and-off basis, you'll have to use a different passphrase for now.
Comment 3 Michael Nottebrock freebsd_committer freebsd_triage 2005-08-19 07:18:16 UTC 
State Changed
From-To: open->analyzed
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2008-09-07 01:36:41 UTC 
Responsible Changed
From-To: lofi->freebsd-ports-bugs

Maintainer was reset.
Comment 5 Stefan Walter freebsd_committer freebsd_triage 2008-10-17 13:16:46 UTC 
Hi Harald, hi Michael,

I'm trying to find out what the state of the problem report ports/79351
[1] is. Has the problem been fixed in the meantime and can this PR be
closed?

Regards,
Stefan

[1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79351
Comment 6 Harald Schmalzbauer 2008-10-17 13:50:32 UTC 
Stefan Walter schrieb am 17.10.2008 14:16 (localtime):
> Hi Harald, hi Michael,
> 
> I'm trying to find out what the state of the problem report ports/79351
> [1] is. Has the problem been fixed in the meantime and can this PR be
> closed?

AFAIR this was corrected several months ago. I haven't tested but 
remember a committ message which mentioned the correction.
I don't have qt on my desktop any more, but a quick 'gpg -c 
~/.Xauthority' showed that gtk-pinentry works with !"§$%&/()=?

Thanks,

-Harry

> Regards,
> Stefan
> 
> [1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79351
Comment 7 Stefan Walter freebsd_committer freebsd_triage 2008-10-17 14:10:12 UTC 
State Changed
From-To: analyzed->closed

The problem is believed to be fixed.