Le vendredi 12 décembre 2014 à 02:52 +0000, Wang, Peter H a écrit : > Hi all, > > I have a question about Cynara or Tizen security mechanism. > > Currently, Crosswalk of Tizen has implemented its WebAPI > “requestFullscreen” based on the “SetFullScreen” function of Tizen > native window. > Assuming Crosswalk is “untrusted”, means, some malicious App can > workaround Crosswalk’s permission check to invoke this function > eventually, will the system security block this invoking if the app > have not right permission label?
Hello Peter, That is an interesting issue that you are raising here. First, it the "supplementary" privilege for full screen actually exists in Tizen 2.3 specs [1]. Second, let think about hybrid apps within the crosswalk 2 processes model later proposal. Then, crosswalk is linked with ... say ozone-wayland or ozone-x11 (or ozone-efl if it existed) that it relies on to have fullscreen behaviour. So even if the crosswalk implementation of APIs checks the privilege using cynara before calling the ozone behaviour, you are pointing out the issue that an hybrid app could call ozone directly without checking cynara. Then the answer is that this scenario is realist, it can occur and it is a hole in security. But we are looking at implementing security inside weston (for ozone-wayland). There was a presentation in Bordeaux that Manuel saw but also available here [2], [3] & [4]. I'm quiet sure that EFL will be cynara ready so would reamain the case of a malicious client calling X11 directly. Cheers José Bollo [1] https://developer.tizen.org/fr/documentation/dev-guide/2.3.0?redirect=https%3A//developer.tizen.org/dev-guide/2.3.0/org.tizen.mobile.native.apireference/index.html [2] http://www.x.org/wiki/Events/XDC2014/XDC2014DodierPeresSecurity/ [3] http://www.phoronix.com/scan.php?page=news_item&px=MTYxMDA [4] https://github.com/mupuf/libwsm _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
