Comment 3 for bug 1238298

Iftikhar,

I followed up with Saviq on the screen unlock:
Oct 14 15:57:45 <fginther> Saviq, what about unlocking the screen, does tha
t even apply?
Oct 14 15:57:58 <Saviq> fginther, for unity8 it does not
Oct 14 15:58:05 <Saviq> fginther, I mean for the unity8 suite
Oct 14 15:58:24 <fginther> Saviq, thanks, (and I was referring to unity8-au
topilot as well)
Oct 14 15:58:27 <Saviq> fginther, and even for apps you shouldn't need that temp
orarily
Oct 14 15:58:40 <Saviq> as we'll unlock when an app is launched behind the greet
er
Oct 14 15:59:00 <fginther> Saviq, yeah!
Oct 14 15:59:04 <Saviq> but we'll be locking this down at some point soon to plu
g that security hole ;)
Oct 14 15:59:16 <fginther> oh well
Oct 14 15:59:31 <Saviq> fginther, but at that point we should have all apps transitioned to unity8
Oct 14 15:59:36 <Saviq> s/unity8/upstart/
Oct 14 15:59:56 <Saviq> and then in the suite you'd restart unity8 under testability
Oct 14 16:00:04 <Saviq> and use unity8's emulator to unlock
Oct 14 16:00:11 <Saviq> so no more blindness

So, this feature appears to be short lived, but ultimately replaced by the apps unlocking the device within the test. Once this is all in place, we can then throw away the unlock code.