> However if you known the passphrase, you can pass it to gpg directly using
> --passphrase-file and --pinentry-mode=loopback.
I figured, but am trying to avoid having the passphrase land on disk at all.
> Due to the way a pipe works there is not much you can do here.
Except (I would hope?) if
... (Windows 10) [DOS] cmd ... [*NOT* powershell]
... cygwin gpg ...
How can I 'echo' into fd 3 to be able to use it on a gpg cmd line?
e.g. 'echo "Secret data" | gpg.exe -c -passphrase-fd 3 3< echo %PASSWORD%'
[Ignore the need, or not, for --batch and/or --pinentry-mode loopback,
I can wrestle
> However if you known the passphrase, you can pass it to gpg directly using
> --passphrase-file and --pinentry-mode=loopback.
I figured, but am trying to avoid having the passphrase land on disk at all.
> Due to the way a pipe works there is not much you can do here.
Except (I would hope?) if
At https://dev.gnupg.org/T4154 , 'allow setting passphrase from an
environment variable', there is a comment of "I don't see why we
should add yet more clumsy passphrase workarounds to gpg. We already
have PINENTRY_USER_DATA which can fulfill the same task."
Can anyone give an example of doing
> Don't mix Cygwin and plain Windows programs.
cygwin has nothing to do with this thread - there is no element of
cygwin within the quoted code or results.
As said, this is pure GnuPG from
> From https://gnupg.org/download/index.html:
> Windows ...
> download sig Simple installer for the
Thank you.
I don't follow all of that, such as deep diving into
gnupg/common/sysutils.c:translate_sys2libc_fd , but I do get the
answer is: Unsupported (at least at this time).
Could you make whatever notation at dev.gnupg.org is appropriate, please?
Summary: --passphrase-fd #, where # >= 3,
Thank you.
I don't follow all of that, such as deep diving into
gnupg/common/sysutils.c:translate_sys2libc_fd , but I do get the
answer is: Unsupported (at least at this time).
Could you make whatever notation at dev.gnupg.org is appropriate, please?
Summary: --passphrase-fd #, where # >= 3,
In the mean time, you could put something along the lines of:
{CmdCalls ; } 2>&1 | grep -v -e "^gpg: problem with fast path key
listing: Forbidden - ignored$" or something, to keep that output out
of your stderr stream.
If something else unexpected displays, you'll get more issues, but
then you
=
Prologue:
Re-reading
https://web.archive.org/web/20171225062127id_/http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx?mfr=true
, I now notice '<& Reads the input from one handle and writes it to
the output of another handle.' (Read from
>From https://gnupg.org/download/index.html:
Windows ...
download sig Simple installer for the current GnuPG <--
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.4.5_20240307.exe
-
C:\Program Files (x86)\GnuPG\bin>ver
Microsoft Windows [Version 10.0.19045.4123]
C:\Program Files
On Mon, Mar 18, 2024 at 9:58 AM Werner Koch via Gnupg-users
wrote:
>
> On Sat, 16 Mar 2024 21:26, B.S. said:
> > ... (Windows 10) [DOS] cmd ... [*NOT* powershell]
> > ... cygwin gpg ...
>
> [Do not use a Cygwin build of gpg - this is not supported. Use a
> standard build for WIndows.]
Thanks
ed therein at https://dev.gnupg.org/T4154 would be useful to web
searchers.
On Mon, Apr 29, 2024 at 8:14 PM Jacob Bachmeyer
wrote:
>
> Bee via Gnupg-users wrote:
> >> Its is called "USER DATA" for a reason - you have to decide what to do
> >> with it.
> &g
> At https://dev.gnupg.org/T4154 , 'allow setting passphrase from an
environment variable', there is a comment of "I don't see why we
should add yet more clumsy passphrase workarounds to gpg. We already
have PINENTRY_USER_DATA which can fulfill the same task."
Of course, the reference here to
> Its is called "USER DATA" for a reason - you have to decide what to do
> with it.
But a novel pinentry must be created to receive the data. Again, this
is circular.
> If your really really want a passphrase, what about passing
> the filename of a file holding the passphrase.
AGAIN, this
Again, specious.
> Simply don't use a passphrase if you need to resort to such a thing. On
> many systems you - and other users - can easily look at the
> environment.
But that environment is not passed and used by pinentry - it has no
knowledge of them. PINENTRY_USER_DATA may exist, but it has
15 matches
Mail list logo
