[Bug 418535] New: yast2-product-creator product signing fails
https://bugzilla.novell.com/show_bug.cgi?id=418535 Summary: yast2-product-creator product signing fails Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bart@geesink.org QAContact: jsrain@novell.com Found By: --- When I choose to sign my installation repository in yast2-product-creator, I get a dialogue stating: Error: Could not digitally sign the source: Try again? I looked in y2log, and found these entries: 2008-08-20 10:32:31 <1> werkbak(3577) [YCP] GPG.ycp:57 gpg command: gpg --detach-sign -u 'A5E0435C' --no-tty --command-fd=0 -a '/home/bart/kiwi//openSUSE11dvd_with_khmer/Addons/openSUSE-DVD//content' < '/tmp/YaST2-03577-ftcjdX/stdin' 2008-08-20 10:32:31 <3> werkbak(3577) [bash] ShellCommand.cc(shellcommand):78 gpg: problem with the agent: No pinentry 2008-08-20 10:32:31 <3> werkbak(3577) [bash] ShellCommand.cc(shellcommand):78 gpg: skipped "A5E0435C": General error 2008-08-20 10:32:31 <3> werkbak(3577) [bash] ShellCommand.cc(shellcommand):78 gpg: signing failed: General error 2008-08-20 10:32:31 <3> werkbak(3577) [YCP] GPG.ycp:76 gpg error: $["exit":2, "stderr":"gpg: problem with the agent: No pinentry\ngpg: skipped \"A5E0435C\":General error\ngpg: signing failed: General error\n", "stdout":""] 2008-08-20 10:32:31 <1> werkbak(3577) [YCP] ProductCreator.ycp:666 Signed source: false If I execute gpg --detach-sign -u 'A5E0435C' --no-tty --command-fd=0 -a '/home/bart/kiwi//openSUSE11dvd_with_khmer/Addons/openSUSE-DVD//content' < '/tmp/YaST2-03577-ftcjdX/stdin' manually, I get this error: can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory When I execute this command: gpg-agent --daemon --use-standard-socket then the signing will not fail. If I start yast2-product-creator from the console where I started the gpg-agent manually, then the signing works as expected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=418535
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=418535
User lslezak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c1
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=418535
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c2
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=418535
User bart@geesink.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c3
--- Comment #3 from Bart geesink
https://bugzilla.novell.com/show_bug.cgi?id=418535
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=418535
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c4
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=418535
User bart@geesink.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c5
--- Comment #5 from Bart geesink
https://bugzilla.novell.com/show_bug.cgi?id=418535
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c6
Petr Uzel
If I do the same command, and use "su -", the error becomes: can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory
This is OK. It only means, that gpg can not connect to the gpg-agent (it looks to ~/.gnupg/S.gpg-agent if there is no GPG_AGENT_INFO environment variable). If it can't find any suitable gpg-agent running, it starts its own gpg-agent and everything should work fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=418535
User bart@geesink.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c7
--- Comment #7 from Bart geesink
https://bugzilla.novell.com/show_bug.cgi?id=418535
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c8
Petr Uzel
Ah yes, and I see I haven't looked well at my original first bugreport comment, where I put a part of the logs, which show exactly that the problem is the same as in bug 422093. Sorry about that.
No problem and thanks for the info.
The problem still remains. If I open the product creator from YaST, I will get that error. I can only use it if I start YaST from a commandline, after 'su -'ing.
I've asked gpg developers what can be done with this (it is not certain that it is actually a bug). For now, I can only advise to use 'su -' as a temporary workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=418535
User bart@geesink.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c10
--- Comment #10 from Bart geesink
https://bugzilla.novell.com/show_bug.cgi?id=418535
User lslezak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c11
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=418535
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=418535
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=418535 Bug 418535 depends on bug 422093, which changed state. Bug 422093 Summary: gpg does not work after su https://bugzilla.novell.com/show_bug.cgi?id=422093 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Status|ASSIGNED |RESOLVED Resolution| |WONTFIX -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=418535
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=418535#c12
Petr Uzel
Just a thought: Couldn't this be a problem of YaST (when started from the KDE menu) starting with the wrong su parameters?
Or should YaST not have the environment variables of the root user? This might fix this particular issue, but it would probably break many other
This looks like a good idea, but AFAIK it is not possible, because kdesu does not have option similar to 'su -'. things. I have to close this as WONTFIX. As a workaround, I suggest to 'unset GPG_AGENT_INFO' in /root/.bashrc or use 'su -'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com