mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-27 16:29:28 -05:00
Fix issue link
This commit is contained in:
parent
d66eda80bc
commit
6359f87ecd
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user