Mailinglist Archive: opensuse-bugs (3912 mails)

< Previous Next >
[Bug 915931] New: gpg Warning using insecure memory
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 03 Feb 2015 09:50:40 +0000
  • Message-id: <bug-915931-21960@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=915931

Bug ID: 915931
Summary: gpg Warning using insecure memory
Classification: openSUSE
Product: openSUSE Factory
Version: 201501*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: bpoirier@xxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

After a recent update, gpg started showing the following warning routinely,
for example when running `gpg --list-keys`:

ben@f1:~$ gpg --list-keys
gpg: Warning: using insecure memory!
/home/ben/.gnupg/pubring.kbx
----------------------------
[...]

Using strace, it appears that the mlock() call is failing:

mlock(0x7f5814308000, 262144) = -1 ENOMEM (Cannot allocate memory)

I addressed the situation by increasing the -l ulimit from what was the
current value of 64 to 512, using /etc/security/limits.conf

ben@f1:~$ rpm -qi gpg2
Name : gpg2
Version : 2.1.1
Release : 1.1
Architecture: x86_64
Install Date: Tue 27 Jan 2015 02:07:54 PM CST
[...]

A quick look at another machine with gpg 2.0.26 shows that it locks a smaller
amount of memory, ~32k

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages