Bug 1409119 - gpg is not build with large secure memory buffer
Summary: gpg is not build with large secure memory buffer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg2
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-29 16:42 UTC by Frank Büttner
Modified: 2017-09-30 06:17 UTC (History)
4 users (show)

Fixed In Version: gnupg2-2.2.0-1.fc26 gnupg2-2.2.0-1.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-08 03:49:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Büttner 2016-12-29 16:42:30 UTC
Description of problem:
When using the option  large secure memory buffer the following warning will be shown:
WARNING: gpg not built with large secure memory buffer.  Ignoring enable-large-rsa

Version-Release number of selected component (if applicable):
gnupg2-2.1.13-2.fc25.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. add the option enable-large-rsa to the gpg config file (~/.gnupg/gpg.conf)
2. run gpg2 --version


Actual results:
The warning above

Expected results:
No warning


Additional info:
The configure script must called with large-secmem in respect to the man page.

Comment 1 Tomas Mraz 2017-01-03 09:35:11 UTC
The question is why upstream did not make this build option a default. Also see https://wiki.gnupg.org/LargeKeys

Comment 2 Fedora Update System 2017-09-05 16:04:08 UTC
gnupg2-2.2.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-22bee61e57

Comment 3 Fedora Update System 2017-09-05 16:04:33 UTC
gnupg2-2.2.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-a43ed4a971

Comment 4 Christian Stadelmann 2017-09-05 18:04:40 UTC
This bug report is marked as modified, but I don't see any indication that this bug is really fixed. Neither the upstream release announcement nor its NEWS or README file indicate any change related to this bug report, as does the Fedora spec file on https://src.fedoraproject.org/rpms/gnupg2/commits/master. I think there has been a mistake here.

Comment 5 Tomas Mraz 2017-09-06 07:19:27 UTC
The Fedora spec file contains the change and it is present in the changelog entry from Tue Jul 18 2017.

Comment 6 Christian Stadelmann 2017-09-06 07:35:27 UTC
(In reply to Tomas Mraz from comment #5)
> The Fedora spec file contains the change and it is present in the changelog
> entry from Tue Jul 18 2017.

Ok, thanks for the hint and sorry for the noise.

Comment 7 Fedora Update System 2017-09-06 22:29:41 UTC
gnupg2-2.2.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-22bee61e57

Comment 8 Fedora Update System 2017-09-07 14:31:31 UTC
gnupg2-2.2.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-a43ed4a971

Comment 9 Fedora Update System 2017-09-08 03:49:47 UTC
gnupg2-2.2.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2017-09-30 06:17:38 UTC
gnupg2-2.2.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.