I'd not depend on VM-not-knowing-the-sound. While it could be achieved initially, I think it will eventually leak into VM. For example when user assign a microphone to a VM.
at least the issue of data leaking via microphone could be fixed by disabling microphones during playback.
but i guess this could be impossible, since there is strange USB-hardware and detecting a microphone could be very hard.
but anyways i think allowing the user to supply a custom sound or to record a voice clip would: * add security, since detection of a [few] second[s] signal should be less error prone than detecting a signal shorter than a second. * improve usability, since voice is easier to recognize than some beep meaning "blue vm activated".
-- 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/9ab0f43b-e78d-8c9a-a370-a25cc3fd813f%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
