A Trojan named Linux.Mirai has been found to be carrying out DDoS attacks.
The malicious program first appeared in May 2016, detected by Doctor Web after being added to its virus database under the name Linux.DDoS.87. The Trojan can work with with the SPARC, ARM, MIPS, SH-4, M68K architectures and Intel x86 computers.
Over 10,000 of you have joined EFF in calling on HP to make amends for its self-destructing printers in the past few days. Looks like we got the company’s attention: today, HP posted a response on its blog. Apparently recognizing that its customers are more likely to see an update that limits interoperability as a bug than as a feature, HP says that it will issue an optional firmware update rolling back the changes that it had made. We’re very glad to see HP making this step.
But a number of questions remain.
First, we’d like to know what HP’s plans are for informing users about the optional firmware update. Right now, the vast majority of people who use the affected printers likely do not know why their printers lost functionality, nor do they know that it’s possible to restore it. All of those customers should be able to use their printers free of artificial restrictions, not just the relatively few who have been closely following this story.
You've probably read a few articles about driverless cars over the past couple of years. The technology is coming along quickly, with fleets of test cars already on the roads in some states. It seems like soon we'll achieve the American dream of stuffing our faces and texting all we want while still managing to avoid public transportation.
But the reality is quite different. We're diving into this technology a little too quickly and ignoring all the warning signs about how we are going to screw up on the way to Driverless Car Utopia.
Perhaps you already noticed it, I have switched all the sites for a secured browsing using HTTPS.
So, new addresses are:
https://blog.remirepo.net/ for this Blog (with an automatic and permanent redirection)
https://forum.remirepo.net/ for the Forum (with an automatic and permanent redirection)
https://rpms.remirepo.net/ for the Repository, but classical address stay available.
Fedora Hubs provides a consistent contributor experience across all Fedora teams and will serve as an “intranet” page for the Fedora Project. There are many different projects in Fedora with different processes and workflows. Hubs will serve as a single place for contributors to learn about and contribute to them in a standardized format. Hubs will also be a social network for Fedora contributors. It is designed as one place to go to keep up with everything and everybody across the project in ways that aren’t currently possible.
AMD developer Marek Olšák initiated the discussion about calling for the next Mesa release to succeed version 12.0. Regardless, it's looking like it will be another release off their three-month cadence.
Marek pointed out that it's been four months since Mesa 12.0 was branched and three months since 12.0 was actually released. He's asking why a stable branch hasn't been created yet and that ideally they should have got this release out 1~2 months before the fall distribution updates, per this mailing list thread.