Signing message problem with GPG loopback pin-entry option

[Alireza Sadeghpour]

Thanks for your response,

Actually i need to use two keys, one  for aes encryption and another one is
used for rsa signing, which both of them are protected with a passphrase.

I tried to indicate rsa key passphrase with --passphrase option and aes key
with --passphrase-file option.

If that is wrong, how can i indicate passphrase for two separate keys in
same command?

Sencerly

On Sun, 20 Feb 2022, 7:37 PM Ingo Klöcker, <kloecker at kde.org> wrote:

> On Sonntag, 20. Februar 2022 16:25:31 CET Alireza Sadeghpour via
> Gnupg-users
> wrote:
> > I am trying to encrypt and sign a file with gpg and loopback pinentry
> > option, with the below command:
> >
> > gpg --pinentry-mode=loopback --passphrase ="mypws" \
> > --ignore-time-conflict --ignore-valid-from \
> > --cipher-algo AES256 --symmetric --ignore-time-conflict \
> > --passphrase-file ~/.gnupg/PG/p-enckey --trust-model always -q --batch
> > --yes --local-user "UserID" \
> > --sign --force-mdc \
> > --output /var/psigner/2 \
> > /var/psigner/1
>
> Using the options --passphrase *and* --passphrase-file makes no sense.
>
> > however i got the below error message:
> >
> > gpg: signing failed: Too much data for IPC layer
> > gpg: /var/psigner/1: sign+symmetric failed: Too much data for IPC layer
>
> Could it be that the file ~/.gnupg/PG/p-enckey contains more data than gpg
> allows/supports for a passphrase?
>
> > Can anyone give me advice to solve the problem?
>
> Removing `--passphrase-file ~/.gnupg/PG/p-enckey` from the command line
> could
> solve your problem.
>
> Regards,
> Ingo
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20220220/abf822ba/attachment.html>