Chrome works on Windows, Mac and Linux devices. The last update from before today was Version 69 on September 4, 2018. Chrome usually updates in the background while you are doing other things, so just relaunch the browser to complete the install of the latest version.
For users who want to manually update, select "About Google Chrome" from the Help menu as seen in this picture.
When it is done updating to Version 70, refresh or relaunch browser. If you have open tabs on your Chrome when you are doing the update, you will have to refresh each open tab so the new update is applied to those sites.
If your Chrome says it is up to date AND IF it says Version 70.0.3538.67 then you are OK.
But if your Chrome says it is up to date AND IF it says any other version number, then it will go into CHECKING mode. It should update automatically unless you have a setting that blocks it from doing so.
In that case, you will have to update using the above directions. We recommend that you have your setting to automatic so that it updates on its own because you aren't going to remember to check it on a regular basis to see if there are any updates.
WHAT'S WITH ALL THE UPDATES?
Users speak - Google listens - then Google acts.
Shortly after the Version 69 release, users started to notice that their Chrome browser was unexpectedly signing into their Google accounts automatically. It contains the storehouse for your browser history, bookmarks, and passwords on Google’s servers - but only when the Sync feature is turned on. For example, users were logging into their Gmail account and were also logged into their Google account when Chrome opened. It didn't matter whether a user had accessed Gmail using Chrome or another browser, like Opera, Edge or Firefox.
Users let Google know they strongly objected because logging into a Google account also allows syncing of data, including bookmarks and passwords. Users didn't want their data going through Google's servers.
This is a big privacy issue.
Google's answer was to disable the automatic sign-in with Chrome Version 70. But it is the default, so users will have to change it if they want to allow Chrome sign-in.
To allow:
Click the 3 dots at the upper right and select "Settings" from the menu.
Click the "Advanced" button on the Settings panel.
Go to "Privacy and security" and select "Allow Chrome sign-in."
Relaunch Chrome if it doesn't automatically relaunch.
In the OFF position, users can sign into any Google service, like their Gmail and not have to sign into Chrome for their data to be seen and their preferences and history to follow them.
CHROME EXTENSIONS
Some extensions on Chrome are potential security risks because ANYONE can upload extensions in Chrome's Web Store. There's no oversee. The Store relies on users to let them know if something they downloaded was malicious or didn't work. You can check this by reading REVIEWS on each extension.
However, all developers aren't legit. Sometimes they are one shot wonders who upload One newly created extension so they can get their foot in the door for their name to be recognized on the list of developers. After their extension gets a certain number of hits, they start to upload malicious add-ons - these are not extensions, but add-ons to extensions, which essentially hijack your account to steal your money and data.
With Version 70, the Chrome Web Store is no longer allowing extensions that feature obfuscated code, with existing apps given 90 days to update. Chrome Extensions will be removed in early January 2019 if they are found to not be in compliance.
NOTICE:
We admins don't think 2 step authentication alone will deter developers from uploading malicious add-ons or extensions that don't work.
Anyone can do 2 step authentication - even you - because all it involves is sending a code to a phone number or an email address, then typing in the code to Chrome Store's permissions screen. It is similar to the process users have to do to prove they aren't a robot. Once the code appears to match, the Store approves them as authentic. This does nothing to prove the extension or add-on is legit or that it works.
If 2 step authentication is coupled with another security checkpoint, it could work.
PERMISSIONS
Previously, the permission notices on extensions allowed the extension to "automatically read and change data on websites."
Beginning with this version, Google gave users a way to limit the permissions on any extension they have already granted access to information on their account.
That means users can restrict Chrome extensions to only run on sites that they have approved. Users can make a customized list of sites that they don't want the extension to have access to or alter the way the user uses those sites. They can also require a click before the extension can run on the current page.
Options include a menu that lets users determine when the browser add-on “can read and change site data.”
Choices include 1) on the current site, and 2) “On all sites.”
To RESTRICT any previously agreed permissions, go to the add-on's icon on your extensions menu, then right click to NEW OPTIONS, and choose your restrictions.
NOTICE: This might not be available for up to a week after you install Version 70 update.
CONTROVERSY OVER SYMANTEC COMPANY
With Version 69 and all previous Chrome versions, any certificate issued by Symantec said it was SECURE and basically said each site was legit, that it wasn't fake and wouldn't steal user credentials, money or data.
With Version 70: - After Google and Mozilla (the maker of Firefox) charged Symantec and its partners with violating the rules of CA/Browser Forum (a group of browser makers and certificate authorities who decide industry standards), for improperly issuing certificates, Symantec was proven to be untrustworthy as a site and browser authority.
HTTPS means a site is secure, and is verified by Google.
HTTP means it is not secure and is not verified by Google.
Version 70 should trigger a "not secure" warning in the browser's address bar, telling the user not to trust the site. Moving forward, Google will deem any site without certificate as "not secure."
Many websites - like us - that had a Symantec-issued certificate have already removed it and contracted with a new company so their certificate shows them as "trusted."
The release of Chrome's next upgrade, version 71, is set for December 4.
Compiled from information found at Computerworld and Google Chrome Developers website
Tap the Facebook reaction button below to share with your Facebook friends
No comments:
Post a Comment