Closed Bug 981905 Opened 7 years ago Closed 7 years ago
Cisco Jabber Guest - request to whitelist plugin
<<Please supply the following information for new plugin whitelist requests>> Plugin name: Cisco Jabber Guest Plug-in Vendor: Cisco Systems, Inc. Point of contact: Michael McCann Current version: 10.0 Download URL: https://jabberguest.cisco.com/call/chip.msi for windows https://jabberguest.cisco.com/call/chip.dmg for mac Sample URL of plugin in use: https://jabberguest.cisco.com/call/[anynumber] Plugin details: See attached ppt <<For each affected operating system, please copy the plugin information from about:plugins in Firefox>> Are there any variations in the plugin file name, MIME types, description, or version from one release to the next? Yes, version number is updated. The version number is part of the file name and description so those are updated as well. Are there any known security issues in current or older versions of the plugin? No. HTML Transition Plan: Our plan to move away from NPAPI is to install the plugin code natively, and use js-ctypes to communicate between the application and the native code. We are also investigating the feasibility of using WebRTC (which is contingent on incorporation of OpenH264 into the browser).
Can you paste the about:plugins data (win/mac) directly into a bug comment? I don't have access to powerpoint.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: need about:plugins data
****Windows 7**** Cisco Jabber Guest Plug-in File: npchip.dll Path: C:\Users\admin\AppData\Roaming\Cisco Systems, Inc\chip\10.0.1.17\npchip.dll Version: 10.0.1.17 State: Enabled Cisco Jabber Guest Plug-in - version 10.0.1.17 - f741143f59da4e88d13743bae7df432569c78204 03/13/2014 14:27:44 MIME Type Description Suffixes application/x-chip Cisco Jabber Guest Plug-in ****Mac 10.7**** Cisco Jabber Guest Plug-in File: Cisco Jabber Guest Plug-in.10.0.1.11.plugin Path: /Users/ramerman/Library/Internet Plug-Ins/Cisco Jabber Guest Plug-in.10.0.1.11.plugin Version: 10.0.1.11 State: Enabled Cisco Jabber Guest Plug-in - version 10.0.1.11 - 976e408128ddb1c11f4ee25e26dee6177d36ebd0 02/26/2014 19:17:14 MIME Type Description Suffixes application/x-chip Cisco Jabber Guest Plug-in - version 10.0.1.11 - 976e408128ddb1c11f4ee25e26dee6177d36ebd0 02/26/2014 19:17:14
Whiteboard: need about:plugins data → application complete
Whiteboard: application complete → application complete - accepted
Builds for testing are now available at http://people.mozilla.org/~bsmedberg/plugin-whitelisting-91f6f3380041/ Please do a QA pass using a new Firefox profile to ensure that the plugin activates without a popup and appears as "Always Activate" in the addon manager. Report back in this bug when QA is complete. Please try to complete QA by the end of this week.
Tested on Mac OX 10.9 and Windows 7. Tests passed on both.
Whiteboard: application complete - accepted → application complete - accepted - qa complete
Fixed for Firefox 30 beta in bug 992995.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
I have a question about this bug. I noticed that it is resolved in Firefox 30, so I updated to v30 on beta channel. At first I did not use a new profile – what I observed is that the Cisco Jabber Guest Plug-in is set to **Ask to Activate**. It did not prompt me with a pop up, however. I did the same test with a new profile, and saw behavior I expected - Cisco Jabber Guest Plug-in is set to **Always Activate**, and it did not prompt me with a pop up. So this leads me to two questions: 1) Under what conditions would the user get a pop-up prompting them to activate the plugin? I would have expected to have seen a pop-up in my first test when plugin was set to Ask to Activate. 2) What is the expected behavior in the scenario where the user already has the plugin installed, and updates to Firefox 30 (and does not use a new profile)?
(In reply to mrmccann from comment #6) > 1) Under what conditions would the user get a pop-up prompting them to > activate the plugin? I would have expected to have seen a pop-up in my > first test when plugin was set to Ask to Activate. From the description i think you: * set the plugin to "ask to activate" yourself, hence the setting is remembered * you previously chose "allow and remember" for your plugin on the site that you tested on You can try to remove the permissions to see if it behaves as expected afterwards: http://benjamin.smedbergs.us/tests/ctptests/#clear-permissions > 2) What is the expected behavior in the scenario where the user already has > the plugin installed, and updates to Firefox 30 (and does not use a new > profile)? It should always activate, unless the user has set it to "ask to activate"/"disabled" or blocked it on a specific site before.
You need to log in before you can comment on or make changes to this bug.