I am developing a Chrome Extension that interacts with a Native Messaging Application for Windows. The current documentation states the the Native Messaging Host can be registered in both HKLM and HKCU. The question is what versions of the Chrome Browser support registration of the Native Messaging Host in HKCU?
Of note: I saw that support for HKCU was addressed in issue #321480 (https://code.google.com/p/chromium/issues/detail?id=321480), and I also saw the code in trunk. What I can't figure out is which versions of Chrome include this new code.
First you should update your chrome to the newest version(above 34+)
You can register to HKCU and It will work
Related
As I understand, as Windows XP support was officially dropped, the newest versions of SSL certificates used in certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
I don't quite understand how the SSL certificates compatibility works, how is it possible that on Chrome and IE it requires you to switch to a new OS altogether but that's not needed when just using a different browser? Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them? What's the connection between the browser and the OS? Where do I draw the line?
OK, so looking at the example of mpql.net, we start with the SSL Labs analysis.
The problem appears to be that the server only supports elliptic curve cryptography (the various TLS_ECDHE_xxx suites) and, according to the MSDN articles Secure Sockets Layer Protocol and TLS Cipher Suites, Windows XP doesn't include any of the elliptic curve protocols. This is not related to the certificates per se, but to the way the web server is configured.
Firefox still works because it uses its own cryptographic library rather than using the SSL support built into Windows. Of course, if you were using a version of Firefox as old as Windows XP is, it probably wouldn't work either. :-)
Solution for this problem in XP is installing KB3055973-v3 that adds support for TLS 128-bit & 256-bit Advanced Encryption Standard (AES) cipher suites.
Google for this solution and beware it is natively for English OS version, otherwise you need to modify the installation files.
Note that I installed "Windows Embedded POSReady 2009" before.
certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
Chrome and IE use the CA store of windows while Firefox uses it's own independent store.
Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them?
It might be that some developer can do it, but why should somebody invest its time to support an OS which is dead and insecure just to support browsers which are no longer supported (Chrome will drop support end of 2015). If you feel this needs to be done anyway just do it. Otherwise, drop XP or at least use Firefox with it.
Although I cant say im 100% correct I believe ssl has everything to do with the browser and not much to do with the actual operating system. So I ran into an issue where the very opposite from what you are asking. A client was on a windows 7 machine and needed to access time warner business email through chrome but couldn't because of a SSL issue. The problem was that Chrome dropped support for the older version of SSL and so her options where use IE or Firefox or downgrade and hope chrome doesn't force its self to update. Microsoft is wanting users to upgrade so of course they are not going to keep IE up to date and google isn't going to support an outdated operating system. Firefox is open source so it makes sense that people would keep the browser compatible with as many devices as possible. Hope this helps.
I'm working on a Quick Meeting type app. Where I want to check whether my app is installed on the system or not.
My Application installer copies the plugin to "Internet Plugins" folder on Mac OSX and ".mozila/plugins" on Linux.
I'm using this web plugin(NPAPI) to detect whether a application is installed on the system or not.
As we know, web plugins can access using navigator.plugins.
If plugin is found in plugins array then we were deciding to launch the application using custom url handler implemented by installed app, otherwise download the installer and ask user to install the app first.
This works fine with Firefox and Safari but not with Google Chrome. Also Chromium doesn't support NPAPI plugins and Google Chrome is dropping support for it.
I thought of using Pepper Plugin, but it doesn't have any api to check installed apps nor to access local files say in users home dir.
Any idea how to do it. Any pointer on this would be helpful.
Since you are registering a custom protocol already, this boils down to detecting the presence of a protocol handler.
My application requires Chrome users to have a specific extension installed
https://chrome.google.com/webstore/detail/clickonce-for-google-chro/eeifaoomkminpbeebjdmdojbhmagnncl
Using JQuery/JavaScript, how can I determine if this extension is installed? I've seen some mentions of using chrome.management.get but I haven't found any working examples.
The reason I need the extension is ClickOnce applications won't launch in chrome unless this is installed.
I'm doing some reading on Google Chrome stand-alone applications and I see they are distributed like Chrome Extensions, and by all means, they seem work just like Chrome Extensions, so I assume they will run on the major platforms that run Chrome, like Linux, Mac and Win. But, I don't see any official word on the supported platforms, is there such a reference point?
Chrome packaged apps are available in ChromeOS, Linux, Mac and Windows. You are right, there is no explicit information about it in our online documentation, but that's unintentional.
In fact, you can already run Chrome packaged apps in all platforms mentioned above. The way they are launched - through the Chrome New Tab - is going to change and will behave more like native apps. The current launching method is for developer preview only.
i'm finding some solution to develop the Packaged App (or extension) for Chrome OS(chromium os).the extension will be access serial port to send AT command for SMS or Call function.
first, i find the NPAPI,But it not support in Chrome OS (right?) . So, maybe the PPAPI and Native Client ? if it's the key, i will look deep in them.
please give me some advice . thanks ~
NPAPI is supported by Chrome OS, but there is no way to install it, you can create Chrome extensions that uses NPAPI plugin for windows, linux, mac, but not for Chrome Os. NPAPI plugins must be preinstalled by vendor as I know, so you can't use it. If you want to use native code you need to look to Native client, but as NaCl is sandbox for native code I am not sure you will be able to access low-level hardware within it.
PPAPI only, NPAPI us NOT supported: https://sites.google.com/a/chromium.org/dev/developers/design-documents/aura-desktop-window-manager