So, as the o/p I would add: jdstrand's note in #5 that we should only do this on a customer requirement is fine by me. We have a clear anti- requirement in some regulatory regions.
Specifically that we should either treat call recording as a special trust domain, and prompt/warn the user about the behaviour, or simply disable the functionality. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1591935 Title: audio record works for call audio Status in Canonical System Image: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in trust-store package in Ubuntu: Confirmed Bug description: krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350 Install the app 'Recorder' from the Ubuntu Store. Confirm it works by opening and making a recording. Note that the app requests permission to access the microphone, and you grant this with the usual trust store prompt. Now move to the phone app, and place a regular phone call. With the call active, open Recorder again, and start recording. Stop recording after some time, and hang up the call. return to the recorder app, and play the recording made during the phone call. Audio from both the local microphone and the remote handset (Which the user heard during the call) will be present on the track. It was expected that no audio from the call could be captured by applications. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp