Hook up PpapiPermissions in more places.

ppapi/proxy/ppb_flash_proxy.cc

Index: ppapi/proxy/ppb_flash_proxy.cc
diff --git a/ppapi/proxy/ppb_flash_proxy.cc b/ppapi/proxy/ppb_flash_proxy.cc
index a8767f7b0d7737f5f9d9a42e68eb2c5230293c15..c45318cc319395a7cbf9a9198d1e0b1ff819f93e 100644
--- a/ppapi/proxy/ppb_flash_proxy.cc
+++ b/ppapi/proxy/ppb_flash_proxy.cc
@@ -88,6 +88,9 @@ const PPB_Flash_Print_1_0* PPB_Flash_Proxy::GetFlashPrintInterface() {
 }
 
 bool PPB_Flash_Proxy::OnMessageReceived(const IPC::Message& msg) {
+  if (!dispatcher()->permissions().HasPermission(PERMISSION_FLASH))
+    return false;

[bbudge, 2012/10/01 17:32:01]

I'm wondering if there is any reason to expose the dispatcher's permissions
directly. Would it be better if the dispatcher instead had a HasPermission()
method?

[brettw, 2012/10/01 23:04:48]

That would work and would be fine with just this one function. I was worried
about having potentially more functions and doing a bunch of plumbing. This
seemed a bit cleaner (a dispatcher has permissions, and you use the permissions
API to access it).

+
   // Prevent the dispatcher from going away during a call to Navigate.
   // This must happen OUTSIDE of OnMsgNavigate since the handling code use
   // the dispatcher upon return of the function (sending the reply message).