On Sat, Dec 24, 2016 at 8:58 AM, Vít Šesták <[email protected]> wrote: > 2. There should be some exception for notifications. That is, dom0 would be > able to play some predefined sound(s) that inform the user that there is > something new.
But how could we prevent a domU from just playing the notification sound and contents? I can think of two ways: 1) Filter out some "trusted sounds" from domUs. 2) Have some kind of input event following which sound may only come from dom0. For example an "identify domain" shortcut, which would stop all domU audio and say the name of the domain of the focused window. #1 seems to me like a very fragile idea doomed to fail, and #2 requires being triggered by the user and not dom0. This raises a problem that notifications are likely to be caused by events not triggered by user input. So perhaps some untrusted "event pending" sound should be played to indicate that a user should press the trusted "tell me next event" key? -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_C4ZB-6717Q_nexrypL%2BqGBeUyud_VagGSJuGmd1uTtAA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
