NEW feature: Edge now Officially supports Chrome Themes in the latest Update
Microsoft Edge Version 82.0.444.0 (Official build) canary (64-bit) You need to Enable this flag: edge://flags/ Allow installation of external store themes Turn this on to allow themes from external web stores to be installed in Microsoft Edge. – Mac, Windows #edge-allow-store-extension-themesHow to view and manage your Microsoft passwords on Linux/Chrome/ChromeOS (Without Edge or mobile)
1. install Google Chrome (or other Chromium based browsers, including Edge itself) 2. install Microsoft Autofill extension 3. Sign into your Microsoft account in the extension 4. Access your Passwords safely and hassle-free * you do Not need to sign in to Google account for this. ** this works on Mac and Windows too, basically any environment where you can install this extension in. The extension also has Import feature, so you can import your passwords at once from a file and save them to your Microsoft account. Questions & answers about Microsoft Authenticator app - Azure AD | Microsoft Docs Q: How are my passwords protected by the Authenticator app? A: Authenticator app already provides a high level of security for multi-factor authentication and account management, and the same high security bar is also extended to managing your passwords. Strong authentication is needed by Authenticator app: Signing into Authenticator requires a second factor. This means that your passwords inside Authenticator app can't be accessed even if someone has your Microsoft account password. Autofill data is protected with biometrics and passcode: Before you can autofill password on an app or site, Authenticator requires biometric or device passcode. This ensures that even if someone else has access to your device, they cannot fill or see your password, as they’d be unable to provide the biometric or device PIN. Furthermore, a user cannot open the Passwords page unless they provide biometric or PIN, even if they turn off App Lock in app settings. Encrypted Passwords on the device: Passwords on device are encrypted, and encryption/decryption keys are never stored and always generated on-the-fly. Passwords are only decrypted when user wants to, that is, during autofill or when user wants to see the password, both of which require biometric or PIN. Cloud and network security: Your passwords on the cloud are encrypted and decrypted only when they reach your device. Passwords are synced over an SSL-protected HTTPS connection, which ensures no attacker can eavesdrop on sensitive data when it is being synced. We also ensure we check the sanity of data being synced over network using cryptographic hashed functions (specifically, hash-based message authentication code).[FIXED] Why Edge on Android is using super old Chromium engine?
Edge on Android is now on the latest version, the same as Edge desktop, everything is new and up to date. https://techcommunity.microsoft.com/t5/discussions/new-edge-canary-mobile-version-available-now-updated-chromium/m-p/2275690 I'm using Edge beta on Android 9. the Chromium version in it is version 77. right now the latest stable version is 80, Beta is 81 so naturally, just like Google chrome itself, Edge Beta should have Chromium 81 but in reality it is using a very old Chromium version 77. Why is that? p.s I detected the engine version using multiple websites that are made to detect browser engines in browsers.Tab Grouping Feature! Google Chrome vs Edge Insider
Please look at this quick video I took, it's from Google Chrome Canary ver 79. https://streamable.com/60m98 Elliot Kirk the tabs look stunning, the colors look vivid and it expands to the top of each tab. real nice in my opinion. I would love to see the same thing in Edge insider canary.Good News: Google is finally killing off Chrome apps, End support for NaCl, PNaCl, and PPAPI APIs
Google said Wednesday that it will begin to phase out traditional Chrome apps starting in June, and winding down slowly over two years’ time. Chrome extensions, though, will live on. This is good, because the new Chromium based Microsoft Edge isn't compatible with Chrome apps which are basically the same as Chromium extensions. so with this update, Microsoft won't be needing to add any compatibility for those apps. With this continued progress, we are expanding upon our earlier announcement and will begin phasing out support for Chrome Apps across all operating systems as follows: March 2020: Chrome Web Store will stop accepting new Chrome Apps. Developers will be able to update existing Chrome Apps through June 2022. June 2020: End support for Chrome Apps on Windows, Mac, and Linux. Customers who have Chrome Enterprise and Chrome Education Upgrade will have access to a policy to extend support through December 2020. December 2020: End support for Chrome Apps on Windows, Mac, and Linux. June 2021: End support for NaCl, PNaCl, and PPAPI APIs. June 2021: End support for Chrome Apps on Chrome OS. Customers who have Chrome Enterprise and Chrome Education Upgrade will have access to a policy to extend support through June 2022. June 2022: End support for Chrome Apps on Chrome OS for all customers. Also end of support for NaCL, PNaCL and PPAPI, are all good news for everyone. They are all Google-specific technologies. most of the stuff built upon them only require Google chrome browser. removing them also removes that restriction and makes everyone happy. Cheers everyone! SourceLet us Import browser data from Google chrome beta and canary to the new Edge
With the new options enabled in the sync: Addresses, phone numbers, and more And Passwords the Edge is getting closer to the full sync. I would like to import my saved passwords from google chrome canary to the new Edge; but it is not supported, only the stable version is supported. correct me if i'm wrong but I think the difference is only in the location where google chrome beta/canary/stable save the browser data. if that's the case then it shouldn't be hard at all to implement this. it will make life easier for a lot of people, right now if i want to do it i have to install a stable chrome first, import data and uninstall it.Microsoft advisory shows whether Edge keeps up with Chrome's patching
Microsoft advisory shows whether Edge keeps up with Chrome's patching The advisory will be updated when Microsoft releases a new version of Edge that includes publicly disclosed security updates from the Chromium project. Microsoft has posted a security advisory that will record all updates to its new Chromium-based Edge browser, giving customers a way to monitor whether the company keeps up with Google's patching of Chrome. "This advisory will be updated whenever Microsoft releases a version of Microsoft Edge which incorporates publicly disclosed security updates from the Chromium project," the Redmond, Wash. firm wrote on the support document. As of mid-day Wednesday, only one listing populated the advisory. The item, dated Jan. 17, called out four CVE-identified vulnerabilities. (CVE, for "Common Vulnerabilities and Exposures," is the most-used bug-naming standard.) The advisory also noted the Edge version number that included the patches and the corresponding version of Chromium that also quashed the bugs. Because Chrome assumes Chromium's version numbers without change - for some reason, Edge does not - the advisory was the first way that was found to link a specific version of Edge to one of Chrome. This security advisory is supposed to list all Edge security updates. Comparing the version number of Edge to that of Chrome lets customers monitor whether Microsoft has kept up with Chromium's/Chrome's fixes. Google released Chrome 79.0.3945.130 - the Chromium version listed in the advisory - on Jan. 16, saying here that the interim update included patches for 11 vulnerabilities. As usual, Google only identified four of the 11 by CVE. The quartet matched the four CVEs that Microsoft said were addressed in Edge. Meanwhile, the Edge update, which Microsoft released Jan. 17 - one day after Chrome's - was marked as version 79.0.309.68. (That's not the most current Edge; Microsoft updated the browser again on Jan. 23 to 79.0.309.71. However, there was no sign that that version patched any vulnerabilities. For a complete listing of Edge updates, users can steer to the Microsoft Update Catalog; pre-filtered the results to show only those for the Stable build of the browser.) Edge 79.0.309.68 thus equals Chrome 79.0.3945.130. Microsoft patched Edge just a day after Google refreshed Chrome, indicating that the former browser will not substantially lag behind the latter. If it had, attackers might have been able to use the interval to reverse engineer a patch, uncover the vulnerability and craft an exploit. Still unknown is the size of the gap between Google promoting a new version of Chrome to the Stable branch and Microsoft following suit with Edge. On Tuesday, Google released Chrome 80 - specifically, version 80.0.3987.87 - with new features as well as 56 security fixes. Google listed 37 of the 56 with CVE identifiers. Ten of the 37 were marked "High," the second-most-serious ranking in Chrome's four-step rating system. As of 2 p.m. ET Wednesday, Microsoft had not updated Edge to reflect the Chrome's shift to version 80. Source: Microsoft advisory shows whether Edge keeps up with Chrome's patching
