Google Chrome 64 is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier. Google Chrome comes with a full range of competitive features, and is among the most standards-compliant and fastest browsers available. Chrome's minimalist interface, fast page-load times, and support for extensions make the browser appealing to the average user as well as to Google fanatics.
• Sandboxing. Every tab in Chrome is sandboxed, so that a tab can display contents of a web page and accept user input, but it will not be able to read the user’s desktop or personal files.
Google say they have “taken the existing process boundary and made it into a jail”. There is an exception to this rule; browser plugins such as Adobe Flash Player do not run within the boundaries of the tab jail, and so users will still be vulnerable to cross-browser exploits based on plugins, until plugins have been updated to work with the new Chrome security. Google has also developed a new phishing blacklist, which will be built into Chrome, as well as made available via a separate public API.
• Privacy. Google announces a so-called incognito mode claiming that it “lets you browse the web in complete privacy because it doesn’t record any of your activity”. No features of this, and no implications of the default mode with respect to Google’s database are given.
• Speed. Speed improvements are a primary design goal.
Stability
• Multiprocessing. The Gears team were considering a multithreaded browser (noting that a problem with existing web browser implementations was that they are inherently single-threaded) and Chrome implemented this concept with a multiprocessing architecture. A separate process is allocated to each task (eg tabs, plugins), as is the case with modern operating systems. This prevents tasks from interfering with each other which is good for both security and stability; an attacker successfully gaining access to one application does not give them access to all and failure in one application results in a “Sad Tab” screen of death. This strategy exacts a fixed per-process cost up front but results in less memory bloat overall as fragmentation is confined to each process and no longer results in further memory allocations. To complement this, Chrome will also feature a process manager which will allow the user to see how much memory and CPU each tab is using, as well as kill unresponsive tabs.
User interface
• Features. Chrome has added some commonly used plugin-specific features of other browsers into the default package, such as an Incognito tab mode, where no logs of the user activity are stored, and all cookies from the session are discarded. As a part of Chrome’s javascript virtual machine, pop-up javascript windows will not be shown by default, and will instead appear as a small bar at the bottom of the interface until the user wishes to display or hide the window. Chrome will include support for web applications running alongside other local applications on the computer. Tabs can be put in a web-app mode, where the omnibar and controls will be hidden with the goal of allowing the user to use the web-app without the browser “in the way”.
• Rendering Engine. Chrome uses the WebKit rendering engine on advice from the Gears team because it is simple, memory efficient, useful on embedded devices and easy to learn for new developers.
• Tabs. While all of the major tabbed web browsers (e.g. Internet Explorer, Firefox) have been designed with the window as the primary container, Chrome will put tabs first (similar to Opera). The most immediate way this will show is in the user interface: tabs will be at the top of the window, instead of below the controls, as in the other major tabbed browsers. In Chrome, each tab will be an individual process, and each will have its own browser controls and address bar (dubbed omnibox), a design that adds stability to the browser. If one tab fails only one process dies; the browser can still be used as normal with the exception of the dead tab. Chrome will also implement a New Tab Page which shows the nine most visited pages in thumbnails, along with the most searched on sites, most recently bookmarked sites, and most recently closed tabs, upon opening a new tab, similar to Opera’s “Speed Dial” page.
What's New On Google Chrome 64 FINAL ?
Google chrome 64 has garnered a lot of fame with many internet users since its launch in 2008. It has so far received a considerable share in global use among the internet browsers. The product upholds a Google sense of innovation, creativity and provides a simple to use, faster browsing for the user. The latest version comes with tabbed browsing, synchronization and privacy functions. One can synchronize bookmarks, extensions, browser preference to ease access regardless of the computer in use. With the capability of tabbed browsing, one can duplicate tabs, drag and rearrange the tabs in the browser window. The tabs function singularly hence; in case one of them has a problem, the rest is unaffected. Embedding tabs is available in Google chrome hence a new tab originating from the parent will be next not at the end of the tabs list. Some of the factors that make the browser one of the best include security, compatibility, speed and ease of use.
Speed
- Chrome is designed to be fast in every possible way: It's quick to start up from your desktop, loads web pages in a snap, and runs complex web applications fast .
Simplicity
- Chrome's browser window is streamlined, clean and simple.Chrome also includes features that are designed for efficiency and ease of use. For example, you can search and navigate from the same box, and arrange tabs however you wish quickly and easily.
Security
- Chrome is designed to keep you safer and more secure on the web with built-in malware and phishing protection, autoupdates to make sure the browser is up-to-date with the latest security updates, and more.
And more features
- Chrome has many useful features built in, including extensions, translation in the browser, themes, and more.
• Sandboxing. Every tab in Chrome is sandboxed, so that a tab can display contents of a web page and accept user input, but it will not be able to read the user’s desktop or personal files.
Google say they have “taken the existing process boundary and made it into a jail”. There is an exception to this rule; browser plugins such as Adobe Flash Player do not run within the boundaries of the tab jail, and so users will still be vulnerable to cross-browser exploits based on plugins, until plugins have been updated to work with the new Chrome security. Google has also developed a new phishing blacklist, which will be built into Chrome, as well as made available via a separate public API.
• Privacy. Google announces a so-called incognito mode claiming that it “lets you browse the web in complete privacy because it doesn’t record any of your activity”. No features of this, and no implications of the default mode with respect to Google’s database are given.
• Speed. Speed improvements are a primary design goal.
Stability
• Multiprocessing. The Gears team were considering a multithreaded browser (noting that a problem with existing web browser implementations was that they are inherently single-threaded) and Chrome implemented this concept with a multiprocessing architecture. A separate process is allocated to each task (eg tabs, plugins), as is the case with modern operating systems. This prevents tasks from interfering with each other which is good for both security and stability; an attacker successfully gaining access to one application does not give them access to all and failure in one application results in a “Sad Tab” screen of death. This strategy exacts a fixed per-process cost up front but results in less memory bloat overall as fragmentation is confined to each process and no longer results in further memory allocations. To complement this, Chrome will also feature a process manager which will allow the user to see how much memory and CPU each tab is using, as well as kill unresponsive tabs.
User interface
• Features. Chrome has added some commonly used plugin-specific features of other browsers into the default package, such as an Incognito tab mode, where no logs of the user activity are stored, and all cookies from the session are discarded. As a part of Chrome’s javascript virtual machine, pop-up javascript windows will not be shown by default, and will instead appear as a small bar at the bottom of the interface until the user wishes to display or hide the window. Chrome will include support for web applications running alongside other local applications on the computer. Tabs can be put in a web-app mode, where the omnibar and controls will be hidden with the goal of allowing the user to use the web-app without the browser “in the way”.
• Rendering Engine. Chrome uses the WebKit rendering engine on advice from the Gears team because it is simple, memory efficient, useful on embedded devices and easy to learn for new developers.
• Tabs. While all of the major tabbed web browsers (e.g. Internet Explorer, Firefox) have been designed with the window as the primary container, Chrome will put tabs first (similar to Opera). The most immediate way this will show is in the user interface: tabs will be at the top of the window, instead of below the controls, as in the other major tabbed browsers. In Chrome, each tab will be an individual process, and each will have its own browser controls and address bar (dubbed omnibox), a design that adds stability to the browser. If one tab fails only one process dies; the browser can still be used as normal with the exception of the dead tab. Chrome will also implement a New Tab Page which shows the nine most visited pages in thumbnails, along with the most searched on sites, most recently bookmarked sites, and most recently closed tabs, upon opening a new tab, similar to Opera’s “Speed Dial” page.
What's New On Google Chrome 64 FINAL ?
The Chrome team is delighted to announce the promotion of Chrome 64 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.
Chrome 64.0.3282.119 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 64.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 53 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$3000][780450] High CVE-2018-6031: Use after free in PDFium. Reported by Anonymous on 2017-11-01
[$2000][787103] High CVE-2018-6032: Same origin bypass in Shared Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-11-20
[$1000][793620] High CVE-2018-6033: Race when opening downloaded files. Reported by Juho Nurminen on 2017-12-09
[$4000][784183] Medium CVE-2018-6034: Integer overflow in Blink. Reported by Tobias Klein (www.trapkit.de) on 2017-11-12
[$2500][797500] Medium CVE-2018-6035: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23
Chrome 64.0.3282.119 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 64.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 53 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$3000][780450] High CVE-2018-6031: Use after free in PDFium. Reported by Anonymous on 2017-11-01
[$2000][787103] High CVE-2018-6032: Same origin bypass in Shared Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-11-20
[$1000][793620] High CVE-2018-6033: Race when opening downloaded files. Reported by Juho Nurminen on 2017-12-09
[$4000][784183] Medium CVE-2018-6034: Integer overflow in Blink. Reported by Tobias Klein (www.trapkit.de) on 2017-11-12
[$2500][797500] Medium CVE-2018-6035: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23
Baca Artikel Lainnya
- Jual ZW3D 2023 2024 2025
- Jual ZWCAD Pro 2023 2024 2025
- JUAL Concise Beam 4.66 Analisis Desain Beban Balok Beton
- Download Browser Opera One 100 Full OFFLINE INSTALLER
- Jual Archicad 26 Mac M1 M2 Macbook macOS
- CleanMyMac BIG SUR MONTEREY VENTURA
- Chip M2 Extreme Silicon Hadir Pada Apple Mac Pro 2023
- JUAL Office APPLE Mac macOS BIG SUR
- Firefox Untuk WIndows 7 dan WIndows 8 Akan Berhenti Di 2024
- Cara Aktifkan Lucid Mode di Opera
- Download Plugins Dark mode Firefox, Chrome, Opera, Edge
- Download FIREFOX 108 OFFLINE INSTALLER 2023 WINDOWS, LINUX, macOS
- Download FIREFOX 101 OFFLINE INSTALLER 2022 WINDOWS, LINUX, macOS
- Jutaan Pengguna Windows Jadul Diblokir Untuk Update Google Chrome
- Download Google Chrome 83 OFFLINE INSTALLER FINAL 2020
- Download Google Chrome 80 OFFLINE INSTALLER FINAL 2020
- Download Google Chrome 78 OFFLINE INSTALLER FINAL
- Download FIREFOX 136 OFFLINE INSTALLER WINDOWS, LINUX, macOS
- Download FIREFOX 120 OFFLINE INSTALLER WINDOWS, LINUX, macOS
- Download Software Cek Suhu Processor Prosessor
[$2000][789952] Medium CVE-2018-6036: Integer underflow in WebAssembly. Reported by The UK's National Cyber Security Centre (NCSC) on 2017-11-30
[$1000][753645] Medium CVE-2018-6037: Insufficient user gesture requirements in autofill. Reported by Paul Stone of Context Information Security on 2017-08-09
[$1000][774174] Medium CVE-2018-6038: Heap buffer overflow in WebGL. Reported by cloudfuzzer on 2017-10-12
[$1000][775527] Medium CVE-2018-6039: XSS in DevTools. Reported by Juho Nurminen on 2017-10-17
[$1000][778658] Medium CVE-2018-6040: Content security policy bypass. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-26
[$500][760342] Medium CVE-2018-6041: URL spoof in Navigation. Reported by Luan Herrera on 2017-08-29
[$500][773930] Medium CVE-2018-6042: URL spoof in OmniBox. Reported by Khalil Zhani on 2017-10-12
[$500][785809] Medium CVE-2018-6043: Insufficient escaping with external URL handlers. Reported by 0x09AL on 2017-11-16
[$TBD][797497] Medium CVE-2018-6045: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23
[$TBD][798163] Medium CVE-2018-6046: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-31
[$TBD][799847] Medium CVE-2018-6047: Cross origin URL leak in WebGL. Reported by Masato Kinugawa on 2018-01-08
[$500][763194] Low CVE-2018-6048: Referrer policy bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-09-08
[$500][771848] Low CVE-2017-15420: URL spoofing in Omnibox. Reported by Drew Springall (@_aaspring_) on 2017-10-05
[$500][774438] Low CVE-2018-6049: UI spoof in Permissions. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-13
[$500][774842] Low CVE-2018-6050: URL spoof in OmniBox. Reported by Jonathan Kew on 2017-10-15
[$N/a][441275] Low CVE-2018-6051: Referrer leak in XSS Auditor. Reported by Antonio Sanso (@asanso) on 2014-12-11
[$N/A][615608] Low CVE-2018-6052: Incomplete no-referrer policy implementation. Reported by Tanner Emek on 2016-05-28
[$N/A][758169] Low CVE-2018-6053: Leak of page thumbnails in New Tab Page. Reported by Asset Kabdenov on 2017-08-23
[$N/A][797511] Low CVE-2018-6054: Use after free in WebUI. Reported by Rob Wu on 2017-12-24
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
[805285] Various fixes from internal audits, fuzzing and other initiatives
This release contains additional mitigations against speculative side-channel attack techniques.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
Thank you,
Abdul Syed
[$1000][753645] Medium CVE-2018-6037: Insufficient user gesture requirements in autofill. Reported by Paul Stone of Context Information Security on 2017-08-09
[$1000][774174] Medium CVE-2018-6038: Heap buffer overflow in WebGL. Reported by cloudfuzzer on 2017-10-12
[$1000][775527] Medium CVE-2018-6039: XSS in DevTools. Reported by Juho Nurminen on 2017-10-17
[$1000][778658] Medium CVE-2018-6040: Content security policy bypass. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-26
[$500][760342] Medium CVE-2018-6041: URL spoof in Navigation. Reported by Luan Herrera on 2017-08-29
[$500][773930] Medium CVE-2018-6042: URL spoof in OmniBox. Reported by Khalil Zhani on 2017-10-12
[$500][785809] Medium CVE-2018-6043: Insufficient escaping with external URL handlers. Reported by 0x09AL on 2017-11-16
[$TBD][797497] Medium CVE-2018-6045: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23
[$TBD][798163] Medium CVE-2018-6046: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-31
[$TBD][799847] Medium CVE-2018-6047: Cross origin URL leak in WebGL. Reported by Masato Kinugawa on 2018-01-08
[$500][763194] Low CVE-2018-6048: Referrer policy bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-09-08
[$500][771848] Low CVE-2017-15420: URL spoofing in Omnibox. Reported by Drew Springall (@_aaspring_) on 2017-10-05
[$500][774438] Low CVE-2018-6049: UI spoof in Permissions. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-13
[$500][774842] Low CVE-2018-6050: URL spoof in OmniBox. Reported by Jonathan Kew on 2017-10-15
[$N/a][441275] Low CVE-2018-6051: Referrer leak in XSS Auditor. Reported by Antonio Sanso (@asanso) on 2014-12-11
[$N/A][615608] Low CVE-2018-6052: Incomplete no-referrer policy implementation. Reported by Tanner Emek on 2016-05-28
[$N/A][758169] Low CVE-2018-6053: Leak of page thumbnails in New Tab Page. Reported by Asset Kabdenov on 2017-08-23
[$N/A][797511] Low CVE-2018-6054: Use after free in WebUI. Reported by Rob Wu on 2017-12-24
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
[805285] Various fixes from internal audits, fuzzing and other initiatives
This release contains additional mitigations against speculative side-channel attack techniques.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
Thank you,
Abdul Syed
DISABLE YOUR AD BLOCK
after click the link above/below, wait 5 seconds, then click on "SKIP AD" in the upper right corner
(setelah di klik Tunggu 5 detik, lalu klik tulisan "SKIP AD" di pojok kanan atas)
after click the link above/below, wait 5 seconds, then click on "SKIP AD" in the upper right corner
(setelah di klik Tunggu 5 detik, lalu klik tulisan "SKIP AD" di pojok kanan atas)
Follow @A_BlogWeb
