Bug 171877 - rpmbuild --sign does not ask for pin or uses gpg-agent
Summary: rpmbuild --sign does not ask for pin or uses gpg-agent
Keywords:
Status: CLOSED DUPLICATE of bug 128771
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-27 12:28 UTC by Ralf Spenneberg
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-11-28 22:39:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ralf Spenneberg 2005-10-27 12:28:03 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21

Description of problem:
I use a smartcard for storing my gpg-keys. 
When signing something I need to enter a pin instead of a passphrase.

rpmbuild --sign just asks for the passphrase. This clearly fails. It never asks for the pin. 

Therefore I tried to use gpg-agent but rpmbuild does not honor gpg-agent. Even when using:
%_gpgbin "/usr/bin/gpg --use-agent"




Version-Release number of selected component (if applicable):
rpm-build-4.4.1-22

How reproducible:
Always

Steps to Reproduce:
1. use gpg-keys stored on smartcard protected by pin
2. rpmbuild -ba --sign <package>
3. Asked for passphrase would expect pin or agent
  

Actual Results:  Asked for passphrase

Expected Results:  Asked for pin or start pinentry program

Additional info:
Comment 1 Paul Nasrat 2005-11-28 22:39:49 UTC 

*** This bug has been marked as a duplicate of 128771 ***
Note You need to log in before you can comment on or make changes to this bug.