Language Selection

English French German Italian Portuguese Spanish

Security: New Patches, Google Moves to 'Maintenance Mode', Eset Ships Binary Blob and Let's Encrypt Incident Explained

  • Security updates for Thursday

    Security updates have been issued by Debian (gdal), Fedora (nethack), Mageia (okular, sleuthkit, and webkit2), openSUSE (salt), Oracle (icu, kernel, python-pip, python-virtualenv, and zsh), Red Hat (icu, python-imaging, thunderbird, and zsh), Scientific Linux (icu, python-imaging, and zsh), SUSE (postgresql10), and Ubuntu (apache2).

  • Upcoming Chrome and Chrome OS releases

    Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases. Our primary objectives are to ensure they continue to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80. Please, follow this blog for updates.

  • Google Discontinues Chrome And Chrome OS Releases

    There seems to be the slightest change in the release date of Chrome and Chrome OS. As reported by Google, They are pausing Chrome and Chrome OS release due to adjusted work schedules.

  • Eset expands protection for businesses with Endpoint Antivirus for Linux

    Eset Endpoint Antivirus for Linux is designed to provide advanced protection from threats to organisations’ general desktops. Powered by the advanced Eset LiveGrid technology, the platform combines speed, accuracy and minimal system impact, leaving more system resources for the desktop’s vital tasks in order to maintain business continuity, the company said.

  • The Let's Encrypt certificate revocation scare

    The Let's Encrypt project has made real strides in helping to ensure that every web site can use the encrypted HTTPS protocol; it has provided TLS certificates at no charge that are accepted by most or all web browsers. Free certificates accepted by the browsers are something that was difficult to find prior to the advent of the project in 2014; as of the end of February, the project has issued over a billion certificates. But a bug that was recently found in the handling of Certificate Authority Authorization (CAA) by the project put roughly 2.6% of the active certificates—roughly three million—at risk of immediate revocation. As might be expected, that caused a bit of panic in some quarters, but it turned out that the worst outcome was largely averted.

    Let's Encrypt allows web-site operators to sign up for its service to sign their TLS certificates, so that browsers will recognize the certificate as valid. Let's Encrypt acts as a Certificate Authority (CA) and its keys are signed by a CA (IdenTrust) that is carried in the root certificate store for the browsers. That means a browser can follow the signature chain from a root certificate it trusts all the way to the certificate of the site, thus establishing the validity of the keys contained in the certificate.

    In order for a site to get a certificate from Let's Encrypt, its administrator needs to show that they control the domain in question. That's typically done by adding a challenge value provided by Let's Encrypt to either the DNS information for the domain or via a URL that can be retrieved from the domain's web server. The administrator proves that they have the needed access, thus show that the domain is under their control.

    Administrators who wish to restrict the kinds of certificates that can be issued for their domains can add CAA records to their DNS configuration. Those can be used to disallow certain providers, such as Let's Encrypt, from issuing certificates for a domain or portion of one. For example, the web site administrator at "subdomain.example.com" could not receive a certificate from Let's Encrypt or some other CA simply by adding a web page to the server they control if the administrator of the top-level "example.com" domain disallowed that with CAA records. Some sites may also want to restrict the CAs that can be used; some CAs offer services beyond just signing, which may be required for security or regulatory compliance.

COVID19: Google suspends upcoming Chrome, Chrome OS releases

  • COVID19: Google suspends upcoming Chrome, Chrome OS releases

    In view of the ongoing developments with novel coronavirus outbreak, Google on Wednesday said it has paused upcoming releases for Chrome and Chrome OS to ensure it continues to be stable, secure, and work reliably for all.

    "Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases. Our primary objectives are to ensure they continue to be stable, secure and work reliably for anyone who depends on them. We'll continue to prioritize any updates related to security, which will be included in Chrome 80," Google Chrome wrote in a blog post.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Essential Guide: How to Upgrade to Ubuntu 20.04 (Beta) Right Now

Well, in this guide I show you the steps required to upgrade to Ubuntu 20.04 from Ubuntu 18.04 or Ubuntu 19.10 right now, , nice and early, ahead of the final release. You do not need to download an .iso, fuss around with a USB thumb drive, or lose any of your files — you can upgrade directly with a half-way decent internet connection. Just keep in mind that (at the time you read this) the final stable release of the Focal Fossa is not yet available, only a beta quality candidate is. Read more

Plasma Mobile: How to help us!

We often get asked: “how long until the 1.0 release?”. Or: “how far away is Plasma Mobile 1.0?”. The usual answer to both these question is “It’ll be ready when it is ready”. But, really, how do we know that it is ready? Recently some of us prepared a check list of items which we consider necessary before we can declare Plasma Mobile “ready” or at rc1 status. Read more

Android Leftovers

today's leftovers

  • Mesa 20.0.3 Released With Latest Open-Source Graphics Driver Fixes

    While many of you are users of Mesa Git for experiencing the bleeding-edge graphics drivers especially if you are a gamer wanting peak performance, for those on the Mesa stable series the Mesa 20.0.3 update has now shipped. Mesa 20.0.3 is the latest bi-weekly point release for back-porting the fixes to this Q1'2020 stable series.

  • Adrien Plazas: A Coloring API for GTK

    This week we had the Design Tools Hackfest 2020, virtualized because of COVID-19, where we discussed that recoloring API. We came up with something I think is interesting enough to discuss more widely.

  • [Former Canonical manager] Dustin Kirkland: Coordinated Launch Cycles at Apex

    I joined Apex Clearing last year, having spent the previous 20 years as a software engineer, product manager, and executive, mostly around open source software, including Ubuntu, OpenStack, and Kubernetes. Albeit IBM, Canonical and Google differ from fintech on many levels, these operating systems and cloud infrastructure technology platforms share a number of similarities with Apex's software-as-a-service platform. Moreover, there also exists some literal overlap: we’re heavy users of both Ubuntu and Kubernetes here at Apex. Ubuntu, OpenStack, and Kubernetes all share similar, predictable, time-based release cycles. Ubuntu has released every April and October, since October of 2004 – that's 32 major software platform releases, on time, every time, over 16 years. Ubuntu has set the bar for velocity, quality, and predictability in the open source world. OpenStack’s development processes have largely mirrored Ubuntu’s, with many of the early project leaders having been ex-Ubuntu engineers and managers. OpenStack, too, has utilized a 6-month development cycle, since 2010, now on its 20th release. Kubernetes came along in 2014, and sought to increase the pace a bit, with quarterly release cycles. Kubernetes is a little bit looser with dates than Ubuntu or OpenStack, but has generally cranked out 4 quality releases per year, over the last 6 years. I’ve been involved in each of these projects at some level, and I’ve thoroughly enjoyed coaching a number of early stage start-ups on how to apply these principles to their product development methodologies.

  • Ulrike Uhlig: Breaking the chain reaction of reactions to reactions

    Each of these interactions is embedded in larger society, and, as said above, we learn these roles from childhood. Therefore, we perpetually reproduce power structures, and learnt behavior. I doubt that fixing this on an individual level is sufficient to transform our interactions outside of small groups, families or work places. Although that would be a good start. We can see that the triangle holds together because the Victim, seemingly devoid of a way to handle their own needs, transfers care of their needs to the Rescuer, thereby giving up on their autonomy. The Rescuer is provided by the Victim with a sense of autonomy, knowledge, and power, that only works while denying the Victim their autonomy. At the same time, the Persecutor denies everyone else's needs and autonomy, and feels powerful by dismissing others. I've recently mentioned the importance of autonomy in order to avoid burnout, and as a means to control one's own life. If the Rescuer can acknowledge being in the triangle, and give the Victim autonomy, by supporting them with compassion, empathy, and guidance, and at the same time respecting their own boundaries, we could find even more ways to escape the drama triangle.