Skip to main content
Legend
April 12, 2016
Answered

Is there a security consideration for Chrome debugger?

  • April 12, 2016
  • 1 reply
  • 542 views

Hi,

I am being driven demented by attempts to get a working debug environment.

I have working Firefox with debugger plugin, but that has its own network blocking issues that currently block a specified type of content silently. This fails only on Firefox and I desperately need a working example in another browser debugger to compare against.

I have Chrome debugger plugin... but I can only get this working sporadically and, crucially, _not_ on the network where I am working today.

However, because I _have_ seen working Chrome debug... is it possible that Chrome / the plugin / my OS is blocking access to debugger when on public networks?

EG:

1. Chrome is coming installed with 213

2. I have installed debugger 216

3. My plugin in Chrome reports itself as 216

4. I _still_ cannot debug using 216...

Can anybody point me to something I need to enable / disable to allow debugging via Chrome on a public network?

G

This topic has been closed for replies.
Correct answer _maria_

Hi,

Chrome only detects the non-content debugger Flash Player version by default.  To use the debugger you'll need to launch Chrome from the command-line (or terminal) using switch commands to tell Chrome where to find the content debugger and the content debugger version:

  • Launch the command-prompt or Terminal app:
    • On Windows, select Start > Run > type cmd.exe and press Enter to launch the command-window
    • On OS X, launch Finder and navigate to /Library/Utiltities/Terminal.app > open Terminal.app
  • Launch Chrome from the terminal with the --ppapi-flash-path and --ppapi-flash-version switches in the following syntax:

<Location to Chrome> --ppapi-flash-path=<location to Flash Player PPAPI> --ppapi-flash-version=<PPAPI Version number>

    • Examples:
      • Windows 32-bit OS: C:\Program Files\Google\Chrome\Application\chrome.exe --ppapi-flash-path=C:\Windows\System32\Macromed\Flash\pepflashplayer32_21_0_0_197.dll --ppapi-flash-version=21.0.0.197
      • Windows 64-bit OS (32-bit Chrome): "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ppapi-flash-path=C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_21_0_0_197.dll --ppapi-flash-version=21.0.0.197
      • OS X: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer --ppapi-flash-version=21.0.0.197
  • To verify Chrome is using the expected version, navigate to https://helpx.adobe.com/flash-player.html and click the Check Now button.  The resulting System Information will indicate the Flash Player version in use and should be the one used in the previous step.
    • The system information widget does detect if the content debugger is installed and will show this in the results.  If you don't see this distinction, then Chrome is not using the Flash Player content debugger version in the --ppapi-flash-path and/or --ppapi-flash-version.  Please ensure the paths to Chrome and Flash Player are correct and the version specified is correct.


--

Maria

1 reply

_maria_
_maria_Correct answer
Legend
April 12, 2016

Hi,

Chrome only detects the non-content debugger Flash Player version by default.  To use the debugger you'll need to launch Chrome from the command-line (or terminal) using switch commands to tell Chrome where to find the content debugger and the content debugger version:

  • Launch the command-prompt or Terminal app:
    • On Windows, select Start > Run > type cmd.exe and press Enter to launch the command-window
    • On OS X, launch Finder and navigate to /Library/Utiltities/Terminal.app > open Terminal.app
  • Launch Chrome from the terminal with the --ppapi-flash-path and --ppapi-flash-version switches in the following syntax:

<Location to Chrome> --ppapi-flash-path=<location to Flash Player PPAPI> --ppapi-flash-version=<PPAPI Version number>

    • Examples:
      • Windows 32-bit OS: C:\Program Files\Google\Chrome\Application\chrome.exe --ppapi-flash-path=C:\Windows\System32\Macromed\Flash\pepflashplayer32_21_0_0_197.dll --ppapi-flash-version=21.0.0.197
      • Windows 64-bit OS (32-bit Chrome): "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ppapi-flash-path=C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_21_0_0_197.dll --ppapi-flash-version=21.0.0.197
      • OS X: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer --ppapi-flash-version=21.0.0.197
  • To verify Chrome is using the expected version, navigate to https://helpx.adobe.com/flash-player.html and click the Check Now button.  The resulting System Information will indicate the Flash Player version in use and should be the one used in the previous step.
    • The system information widget does detect if the content debugger is installed and will show this in the results.  If you don't see this distinction, then Chrome is not using the Flash Player content debugger version in the --ppapi-flash-path and/or --ppapi-flash-version.  Please ensure the paths to Chrome and Flash Player are correct and the version specified is correct.


--

Maria

Legend
April 13, 2016

Ouch.

Ok, so if I use a wrong path, Chrome tells me it cannot load.

If I use a correct path, it ignores me...

I had it wrong yesterday. Chrome is on 216 but debugger is on 213. I think Chrome may be defaulting to the highest one it finds or something equally irritating.

Ho hum. At least I can debug in _Opera_.

Legend
April 13, 2016

YES!

I found I had 216 in my user directory, so I deleted it.

I now have a debuggable SWF in Chrome!

Fantastic! This is almost as good as... um... a year or two ago...