On Wednesday, April 11, 2018 at 1:42:57 AM UTC-4, berto0...@gmail.com wrote:
> I also had to change
>
> $type:TemplateVM $default allow,target=sys-whonix
>
> to
>
>
> $type:TemplateVM $default allow,target=sys-net
>
> to make the Qubes repo work in Fedora (Template and AppVMs). All other
On Wednesday, April 11, 2018 at 12:42:57 PM UTC+7, berto0...@gmail.com wrote:
> I also had to change
>
> $type:TemplateVM $default allow,target=sys-whonix
>
> to
>
>
> $type:TemplateVM $default allow,target=sys-net
>
> to make the Qubes repo work in Fedora (Template and AppVMs). All other
I also had to change
$type:TemplateVM $default allow,target=sys-whonix
to
$type:TemplateVM $default allow,target=sys-net
to make the Qubes repo work in Fedora (Template and AppVMs). All other repos
and the Qubes Repo in the Debian template worked as expected.
There is some kind of bug or
glad I could help! I just went through this last week.
Even though I changed the settings in qubes manager to
point to custom-sys-net, my RPC policy still said sys-net:
<
# Default rule for all TemplateVMs - direct the connection to sys-net
$type:TemplateVM $default allow,target=sys-net
/>
I
Am Freitag, 9. März 2018 08:53:41 UTC+1 schrieb sevas:
> I deleted my original sys-net and sys-fw and I received similar errors. What
> I did to fix it was
>
> dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy
>
> and fixed the command which was pointing to the wrong sys-net.
Thanks a
On Friday, March 9, 2018 at 2:53:41 AM UTC-5, sevas wrote:
> I deleted my original sys-net and sys-fw and I received similar errors. What
> I did to fix it was
>
> dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy
>
> and fixed the command which was pointing to the wrong sys-net.
I deleted my original sys-net and sys-fw and I received similar errors. What I
did to fix it was
dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy
and fixed the command which was pointing to the wrong sys-net.
--
You received this message because you are subscribed to the Google
