-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Oct 03, 2020 at 11:06:37AM -0400, Chris Laprise wrote:
> Setting +x execute on the qubes-rpc/ file containing the echo statement
> resolves the "not executable" portion of the error – it now works with
> "allow" but not "ask". Setting +x was
So it has some problem processing the default_target. If I remove that
parameter, the policy rule looks like this:
$anyvm dom0 ask
The result is the dialog window now appears; I can select 'dom0' in the
dropdown and click OK, but the auth still fails.
Log:
Oct 03 11:16:02 dom0 qrexec-policy
Setting +x execute on the qubes-rpc/ file containing the echo statement
resolves the "not executable" portion of the error – it now works with
"allow" but not "ask". Setting +x was not required under R4.0.
Here is what "ask" is now showing in the log X3:
Oct 03 10:56:06 dom0 qrexec-policy-daem
On 10/1/20 11:12 AM, Marek Marczykowski-Górecki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Sep 28, 2020 at 08:12:48PM -0400, Chris Laprise wrote:
There are two separate rpc configurations I tried recently which failed to
work:
1. The 'vm-sudo' doc instructions for a sudo do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Sep 28, 2020 at 08:12:48PM -0400, Chris Laprise wrote:
> There are two separate rpc configurations I tried recently which failed to
> work:
>
> 1. The 'vm-sudo' doc instructions for a sudo dom0 prompt. The domU appears
> to retry in rapid su
There are two separate rpc configurations I tried recently which failed
to work:
1. The 'vm-sudo' doc instructions for a sudo dom0 prompt. The domU
appears to retry in rapid succession 3 times but no prompt appears. I
tried switching the rpc rule from 'ask' to 'allow' but no dice.
2. The man
