Bug 842074

Summary:	gpgme cannot provide passphrase to gpg2
Product:	Red Hat Enterprise Linux 7	Reporter:	Miroslav Vadkerti <mvadkert>
Component:	gpgme	Assignee:	Jiri Kucera <jkucera>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	ovasik, trailtotale
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:25:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1308754, 1630904, 1630910, 1660473

Description Miroslav Vadkerti 2012-07-21 18:12:40 UTC

Description of problem:

# volume_key --save -o packet-phrase /dev/loop0
Passphrase for `/dev/loop0': 
New packet passphrase: 
Repeat new packet passphrase: 
volume_key: Error creating `packet-phrase': GPGME: Invalid crypto engine

gpgme package is installed on the system

Version-Release number of selected component (if applicable):
volume_key-0.3.8-1.el7

How reproducible:
100%

Steps to Reproduce:
1. Create a luks device (for example on loop)
2. volume_key --save -o packet-phrase /dev/loop0
  
Actual results:
volume_key: Error creating `packet-phrase': GPGME: Invalid crypto engine

Expected results:
Passphrase packet successfully created

Comment 1 Miloslav Trmač 2012-07-23 15:37:26 UTC

Thanks for your report.  As a work-around, (yum install gnupg).

Comment 2 Miloslav Trmač 2012-07-23 16:13:51 UTC

Fixed in rawhide volume_key-0.3.8-3.fc18 , rhel7 build to follow.

Comment 3 Miloslav Trmač 2012-08-06 19:12:35 UTC

Dependency added in volume_key-0.3.8-4.el7 , and it should fix the error message from comment 0 - but please re-test, I'm pretty sure you'll run into #637902 (... and then this bug should be reassigned).

Comment 17 RHEL Program Management 2020-12-15 07:25:00 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.