iMaccanici Assistenza Mac

Riguardo gli ultimi miei post ho trovato queste due segnalazione dello stesso "bug":

https://bugs.chromium.org/p/chromium/is ... ?id=806599" onclick="window.open(this.href);return false;

https://bugs.chromium.org/p/chromium/is ... ?id=806506" onclick="window.open(this.href);return false;

Il mio inglese non è proprio il massimo e quindi non sono sicuro di aver capito tutto... Nel primo link pare che il team di Chrome non sia riuscito a riprodurre l'errore, nel secondo ... boh?!

Io ho segnalato la cosa non nel forum ma dal form che appare in Chrome/Informazioni/Segnala un problema.

Google Chrome - 64.0.3282.140






Security Fixes and Rewards:

[808163] Various fixes from internal audits, fuzzing and other initiatives

>>> https://chromereleases.googleblog.com/2 ... sktop.html" onclick="window.open(this.href);return false;

>>> https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

P.S.
Pare propio che abbiano sistemato quella seccatura per la quale avevo dovuto disattivare l'accelerazione hardware: ora l'ho riattivata e non ho avuto problemi a visualizzare a schermo intero quel video che avevo segnalato nei precedenti post.

Meglio così.
Grazie per il riscontro.

Google Chrome - 64.0.3282.167






[806388] High CVE-2018-6056: Incorrect derived class instantiation in V8. Reported by lokihardt of Google Project Zero on 2018-01-26


https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Google Chrome - 64.0.3282.186






https://chromereleases.googleblog.com/2 ... op_22.html


https://www.google.com/intl/it/chrome/browser/?hl=it

Google Chrome - 65.0.3325.146






Security Fixes and Rewards:

[758848] High CVE-2018-6058: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25
[758863] High CVE-2018-6059: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25
[780919] High CVE-2018-6060: Use after free in Blink. Reported by Omair on 2017-11-02
[794091] High CVE-2018-6061: Race condition in V8. Reported by Guang Gong of Alpha Team, Qihoo 360 on 2017-12-12
[780104] High CVE-2018-6062: Heap buffer overflow in Skia. Reported by Anonymous on 2017-10-31
[789959] High CVE-2018-6057: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-11-30
[792900] High CVE-2018-6063: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-12-07
[798644] High CVE-2018-6064: Type confusion in V8. Reported by lokihardt of Google Project Zero on 2018-01-03
[808192] High CVE-2018-6065: Integer overflow in V8. Reported by Mark Brand of Google Project Zero on 2018-02-01
[799477] Medium CVE-2018-6066: Same Origin Bypass via canvas. Reported by Masato Kinugawa on 2018-01-05
[779428] Medium CVE-2018-6067: Buffer overflow in Skia. Reported by Ned Williamson on 2017-10-30
[798933] Medium CVE-2018-6068: Object lifecycle issues in Chrome Custom Tab. Reported by Luan Herrera on 2018-01-04
[799918] Medium CVE-2018-6069: Stack buffer overflow in Skia. Reported by Wanglu & Yangkang(@dnpushme) of Qihoo360 Qex Team on 2018-01-08
[668645] Medium CVE-2018-6070: CSP bypass through extensions. Reported by Rob Wu on 2016-11-25
[777318] Medium CVE-2018-6071: Heap bufffer overflow in Skia. Reported by Anonymous on 2017-10-23
[791048] Medium CVE-2018-6072: Integer overflow in PDFium. Reported by Atte Kettunen of OUSPG on 2017-12-01
[804118] Medium CVE-2018-6073: Heap bufffer overflow in WebGL. Reported by Omair on 2018-01-20
[809759] Medium CVE-2018-6074: Mark-of-the-Web bypass. Reported by Abdulrahman Alqabandi (@qab) on 2018-02-06
[608669] Medium CVE-2018-6075: Overly permissive cross origin downloads. Reported by Inti De Ceukelaire (intigriti.com) on 2016-05-03
[758523] Medium CVE-2018-6076: Incorrect handling of URL fragment identifiers in Blink. Reported by Mateusz Krzeszowiec on 2017-08-24
[778506] Medium CVE-2018-6077: Timing attack using SVG filters. Reported by Khalil Zhani on 2017-10-26
[793628] Medium CVE-2018-6078: URL Spoof in OmniBox. Reported by Khalil Zhani on 2017-12-10
[788448] Medium CVE-2018-6079: Information disclosure via texture data in WebGL. Reported by Ivars Atteka on 2017-11-24
[792028] Medium CVE-2018-6080: Information disclosure in IPC call. Reported by Gal Beniamini of Google Project Zero on 2017-12-05
[797525] Low CVE-2018-6081: XSS in interstitials. Reported by Rob Wu on 2017-12-24
[767354] Low CVE-2018-6082: Circumvention of port blocking. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-09-21
[771709] Low CVE-2018-6083: Incorrect processing of AppManifests. Reported by Jun Kokatsu (@shhnjk) on 2017-10-04


>>> https://chromereleases.googleblog.com/2 ... sktop.html" onclick="window.open(this.href);return false;

>>> https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Google Chrome - 65.0.3325.162






https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Google Chrome - 65.0.3325.181





Various fixes from internal audits, fuzzing and other initiatives.

>>> https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Google Chrome - 66.0.3359.117






https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Kernel Panic ha scritto:Google Chrome - 66.0.3359.117

https://www.google.com/intl/it/chrome/browser/?hl=it" onclick="window.open(this.href);return false;

Grazie!

Qui l'elenco delle modifiche: https://chromereleases.googleblog.com/2 ... sktop.html" onclick="window.open(this.href);return false;

“Google ha dichiarato che con la nuova versione di Chrome (68.x) etichetterà come non sicuri tutti i siti web senza https (SSL)”

[andrea] ha scritto:“Google ha dichiarato che con la nuova versione di Chrome (68.x) etichetterà come non sicuri tutti i siti web senza https (SSL)”

Come noi!


Insicuri a vita...

fragrua ha scritto:

[andrea] ha scritto:“Google ha dichiarato che con la nuova versione di Chrome (68.x) etichetterà come non sicuri tutti i siti web senza https (SSL)”

Come noi!


Insicuri a vita...

però dovremmo far qualcosa...

Tipo comprare un certificato ssl... La cosa "buffa" è che capita anche quando accedi ad apparati tramite browser, tipo firewall, telecamere, nas e via di questo passo.

kext ha scritto:però dovremmo far qualcosa...

Più di sollecitare non posso… siamo nelle mani di un coso chiamato Stefano!