On 3/7/2011 8:51 AM, Carsten Munk wrote:In the long-term, we will
re-evaluate the direction we are taking with MeeGo
security with a new focus on *End-User Privacy*.
While we do not intend to immediately remove the security enabling
technologies we have been including in MeeGo, all security
technologies will be re-examined with this new focus in mind.We will revisit
technology choices made for MSSF (as well as non-MSSF
components that have security implications) and make appropriate changes in
these areas given this direction change.
One thought that popped into my mind: In MeeGo Smart TV there would
probably be a focus that's different from End-User privacy, with
regards to stream protection (which is a market requirements these
days, sadly?) and in IVI where there would be regulatory problems.
Does this fit well with end-user privacy goal?
Most modern SOCs and the like have a complete Hardware pipeline for the
protected content,
this is doubly true in the TV space.
(not just for DRM... for playing back two 1080p concurrently, you HAVE
to have all that stuff in hardware,
you don't want the CPU involved on a box that by and large does that
stuff 99%+ of the time. The CPU
is just there for the pretty TV guide ;-)
It's also more or less true for phone silicon; at least the parts that I
have visibility into (Intel).
There the argument is not just DRM (again) but also power efficiency;
for playing back movies,
having a hardware pipeline just makes the most sense power wise. DRM
works there almost
as an accident as well (it's of course designed in from the start.. but
even without DRM it would
mostly be the same pipeline)
To be clear, this does not mean that "tracker" is completely removed;
tracker is still being used (together with tumbler) for indexing media
on the device. At this point we are seeing serious issues
(performance/stability) with this solution, but the first attempt will be to
fix the
deficiencies rather than a replacement.
Ironically with performance, at least in terms of startup, this may be
partly caused by BMC#1, https://bugs.meego.com/show_bug.cgi?id=1 -
which starts scanning instantly at startup, probably trashing initial
performance.
we start after 2 minutes... but still.
there's a lot of impact from this currently, both in terms of just raw
CPU cycles to power impact
to stability (we're seeing quite some crashes, which worries me from a
security pov)
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
