Tag Info

Hot answers tagged


You can download the certificate manually with openssl and add it into your local trusted certificates: echo -n | openssl s_client -connect download.01.org:443 | \ sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' | \ sudo tee '/usr/local/share/ca-certificates/download_01_org.crt' sudo update-ca-certificates


I had the same problem too. Simply open /etc/default/grub.cfg file as root and find the line which says something like GRUB_CMDLINE_LINUX="............" And paste these lines into the double quotes: acpi_osi= vconsole.font=latarcyrheb-sun16 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 rd.lvm=0 rd.md=0 ...


I've sent a message on 01.org contact form concerning this certificate problem and linking to this thread. We'll see if it's a man in the middle attack, a server misconfiguration or a new parent certificate unknown on client side. update, I had a response from intel : Appreciate you letting us know. We are aware of the situation and we are ...


I have the exact same issue. Personally, I sent a bug report and decided to downgrade chrome to its previous version. I did this by first downloading the 39.0.2171.99 version on http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/ Then I made sure to fully exit chrome, and run sudo dpkg -i google-chrome-stable<version>.deb ...

Only top voted, non community-wiki answers of a minimum length are eligible