Welcome to Anthon Open Source Community! We are a group of free and open technology enthusiasts working hard for improvements.

Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program. -- Linus Torvalds


  • Repository key expiration!FEBRUARY 14, 2017

    Let us start with an apologize - we messed up. Starting with AOSC OS2 back in early 2014, the repositories for AOSC OS were signed with a GPG key - it was a time when we had no idea about longterm maintainership - thus no plan, nor anticipation for the expiration of this GPG key on Valentine's Day of 2017.

    Although the problem has already been addressed for our source repository (with extra security enhancements), we do realize that some of you have already been running into issues trying to update your AOSC OS. It will be another two days before we could push out another batch of updates that addresses this issue directly - but you can still fix it yourself (albeit you can't even obtain an update for Apt now, as you can't update your system anyways). So here is how it goes:

    First, obtain a copy of our new GPG key.


    Then, remove the old key from the old storage.

    sudo rm -fv /etc/apt/trusted.gpg

    And finally, add the new key to the Apt key storage.

    sudo apt-key add 20170214-2y.gpg

    And you should be greeted with an "OK" message. Now, you are good to go again with the new keys on hand.

    sudo apt update

    But at the time of posting, you may not be able to update your system via our various mirrors, this is because our new signature was not yet synchronised with the mirrors. To workaround this issue temporarily, use apt-gen-list and select our source server again - it might be slower in certain areas, but it gets the job done.

    sudo apt-gen-list -e "40-source"

    Then, as usual.

    sudo apt update
  • Core 4.2 is here!FEBRUARY 8, 2017


    Core 4.2 was just released as the latest feature update to the Core 4.0 series. With 4.2, we have updated virtually every single component in the Core, but more importantly, we have officially added support for the MIPS64 Little Endian architecture, currently maintained by Junde Yhi (creation of build specifications, and package porting) and Mingcong Bai (package porting).

    What's more? You could expect, with Core 4.2:

    • Improved network performance.
    • Security enhancements.
    • Component updates.

    Core 4.2 is now readily available for the AMD64/x86_64 port of AOSC OS, updates for all other architectures will come in this upcoming weekend.

    Please note that Core 4.2 contains security updates, which were assigned with AOSA-2017-0018 (for GNU C Library) and AOSA-2017-0019 (for Bash). Please update your AOSC OS with the newest Core at your earliest convenience!

    For detailed description of changes made between Core 4.1 and 4.2, please checkout the full changelog.

  • AOSA-2017-0019: Update BashFEBRUARY 8, 2017

    Please update your bash package to version 4.4.12.

    At patch level 7, which would be version 4.4.7 of Bash, a security issue was addressed that:

    "An exploit can be realized by creating a file or directory with a specially crafted name. A user utilizing GNU Bash’s built-in path completion by hitting the Tab button (f.e. to remove it with rm) triggers the exploit without executing a command itself. The vulnerability has been introduced on the devel-branch in May 2015."

    And was consequently assigned CVE-2017-5932.

    Relevant documentation:

  • AOSA-2017-0018: Update GlibcFEBRUARY 8, 2017

    Please update your glibc package to version 2.25.

    Two security vulnerabilities were addressed in the recently released GNU C Library, version 2.25:

    • On ARM EABI (32-bit), generating a backtrace for execution contexts which have been created with makecontext could fail to terminate due to a missing .cantunwind annotation. This has been observed to lead to a hang (denial of service) in some Go applications compiled with gccgo. Reported by Andreas Schwab. (CVE-2016-6323)
    • The DNS stub resolver functions would crash due to a NULL pointer dereference when processing a query with a valid DNS question type which was used internally in the implementation. The stub resolver now uses a question type which is outside the range of valid question type values. (CVE-2015-5180)

    Relevant documentation:

  • Dev. Updates (Issue #1, 2017)FEBRUARY 6, 2017

    Here's a quick introduction to a new series of posts regarding AOSC OS development updates over a period of time (per one to two months) - a brief description about what we have done while nothing was posted on the Portal, and a look into the next period of time - what would we do, and what could you expect from us.

    What happened?

    January is a month when most of our developers took a break from busy school work (winter break, whee), and the month when time allows for major changes to AOSC OS. In the past month, we have updated some major components of AOSC OS, including Python 3.6, OpenMPI 2.0, and Boost 1.63. All of these changes will definitely improve performance, and making work easier for developers using AOSC OS. Do keep in mind that these update required an extensive amount of rebuild due to ABI/API incompatibilities introduced with new versions of these components - do expect hundreds to thousands of package updates, and (unfortunately) some bugs introduced by our oversight. If you did happen to bump into a friendly (or not so friendly) bug, do report it to us.

    Progress was also made on the MIPS64 front, for which we have finished building a base system - it's ready to boot with full Systemd - when a Kernel is ready for Junde Yhi's Loongson 3A. But given time constraints in recent weeks, we could not guarantee a released tarball until summer break time (June, or July).

    What you could expect before Issue #2

    In the coming month, we will push out a new series of tarballs (system releases) for the spring, which of course, will include the newest packages we could offer for each of our AOSC OS ports. Also, we will make another attempt on pushing out Live system releases with a functional and graphical installation program.

    On the question of ports, we are now armed with a bare-metal RISC-V rv32i toolchain, once we get our hands on a device, we should be able to start a new port (8th!) for AOSC OS - if not, we might have to start with RISC-V's official ISA emulator, Spike.

    WSAOSC (Windows Subsystem for AOSC OS) will also start a complete rewrite, led by Yi Rong, the original creator of the old installer written in Go language. More details will be posted when development restarts.

    And that's all for this issue of Dev. Update for AOSC OS, we will see you around in a bit. If you want to get in touch with us, please join our IRC channel at #aosc on

  • New package additions: Feb. 6, 2017

  • AOSA-2017-0017: Update TCPDump

  • AOSA-2017-0016: Update LCMS2

  •



  • Google+

    A portal that syncs the newest news and happenings in and around AOSC.

  • Public Clipboard

    Our public clipboard service (or pastebin) that you can use for all your clippy needs.

  • Community Repository

    Our community repository server, where AOSC OS installation medias, tarballs, packages, project documentation, etc. are stored.

  • IRC Logs

    Have a look at our chatter room!