Stop popup which asks for the passphrase

[Peter Lebbing]

I'm reposting a question[1] asked by Shweta Tyagi in a different thread,
so it is in its own thread. I feel Shweta might have chosen to seek
their answer elsewhere after they only got unhelpful responses there,
and I'd like to rectify that.

Shweta asked:

Hi All,

I am using the following command

gpg --batch --passphrase-fd n and it stops popup which asks for the
passphrase. but when I run this command on window server 12 it's not
working its always show popup for the passphrase. can someone please
help me how can I stop popup on window server 12.

[1] https://lists.gnupg.org/pipermail/gnupg-users/2019-March/061789.html

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Stop popup which asks for the passphrase

[Peter Lebbing]

Hello Shweta,

> gpg --batch --passphrase-fd n and it stops popup which asks for the
> passphrase. but when I run this command on window server 12 it's not
> working its always show popup for the passphrase.

It is not clear to me which versions of GnuPG you are using. Using a
recent version, but on Linux, I cannot reproduce that this command
works, so I agree with Windows there.

What works for me is:

$ gpg --batch --pinentry-mode loopback --passphrase-fd n [...]

(obviously filling in a number for n, and continuing with more options
and a command for gpg).

With older versions of gpg-agent, it might be necessary to specify the
following in ~/.gnupg/gpg-agent.conf (rather, its location on your OS of
choice):

allow-loopback-pinentry

but this is the default now.

As a full working example, this works for me:

$ echo Hi | gpg --batch -o test.gpg -u 1819B624D400781C8988105EC97A5BCE0BFBF628 
--passphrase-fd 3 --pinentry-mode loopback -s 3<



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Please start a new thread

[Peter Lebbing]

Hello Shweta,

Seeing how you did not start a new thread, I get the feeling we "scared
you off" from posting. That is really unfortunate, and not our intention
at all. I'm sorry if you felt intimidated by the response you got.

It's rather unusual, but I took the liberty of posting your question to
the mailing list again, but now not by replying to an existing mailing
list post but addressing a mail to . And
subsequently answering the question to the extent I could.

Let me conclude by copying the part of the list information page[1] that
pertains to basic rules of conduct. The rules are there to make
communication easier; for instance, if you don't trim your quotes it
becomes an effort just to read the flow of the conversation. People who
might otherwise have insightful stuff to add might have given up
reading. And if someone searches the list archive to find if someone
else was already helped with the same problem they're having, it should
be possible to quickly navigate through large amounts of conversation.
That is also why it's important to have one thread deal with one subject
only (or a set of closely related subjects at least :-).

> The topic of this is list is help and discussion among users of GnuPG.
> This includes questions on how to script GnuPG, how to create or sign
> keys and general discussion on encryption and digital signatures as
> long as it somehow pertains to GnuPG. 
>
> The contents of all messages sent to this mailing list is assumed to
> be in the public domain but posted code snippets or patches are under
> their respective license. Do not post any material which may not be
> published. Take care before posting; retracting a post is in general
> not possible. Please write only in English, *avoid* *top* *posting*
> *and* *strip* *quotes* to the necessary minimum. 
>
> Some kinds of postings will not be accepted: e.g. large ones, mails
> without the list name in the To: or CC: header and HTML mails. Your
> mail client does have an option to send plain text only messages; try
> this if you don't get your posting through or notice it in the
> archive.

HTH,

Peter.

[1] https://lists.gnupg.org/mailman/listinfo/gnupg-users

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

答复: Two questions about system entropy and update

[Shaoping Xie via Gnupg-users]

I have tried many suggestions on the internet and none worked.

I have finally generated the key pair on another system and then 
exported/imported the keys.

I hope that my experience may save some time and effort of other fellows.

Regards，
Shaoping


发送自 Windows 10 版邮件应用

发件人: Shaoping Xie
发送时间: 2019年3月31日 8:43
收件人: gnupg-users@gnupg.org
主题: Two questions about system entropy and update 

Good Morning ,

  I have been tried to generate a key pair and gotten the error :
  
  Not enough random bytes available.  Please do some other work to give
  the OS a chance to collect more entropy! (Need 300 more bytes)
  
  It seems that the error is very common by googling the internet . However, 
none of recommendations has worked and helped . 
  I am using Solaris 10 X86 system . I had generated the key pair without any 
problem before . Can some experts explain why I have suddenly had this problem 
? Does it help if I remove the old key pair ?
  (I had tried to run the key generation while running iostat, mpstat and using 
find in other windows. Is there any way I may view the system entropy in 
Solaris system ?)
  
  My GPG is pretty old :
  gpg (GnuPG) 1.4.10; Copyright (C) 2008 Free Software Foundation, Inc.
  How can I update GPG ? I have the file transfers with dozens of clients, 
which are essential for business . The update cannot affect the current 
public/private keys . Is it safe to upgrade on the current system or I have to 
build a new system ?
  Can the new version solve the problem with system entropy ?
  
  Thank you,
  Shaoping 
  


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users