Since Chrome Apps are being discontinued effective 2018, does anyone know if chrome.mdns and chrome.sockets API's are going to be made available for Chrome Extensions?
If you check this blog about the Chrome Apps, it only stated here that in early 2018, users on these platforms (Windows, Mac, and Linux) will no longer be able to load Chrome apps, but it will still be available in the CHROME OS. And it is not stated here the effect of it in the Chrome Extension.
So what can I suggest you is to check the chrome.mdns and chrome.socket for the updates on this API.
Related
I have an extension which talks to a native application. This application only works on macOS or Windows. But when I add the extension to my browser, it is also synchronized automatically to platforms where it does not make sense such as Linux or Chrome OS.
I'd figured there would be an option in the manifest.json to limit the app to specific platforms but I can't find anything like that. Am I correct? Or is there a solution?
Extensions will be installed based on chrome login. So it will be installed on all devices with chrome login.
You can programmatically enable/disable your scripts after checking for supported platform OS.
Use this API in background script to collect platform details - API Link.
Related question: Detect operating system from Google Chrome Extension
I am a bit confused... I was reading the tutorial for developing chrome extensions. But once I reach the step where to release it, I saw the developer console this message.
Does it means that my chrome extension will no longer available for chrome browser on any other OS than Chrome OS?
Chrome Apps are not Chrome extensions. The change in policy applies to Chrome Apps, not Chrome Extensions.
Your Chrome extension will be available for users of Google Chrome on all OS platforms where Chrome supports extensions (i.e. not on Android).
I'm trying to integrate U2F Authentication in GWT project and I need to know if is this solution compatible with all new web browsers (Firefox, Internet Explorer, Safari...)? Normally in Google Chrome I've to install a plugin that's called "FIDO U2F (Universal 2nd Factor) extension".
Is the same for others browsers?
Is there any way to work without a plugin for new web browser?
Do other browsers support U2F? currently not.
Is there any way to work without a plugin for a new web browser? No, that's the whole point of U2F: a phishing attack is made impossible thanks to direct communication with the browser.
Extra information
You had to install a plugin in Chrome in the past, currently (I think starting from version 40), this is not required anymore: U2F capability is built in from that version on in Chrome. As to which other browsers support U2F: currently none. Firefox supports U2F via the U2F Support Add-on, and is working on supporting U2F natively.
Microsoft reportedly will include FIDO support in Windows 10. It might be possible that browsers will rely on the OS-U2F-check then, and do not (need to) include FIDO support directly anymore. However, this is speculation only for the moment.
An easy compatibility check I'd like to carry out is to use the Yubikey's demo site.. It will be reported immediately when your browser does not support U2F (try opening the demosite in Firefox and see what happens).
Yes, it is an old thread, but let's make an update:
2016 September update : FIDO U2F browser support
Chrome for Windows, OS X and Linux: Yes (Built-in)
Chrome for Android [for FIDO U2F over NFC and over BLE devices]: Yes (You still have to download the official Google Authenticator App but this requirement will disappear in the future)
Firefox: Devs are now officially working on it. Mozilla Foundation joined the FIDO Alliance. For now, while waiting for the official built-in support, you can use this great addon: https://addons.mozilla.org/en-US/firefox/addon/u2f-support-add-on/ (It won't work on websites that do not know Firefox can be used too...)
Safari, Internet Explorer and Edge: No U2F support is even planned, but who cares anyway... :)
Just for the record: Opera Public Beta (v41) has U2F built-in support too. The next stable release should support FIDO U2F too.
Google Chrome: out-the-box since Chrome 41 (no extension required) https://support.google.com/accounts/answer/6103523?hl=en
Internet Explorer: "in development" https://dev.modern.ie/platform/status/fido20webapis/
Mozilla Firefox: popular feature request https://bugzilla.mozilla.org/show_bug.cgi?id=1065729
It isn't specifically true that browsers can't add compatibility via extensions as per Michael's post, the issue isn't that it's secure because the browser "directly communicates" - USB can be sniffed so U2F isn't secure in that sense, which is precisely why it has defences against replay attacks.
The issue relates to browsers not generally having support internally to directly talk to USB devices - or more usefully for extensions to do that (but that would throw up other unrelated security concerns). It's perfectly plausible for a piece of software to act as an intermediary for an extension and pass on authentication events to a FIDO device; I've investigated the possibility and it absolutely would work without harming the security of U2F itself - native browser support would be preferable though.
I have been finding the way to get the urls of opened tabs of the browsers of Firefox and Chrome using Accessibiltiy.
I found that Firefox can get the urls using at-spi, but Chrome can get the url of focused tab a few months ago.
I have gotten a new result recently during the test. It is that I cannot access the child of Chrome using Accessibility, so I don't even know the url of focused tab.
"atspi_accessible_get_child_count" returns 0.
But as I said earlier, it worked on Chrome 31 version.
According to Assistive technology support, there are not tools to test accessibility in Linux.
Chrome does not support Accessibility anymore?
There is the answer in Chrome Accessibility.
That says accessibility of Chromium on desktop Linux is not really supported currently.
You need to start Chrome like this:
ACCESSIBILITY_ENABLED=1 chrome --force-renderer-accessibility
Both of these are necessary. For electron apps, ACCESSIBILITY_ENABLED=1 seems to be enough, at least that was the case with VSCodium and Signal Desktop.
On Windows, this is not necessary because a11y enables itself once a known screen reader is detected (afaik), but Orca under Linux is apparently not known.
I've read about Packaged Apps and played with the example apps. I can load them into my Chrome Canary, but I can't seem to find a way to build/package a .app for OS X. Is this not possible yet, or am I just missing something?
Previously Google Chrome packaged apps were only for Google Chrome. According to a recent blog post by Sriram Saroop, the product manager for Chromium, there is an available Chrome App Launcher to run Google Chrome packaged apps outside of the browser.
The Chrome App Launcher will be coming "soon" to Mac and Linux.