Language Selection

English French German Italian Portuguese Spanish

Upcoming Fedora Test Days: preupgrade and Xfce!

Filed under
OS
Linux

So this week we round out the Fedora 13 Test Day schedule, which has seen us run the gauntlet from NFS, through color management and SSSD, scale the heights of Graphics Test Week, and will see us come to a triumphant finish with the Preupgrade Test Day on Thursday 2010-04-29 and the Xfce Test Day on Friday 2010-04-30.

These are two juicy topics: preupgrade is the recommended method for upgrading from one Fedora release to the next, and is widely used. We also really need to have it working properly at release time, so we need your help to test and make sure it is! Xfce is one of the most popular 'alternate' Linux desktops, and has a very dedicated Fedora SIG which works hard to provide a smooth experience and live spin, and has organized the Test Day to make sure the Fedora 13 Xfce experience is second to none. So please come out and help us polish off these final Fedora 13 features!

As always, the Test Days will run all day in the #fedora-test-day channel on Freenode IRC. If you're not sure about IRC, read the guide or use WebIRC. If you can't do the testing on the Test Day, you can still run through the tests and provide your results earlier or later; you'll just miss out on the real-time IRC discussion, but that's okay. You can do the Xfce testing with a live image which will be provided on the Test Day page. Obviously this isn't possible for the preupgrade testing, but you can test it in a virtual machine if you don't want to (or can't) mess with your real Fedora installation.

Testing is easy and there's lots of guidance on how to do the testing and file your results on the Wiki pages - you don't need any special skills to help out! Even if you get stuck, there will be QA team members, developers, and other testers on IRC to help you out. The more testing we get done the more polished Fedora 13 will be for everyone.

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos