Prevented by Google from using the Android operating system, in the United States, the technology giant Huawei poses new challenges.

The android development company, according to relevant publications, is working on its own operating system called HongMeng.

"We prepared our own operating system, this is our plan B. But, of course, we would prefer to work with Google and Microsoft ecosystems",  one of the executive directors of the company, Richard U, told the German newspaper Die Welt in March.

“They [Huawei] already have a system, but they are not ready to [launch it],” said Wong Kam Fai, a professor at the University of Hong Kong, to France Press. now they must speed up."

Huawei Honor 20: the company introduced a new smartphone. But did not say anything about the sanctions

According to the source of the publication Huawei Central, specializing in technology news about the corporation, the new system will be called HongMeng OS.

How much is a billion? A billion of anything, let alone dollars, is a lot.  A billion is 1,000 million. If you stack one billion $1 banknotes on top of each other, the pile would reach 68 miles upwards into the sky.

When it comes to investing money, whenever you hear of a billion dollars being spent, you just know that there is serious money to be made.

One raising as a rocket industry where billions are being spent is blockchain. And this number is growing drastically every year.

Experts warned that the Alpine Linux Docker images, which had been distributed through the official Docker Hub for about three years, used an empty password (NULL) for the root account. The problem affected all versions of Alpine Linux since 3.3. It is worth noting that Alpine Linux is one of the most popular distributions on the Docker Hub, with more than 10,000,000 installations.

The vulnerability received the identifier CVE-2019-5021, and in this case it is interesting that it was not discovered for the first time. The problem was already paid attention in August 2015 and corrected in November. But only three weeks after the patch was released, in December 2015, the bug accidentally returned to the code, and was seen again only in January of this year by analysts. At first it was thought that the problem only affected the Glider Labs Alpine Linux image, but then it became clear that the official images had also suffered.