Problems with gpg decrypt. Locked process.
Mario Adrián López Alemán
mario.lopez at gazzang.com
Thu Feb 6 20:18:42 CET 2014
Hi everyone.
I'm investigating a problem with our application.
The problem that we currently have is when we try to decrypt a message.
Apparently when too many requests arrive at the same time, the system
just hangs.
This happens randomly, but I can reproduce it with no problem
I'm currently using (GnuPG) 2.0.14 in RHEL 6
Here's an example of what I see with ps aux.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
app 8275 0.0 0.0 119220 1656 ? SL 22:53 0:00 gpg2
--homedir /var/lib/home/.secret --default-key
EDCE7A7F8F688ADED9827AC56F8BA569180ED139 --batch --yes --no-tty
--ignore-time-conflict --ignore-valid-from --with-colons
--fixed-list-mode --with-fingerprint --status-fd 2 --attribute-file
/dev/null --primary-keyring /dev/shm/ruhciPwebapp-request.gpg
--logger-fd 17 --armor --sign --clearsign
app 8276 0.0 0.0 119576 1908 ? SL 22:53 0:00 gpg2
--homedir /var/lib/home/.secret --default-key
EDCE7A7F8F688ADED9827AC56F8BA569180ED139 --batch --yes --no-tty
--ignore-time-conflict --ignore-valid-from --with-colons
--fixed-list-mode --with-fingerprint --status-fd 2 --attribute-file
/dev/null --primary-keyring /dev/shm/ruhciPwebapp-request.gpg
--logger-fd 9 --trust-model always --recipient
05FBAC395F2C8E91B779329A34053B48028993C1 --armor --sign --encrypt -
Any suggestions are welcome.
Regards!
--
Be aware that if you reply directly to this message, your reply may not be
secure. Do not send us communications that contain unencrypted confidential
information such as passwords, account numbers, or Social Security numbers.
This message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. If you are not the intended recipient, please destroy all
copies of this message and any attachments. In addition, please notify
Gazzang immediately by email to info at gazzang.com.
More information about the Gnupg-users
mailing list