Comment 5 for bug 1591935

On 28 June 2016 at 16:02, Jamie Strandboge <email address hidden> wrote:

> "On Thu, 2016-06-09 at 09:05 -0400, Pat McGowan wrote:
> Seems Rex understood the plumbing, maybe there is a pulse setting to
> disable it.
>

I would very much prefer this since this is a very sensitive area and IMHO, we
should only enable voicecall recording if there is a clear customer requirement,
and even then only with proper design.

The oem bug #1569213 references the voicecall-record[1] profile as being newly enabled.
Can we simply not disable that profile? Or is Ondrej saying that because of how
we do routing, you might be able to still record without the voicecall-record
profile (I'm guessing this means it would show up in pulse as a different,
recordable profile?)? If that's the case, let's fix the routing. :)

In other words:

 * the microphone is currently mediated by pulseaudio and trust-store

 * call recording recently was added somewhere and doesn't seem to be mediated
   by trust-store on all platforms (someone should confirm)

 * if pulseaudio and trust-store properly mediated call recording then this is
   probably technically enough to satisfy mediation requirements

 * (this bug) indicates it is surprising
   that call audio is lumped in with microphone recording. I agree this is
   surprising and strongly feel we should disable call audio recording until
   there is a clear customer requirement. call audio recording was never a
   consideration by our implementation because it didn't exist at the time--
   if it is something we want, it should be properly designed (likely a 2nd
   trust-store prompt)

[1]https://github.com/mer-hybris/pulseaudio-modules-droid/blob/master/README#L114