On Friday, October 31, 2014 12:33:13 AM Hauke Laging wrote:
gpg-connect-agent GET_PASSPHRASE --data --no-ask
4F7E9F723D197D667842AE115F048E6F0E4B4494 t1 t2 t3 /bye
D fubar
OK
It prints the GPG passphrase in plain text. Is the password cached in plain
text?
--
Regards,
Sudhir Khanger,
On Fri, 31 Oct 2014 06:51, m...@sudhirkhanger.com said:
It prints the GPG passphrase in plain text. Is the password cached in plain
text?
Catch-22. How would you protect the key used to decrypt the cache?
Actually the content of the passphrase cache is stored encrypted in RAM
but the key for
On 2014-10-29, Werner Koch wrote:
The only changes for gpgsm since beta834 are related to the key
storage. Without any log output I can't help very much. Please
check that the correct gpg-agent is used and not some older
version - has it been started and is still running after the test
On Fri, Oct 3, 2014 at 4:35 PM, Werner Koch w...@gnupg.org wrote:
Hello!
I just released another *beta* version of GnuPG *2.1*. It has been
released to give you the opportunity to check out new features and to
help fixing bugs.
Hi all,
I had a few minor issues/questions with GnuPG 2.1
On Fri, 31 Oct 2014 12:19, lech...@wi.uni-muenster.de said:
Indeed, I’ve got an older gpg-agent running as well.
Don't do that.
For card access I’m using gnupg-pkcs11-scd.
Well, scdaemon is part of GnuPG. If you replace it with something else
it might quite well happen that the systems
Robert,
On Wednesday 29 October 2014 at 19:00:39, Robert J. Hansen wrote:
Because this gets asked quite often, I've started to capture
some arguments of the debate how long RSAs could/should/can be
at http://wiki.gnupg.org/LargeKeys
I thought we largely addressed this in the FAQ, sections
On Wednesday 29 October 2014 at 22:29:07, Florin Andrei wrote:
Ideally, I would run a script, have the user type in the new PIN, and
the script would run gpg --change-pin, do another thing with the PIN
string after that, then discard it.
The problem, of course, is that pinentry is launched.
yes, I think that the recurring debate demands that the arguments
are made visible so they can be tested by readers.
The FAQ is discussed in public and changes are submitted to the
community for comment and review before I make any changes. So far, no
one on the list has raised a serious
On 10/31/2014 01:31 PM, SubramaniaRao, ravikumar wrote:
Hello GNUPG Users,
Help needed to setup Passphrase with GNUPG 2.0.26.
We have installed the following.
(a) libgpg-error-1.11
(b) libgcrypt-1.4.0
(c) libassuan-2.1.2
(d) libksba-1.3.1
(e) pth-2.0.7
(f)
Anyway, gpg might want to use pinentry to gather the passphrase from the
user, and it's not clear that you have the right environment set up for
pinentry.
One option would be to install GnuPG 1.4 on the host machine -- headless
servers are some of the few uses I can still see for it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/31/14 2:28 PM, Robert J. Hansen wrote:
| Anyway, gpg might want to use pinentry to gather the passphrase
| from the user, and it's not clear that you have the right
| environment set up for pinentry.
|
| One option would be to install GnuPG
11 matches
Mail list logo
