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.
Related
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.
I wanted to create an extension for the Edge web browser, and I have a Chrome extension related to it.
Is it possible to run a Chrome extension in the Edge web browser?
Update (2016-03-19)
Not yet, but Edge decided to support the roughly the same WebExtensions model as Firefox - partial compatibility with Chrome extensions. They will be offered through Windows Store.
Edge has started rolling out experimental extension support. This is currently in Insider Preview builds and an extremely closed platform preview / closed beta. See also updated FAQs.
Some choice Twitter quotes from devs:
Jacob Rossi on porting extensions
Lots of questions on this: yes we're working on a porting tool to run Chrome extensions in Edge. Not yet finished and not all APIs supported
Jacob Rossi on Store accessibility for developers
extn's in Store will at first be a carefully selected set covering top scenarios and API coverage, opening up to more in future
Kyle Pflug on sideloading non-Store extensions
We'll allow side-loading after launch, but will require dev mode toggle & will have appropriate warnings in UI
I was searching for some solution for audio chat between two users in safari browser Using WEBRTC(Peer js). I have found some solutions using temasys plugins , but they only work for local streaming.
Is there someway in safari browser.
Yes, you can use Temasys plugin for Mac OSX safari and IE. I have used temasys successfully for these browsers on a live site though there are random issues sometimes. And now, I think peerjs supports Temasys integration also.
Things are about to change.
Apple announced support for WebRTC in Safari 11.
You can download the latest beta version of Safari 11 at the following link:
(You need to sign in with your Apple ID) https://developer.apple.com/safari/download/
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.
Could you suggest how best to test the site for Google Chrome mobile version...? I know that Opera Mobile and Mozilla Firefox are emulators for the desktop, but I have not seen this for Chrome. Maybe I'm just looking bad?
for example:
Mozilla Firefox - http://www.mozilla.org/en-US/mobile/ (fennec)
Opera - http://www.opera.com/developer/tools/mobile/
Pretty old question but in case someone else hit it in future;
Best solution i found is this;
https://developers.google.com/chrome-developer-tools/docs/remote-debugging?hl=tr
And the best part is, its working!
PS: If "adv devices" command doesn't work make sure that you have the USB driver for your phone is installed on your PC.
Google Chrome Canary can be a better replacement for this purpose. I use Chrome Canary for testing purpose.
https://developers.google.com/chrome-developer-tools/docs/mobile-emulation
It's easy to browse mobile version of nay site using browsing agent switcher, there are browser agent switcher for all browsers, more read here about browsing mobile version of site on desktop PC.