From 6359f87ecdd878e6688896b1bf5388b2e42503a0 Mon Sep 17 00:00:00 2001 From: Jean-Philippe Ouellet Date: Fri, 11 Nov 2016 04:23:23 -0500 Subject: [PATCH] Fix issue link --- services/qrexec3.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/services/qrexec3.md b/services/qrexec3.md index d1aa3edb..cdc91150 100644 --- a/services/qrexec3.md +++ b/services/qrexec3.md @@ -187,9 +187,10 @@ _after_ considering the action. Sometimes just service name isn't enough to make reasonable qrexec policy. One example of such situation is [qrexec-based USB -passthrough](https://github.com/qubesos/qubes-issues/531) - using just service -name it isn't possible to express policy "allow access to device X and deny to -others". It isn't also feasible to create separate service for every device... +passthrough](https://github.com/qubesos/qubes-issues/issues/531) - using just +service name it isn't possible to express policy "allow access to device X and +deny to others". It isn't also feasible to create separate service for every +device... For this reason, starting with Qubes 3.2, it is possible to specify service argument, which will be subject to policy. Besides above example of USB