Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-01-16 09:47:11 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'jpouellet-issue-link'

Browse Source
This commit is contained in:
Andrew David Wong 2016-11-11 14:30:13 -08:00
commit 11d781565c
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
services/qrexec3.md
View File

@ -187,9 +187,10 @@ _after_ considering the action.
Sometimes just service name isn't enough to make reasonable qrexec policy. One Sometimes just service name isn't enough to make reasonable qrexec policy. One
example of such situation is [qrexec-based USB example of such situation is [qrexec-based USB
passthrough](https://github.com/qubesos/qubes-issues/531) - using just service passthrough](https://github.com/qubesos/qubes-issues/issues/531) - using just
name it isn't possible to express policy "allow access to device X and deny to service name it isn't possible to express policy "allow access to device X and
others". It isn't also feasible to create separate service for every device... 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 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 argument, which will be subject to policy. Besides above example of USB