With the release of Core 4.2.2, we have reached the end of the “Series 4” of AOSC OS Core.
This point release updated Linux API Headers to version 4.11.3 in order to retain compatibility of the new Chromium/Google Chrome 59 browser - which contains a great deal of security updates/fixes. With July closing in, we are getting ready to unveil the collection of features and updates coming in Core “E” - our fifth Core release series - coming this summer.
With the hint “E” - yes, we are about to start a call-for-codename for this new series of AOSC OS Core releases, we will vote for the next codename on the first day of AOSCC 2017 - details coming in the following week or so.
Just a short announcement to tell you what’s up with the new version - and moreover, to thank you for using AOSC OS and staying supportive of our development effort.
Core 4.2.2 is now available for
amd64 users, this update will come for
armel (ARMv7) and
arm64 (ARMv8, AArch64) users in the coming week.
powerpc (PowerPC 32-bit),
ppc64 (PowerPC 64-bit, big endian) users however… Please don’t wait around, as none of these architectures will support the Chromium browser family, we have elected to skip this release. Core “E” will come in time, however, so look out for that!
Lastly, as we have no PowerPC device available for development at the moment, we have decided to suspend all updates - and that includes security updates - for both PowerPC architectures.
We do apologise for the inconvenience and we would further recommend that you move away from AOSC OS for this summer, in our hope to keep you safe from cyberattacks and existing bugs.
— Mingcong Bai
Please update your
amd64 only) and
chromium packages to version
A recently released version of Chromium and Google Chrome has addressed a series of security vulnerabilities, assigned with the following CVE IDs:
CVE-2017-5070, CVE-2017-5071, CVE-2017-5072, CVE-2017-5073, CVE-2017-5074, CVE-2017-5075, CVE-2017-5076, CVE-2017-5077, CVE-2017-5078, CVE-2017-5079, CVE-2017-5080, CVE-2017-5081, CVE-2017-5082, CVE-2017-5083, CVE-2017-5085, CVE-2017-5086.
Please update your
sudo package to version
A recently released version of Sudo has addressed a security vulnerability titled “Potential overwrite of arbitrary files on Linux”:
“On Linux systems, sudo parses the /proc/[pid]/stat file to determine the device number of the process’s tty (field 7). The fields in the file are space-delimited, but it is possible for the command name (field 2) to include spaces, which sudo does not account for. A user with sudo privileges can cause sudo to use a device number of the user’s choosing by creating a symbolic link from the sudo binary to a name that contains a space, followed by a number.”
This vulnerability has been assigned CVE-2017-100036.
Just a quick notice that Cinnamon 3.4 is now available in our community repository (along with the new Slick Greeter)! Here’s a screenshot…
For more information on changes introduced with Cinnamon 3.4 please refer to this Linux Mint blog post.
With the hard work of our community infrastructure contributors, there are now two more services available for our community members:
Thanks to Dingyuan Wang (gumblex) for creating this website.
It should not take much explanation for our Packages site - as mentioned above, it is a catalog of AOSC OS packages - and you could now search for a particular package available to AOSC OS (or to find out if it’s available yet), check on update status, and compare versions of a given package available to all our AOSC OS ports.
Dingyuan Wang also mentioned that there will be a function where AOSC OS users could file package requests on the same website, making it easier for users and developers to check on request status.
Thanks to Sijie Bu (butangmucat) for making this service available.
Currently there are four mailing lists available, each dedicated to different functions…
If you have any questions, concerns, or suggestions to our community services and infrastructure, please pop a mail to our discussions mailing list
Please update your
firefox package to version
53.0 and above.
A recently released version of Firefox has addressed the following security vulnerabilities, assigned with multiple CVE IDs:
CVE-2017-5429, CVE-2017-5430, CVE-2017-5432, CVE-2017-5433, CVE-2017-5434, CVE-2017-5435, CVE-2017-5436, CVE-2017-5437, CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442, CVE-2017-5443, CVE-2017-5444, CVE-2017-5445, CVE-2017-5446, CVE-2017-5447, CVE-2017-5448, CVE-2017-5449, CVE-2017-5450, CVE-2017-5451, CVE-2017-5452, CVE-2017-5453, CVE-2017-5454, CVE-2017-5455, CVE-2017-5456, CVE-2017-5458, CVE-2017-5459, CVE-2017-5460, CVE-2017-5461, CVE-2017-5462, CVE-2017-5463, CVE-2017-5464, CVE-2017-5465, CVE-2017-5466, CVE-2017-5467, CVE-2017-5468, CVE-2017-5469.
Please update your
google-chrome packages to version
58.0.3029.81 and above.
A recently released version of Chromium/Google Chrome Web browser addressed the following security issues, assigned with multiple CVE IDs:
We have received complaints regarding their SSH Host keys being erased despite that they have already regenerated their SSH Host key before
AOSA-2017-0034 was posted.
This is our fault for not checking on vulnerable host keys by checksum - instead, we chose to regenerate the keys regardless. But here’s the way to workaround this issue, issue this command before you upgrade your system (given that your
openssh package has version older than
# touch /usr/share/doc/openssh/AOSA-2017-0034
Again, we apologize for this incident.