Bringing the conversation from email: On 27 June 2016 at 23:18, Tyler Hicks <tyler.hi...@canonical.com> wrote:
I've pulled in Jamie Strandboge, who may have some insights about how the audio recording policy should work. I'm not aware of the intended functionality in the situation described in the bug. I don't personally see capturing the audio output in the recording as a security vulnerability as the user is still in control of audio recording. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
