Bug 171877

Summary: rpmbuild --sign does not ask for pin or uses gpg-agent
Product: [Fedora] Fedora Reporter: Ralf Spenneberg <ralf>
Component: rpmAssignee: Paul Nasrat <nobody+pnasrat>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-11-28 22:39:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***