git-remote-gcrypt not working with qubes-gpg-client-wrapper (-q and --gen-rand not supported)

[whohoho]

Qubes OS version: R3.2

Steps to reproduce the behavior:

sudo apt-get install git-remote-gcrypt
git config --add gpg.program /usr/bin/qubes-gpg-client-wrapper
git remote add crypted gcrypt::[remote-url]
git pull crypted master

Relevant errors:

/usr/bin/qubes-gpg-client-wrapper --no-tty --armor --gen-rand 1 9
qubes-gpg-client: unrecognized option '--gen-rand'

/usr/bin/qubes-gpg-client-wrapper --no-tty --status-fd 3 -q -d
qubes-gpg-client: invalid option -- 'q'

more errors after fixing prev. ones in git-remote-gcrypt

• /usr/bin/qubes-gpg-client-wrapper --no-tty --with-colons --print-md SHA256
  qubes-gpg-client: unrecognized option '--print-md'

• /usr/bin/qubes-gpg-client-wrapper --no-tty --batch --no-default-keyring --secret-keyring /dev/null --keyring /dev/null --passphrase-fd 3 -d
  qubes-gpg-client: unrecognized option '--no-default-keyring'

[whohoho]

another one:
gpg --no-tty --batch --force-mdc --compress-algo none --trust-model=always --passphrase-fd 3 -c

gpg --no-tty --compress-algo none --trust-model=always -se --throw-keyids --default-recipient-self

[whohoho]

another one:
gpg --no-tty --batch --force-mdc --compress-algo none --trust-model=always --passphrase-fd 3 -c

gpg --no-tty --compress-algo none --trust-model=always -se --throw-keyids --default-recipient-self

[marmarek]

On Sat, Jan 13, 2018 at 01:11:15AM +0000, whohoho wrote: gpg --no-tty --batch --force-mdc --compress-algo none --trust-model=always --passphrase-fd 3 -c

Is this configurable to not use --passphrase-fd? --passphrase-fd does not make sense in split gpg trust model - client VM should not know any secret.

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[marmarek]

On Sat, Jan 13, 2018 at 01:11:15AM +0000, whohoho wrote: gpg --no-tty --batch --force-mdc --compress-algo none --trust-model=always --passphrase-fd 3 -c

Is this configurable to not use --passphrase-fd? --passphrase-fd does not make sense in split gpg trust model - client VM should not know any secret.

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[whohoho]

In that command symmetric encryption with a passprase is used, so it does not actually have to go to the gpg vm.

I am working on a patch now to have the local gpg do those things.

[whohoho]

In that command symmetric encryption with a passprase is used, so it does not actually have to go to the gpg vm.

I am working on a patch now to have the local gpg do those things.

[marmarek]

Ah, indeed there is -c. Currently options whitelist is not context aware, so it isn't possible to whitelist options for specific mode only. And better keep it this way for simplicity.

Handling it locally indeed may be a good idea, should be doable in gpg-client-wrapper script, or yet another wrapper.

[marmarek]

Ah, indeed there is -c. Currently options whitelist is not context aware, so it isn't possible to whitelist options for specific mode only. And better keep it this way for simplicity.

Handling it locally indeed may be a good idea, should be doable in gpg-client-wrapper script, or yet another wrapper.

[whohoho]

This is what i have now:
https://github.com/whohoho/qubes-app-linux-split-gpg/blob/master/gpg-client-wrapper

[whohoho]

This is what i have now:
https://github.com/whohoho/qubes-app-linux-split-gpg/blob/master/gpg-client-wrapper

[marmarek]

See QubesOS/qubes-app-linux-split-gpg#16

[marmarek]

See QubesOS/qubes-app-linux-split-gpg#16