What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fedora 43 ushered in RPM 6.0 on October 28, 2025, making it the first Fedora release to ship the new RPM software stack, while Jef Spaleta succeeded Matthew Miller as Fedora Project Leader. Fedora 43 retained RPM v4 package generation by default, so the release modernized RPM security without immediately converting Fedora’s repositories to RPM v6 packages.
This is a retrospective account of the Fedora 43 release window, not a breaking-news announcement. The two developments belong to the same period, but they represent different kinds of change: RPM 6.0 is a packaging and security-infrastructure upgrade, while the Project Leader transition is a governance and community-leadership change.
Key takeaways
- Fedora Linux 43 reached general availability on October 28, 2025, and was the first Fedora release to include RPM 6.0.
- Fedora 43 continued generating RPM v4 packages by default, so shipping RPM 6.0 did not mean an immediate Fedora-wide migration to the RPM v6 package format.
- RPM 6.0 modernized OpenPGP support, package signatures, key identification, digest algorithms, signing backends, and package-provenance capabilities.
- Fedora did not yet adopt RPM 6.0’s upstream enforced-signature default in Fedora 43.
- Jef Spaleta was announced as Matthew Miller’s successor on April 2, 2025, with the formal leadership handoff planned around Flock 2025.
- Everyday Fedora users were more likely to notice changes in verification, signing, diagnostics, and third-party tooling than changes to the desktop interface or package-installation workflow.
What exactly happened in Fedora 43?
Fedora Linux 43 was released on October 28, 2025, and became the first Fedora release to ship RPM 6.0. Fedora’s official release coverage presented RPM 6.0 as a major underlying change focused largely on package security, signatures, and modern cryptographic capabilities; the Fedora 43 announcement from Red Hat provides the release context.
The RPM project released RPM 6.0 upstream on September 22, 2025. Fedora’s package record identifies the Fedora 43 build as rpm-6.0.0-1.fc43, rebased to the RPM 6.0 final release. Fedora therefore adopted the new RPM software version during Fedora 43’s development and release cycle, but Fedora made a separate decision about which package format to generate.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- USB-C 2-in-1 storage OTG: The Lexar JumpDrive Dual Drive D40E features USB Type-A and Type-C connectors in a slim, portable form factor for easy device compatibility
- Transfer speeds up to 100MB/s: Based on internal testing, performance may vary depending upon the host device, interface, and usage conditions. 1MB=1,000,000 bytes
- Plug and Play: Widely compatible with USB Type-C smartphones, tablets, laptops, Macs, and traditional Type-A devices, no software installation required. The 360° swivel design allows for easy switching between connectors without the hassle of losing a cap
- Durable & Compact: The Lexar D40E USB memory stick features a metal enclosure, withstands temperatures from 0° to 50° C (32°F to 122°F), and is lightweight at 26g with dimensions of 70.4 x 16.9 x 11.7mm
- Security & Warranty: Securely protects files using an advanced security software solution with 256-bit AES encryption. Backed by a Lexar 3-year limited warranty
| Term | What it means | Fedora 43 position |
|---|---|---|
| RPM 6.0 | The RPM package-management software and library version. | Shipped in Fedora 43. |
| RPM v4 | The established RPM package format used for Fedora package generation. | Remained Fedora 43’s default output format. |
| RPM v6 | The newer package format supported by RPM 6.0. | Supported by RPM 6.0, but not adopted as Fedora 43’s default generated format. |
| Signature enforcement | Rejecting packages when required signatures are absent or invalid. | Fedora 43 deferred the upstream RPM 6.0 enforced-signature default. |
The distinction matters because the phrase “Fedora 43 moved to RPM 6” can be misunderstood. Fedora 43 upgraded the RPM engine, but Fedora did not simultaneously rebuild every repository package in RPM v6 format. Fedora’s RPM 6.0 change proposal explicitly kept v4 package generation as the Fedora 43 default and placed the v6 format migration outside the scope of that change.
What does RPM 6.0 add?
RPM 6.0 adds modern signing, key-management, digest, and package-format capabilities intended to improve package authenticity and integrity. The upstream RPM 6.0 release notes describe the capabilities below, although upstream support should not be confused with every Fedora 43 default.
Modern OpenPGP keys and signatures
RPM 6.0 supports OpenPGP v6 keys and signatures, as well as key and signature capabilities related to post-quantum cryptography. RPM 6.0 also supports multiple OpenPGP signatures on a package. Multiple signatures can provide more flexible verification and transition paths when signing infrastructure or keys change.
Key identification becomes less dependent on short key IDs. RPM 6.0 uses full key IDs or fingerprints in areas where short identifiers could be ambiguous. Previously imported keys can be updated with rpmkeys --import, which is relevant to administrators maintaining trusted key material over time.
More signing-backend choices
RPM’s signing tool, rpmsign, can use either GnuPG or Sequoia’s sq as a signing backend. Sequoia provides an alternative OpenPGP implementation for organizations that do not want their signing workflow tied exclusively to GnuPG-specific behavior.
That flexibility also creates a compatibility consideration: custom signing commands and scripts that assume a particular backend, output layout, or short key-ID format should be tested rather than presumed to work unchanged.
Additional and stronger digests
RPM 6.0 adds support for stronger and additional package and payload digests, including SHA-3-256 and SHA-512. The package header and payload are separate integrity concerns: metadata in the header describes the package, while the payload contains the files that will be installed.
The RPM project’s signatures and digests documentation explains how signatures and hashes contribute to verification. The practical goal is not simply a new algorithm label; it is stronger evidence that package metadata and package contents have not been altered and that the package came through a verifiable signing and build process.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
RPM v6 package-format support
RPM 6.0 supports the new RPM v6 package format in addition to RPM v4 packages. The format adds or standardizes contemporary cryptographic algorithms, SHA-3-256 header digests, SHA-512 and SHA-3-256 payload digests, 64-bit size fields, per-file MIME information, and payload hashes that can independently help establish package provenance.
The RPM v6 format documentation describes the format in more detail. RPM’s rpmformat query tag can identify package format 3, 4, or 6, allowing package-inspection tools to distinguish the format instead of inferring it from a filename or RPM version alone.
Why is RPM 6.0 not the same as RPM v6 packages?
RPM 6.0 is the software version; RPM v6 is a package-file format, and Fedora 43 adopted the former without making the latter its default output. This is the central technical qualification for understanding Fedora 43.
Upstream RPM 6.0 defaults to building v6 packages, but Fedora’s accepted change kept Fedora 43 package generation at v4. Fedora made that choice to limit the immediate compatibility impact while the RPM 6.0 software became available for testing and use. Fedora 43 could therefore use the new RPM implementation while continuing to distribute the package format its existing ecosystem expected.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →RPM 6.0 can read both RPM v4 and RPM v6 packages, but “supports both” does not mean that every older RPM release supports every operation equally. RPM’s compatibility notes say that v6 packages can be queried by RPM versions as old as 4.6, unpacked by versions as old as 4.12, and verified or installed by RPM 4.14 and newer with qualifications. The exact result depends on the operation, the package contents, and the older RPM implementation.
| Operation or assumption | What the documentation supports | Practical qualification |
|---|---|---|
| Using RPM 6.0 with existing Fedora packages | RPM 6.0 supports RPM v4 packages. | Fedora 43 continued generating v4 packages by default. |
| Identifying package format | The rpmformat tag identifies format 3, 4, or 6. |
Tooling should inspect the format rather than assume the RPM software version determines it. |
| Querying v6 packages with older RPM | Query support reaches back to RPM 4.6 according to RPM’s compatibility notes. | Query support is not equivalent to full installation or verification support. |
| Unpacking v6 packages with older RPM | Unpacking support reaches back to RPM 4.12 according to the documented compatibility notes. | Other package operations may have stricter requirements. |
| Installing or verifying v6 packages with older RPM | RPM 4.14 and newer are documented with caveats. | Test the complete operation in the target environment before deployment. |
RPM v3 package installation support was removed in RPM 6.0, although RPM 6.0 retains limited abilities to query and unpack older v3 packages. Administrators maintaining legacy package archives should treat this as a compatibility boundary rather than assuming that every historical RPM remains installable.
Did Fedora 43 enable mandatory signature checking?
No: Fedora 43 did not adopt RPM 6.0’s upstream enforced-signature default. Upstream RPM 6.0 enables signature checking by default, but Fedora’s RPM 6.0 change proposal explicitly deferred the corresponding Fedora default change.
This distinction prevents two opposite mistakes. Fedora 43 did gain the newer RPM signature and key-handling implementation, but Fedora 43 did not automatically turn every upstream signature-enforcement behavior into a Fedora-wide policy. Repository configuration, package-management policy, and future Fedora changes determine how signature enforcement is applied.
Rank #3
- What You Get - 2 pack 64GB genuine USB 2.0 flash drives, 12-month warranty and lifetime friendly customer service
- Great for All Ages and Purposes – the thumb drives are suitable for storing digital data for school, business or daily usage. Apply to data storage of music, photos, movies and other files
- Easy to Use - Plug and play USB memory stick, no need to install any software. Support Windows 7 / 8 / 10 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, compatible with USB 2.0 and 1.1 ports
- Convenient Design - 360°metal swivel cap with matt surface and ring designed zip drive can protect USB connector, avoid to leave your fingerprint and easily attach to your key chain to avoid from losing and for easy carrying
- Brand Yourself - Brand the flash drive with your company's name and provide company's overview, policies, etc. to the newly joined employees or your customers
For ordinary users, package signatures still matter because package managers use repository metadata and package verification to help establish authenticity and integrity. However, users should not interpret the RPM 6.0 upgrade alone as a promise that Fedora 43 rejects every unsigned or improperly signed package in every configuration.
What changes for ordinary Fedora users?
Most Fedora Workstation, Server, and Spin users can continue using the normal Fedora update and package-management workflow. RPM operates underneath DNF and related tools, so the RPM 6.0 transition does not require users to manually rebuild their package database or change the desktop interface.
The most likely user-visible effects are in package verification, key handling, error messages, diagnostics, and the behavior of external repositories or utilities. A routine installation from standard Fedora repositories should not feel like a new desktop feature, and there is no official evidence in the supplied release material that RPM 6.0 delivers a general performance improvement.
Users with third-party repositories should pay more attention. A repository that relies on custom signing keys, outdated RPM libraries, package-format assumptions, or scripts that parse RPM output may expose compatibility issues even when standard Fedora packages work normally.
Who should test carefully before upgrading?
- Administrators with custom repositories: verify repository metadata, package signatures, key rotation, and installation behavior.
- Organizations with bespoke signing infrastructure: test GnuPG-specific commands, key imports, fingerprints, and any Sequoia-based workflow.
- Developers maintaining automation: inspect scripts that parse signature output, key IDs, package headers, or diagnostic text.
- Systems using older RPM libraries: confirm that package inspection, unpacking, verification, and installation all behave as required.
- Users with many external repositories: test the upgrade in a non-production system before applying it broadly.
Fedora’s normal release-upgrade process remains the appropriate path for a standard Fedora installation. The RPM change increases the importance of testing custom integrations, not the need for a special end-user migration procedure.
What do packagers and tooling authors need to review?
Packagers and tooling authors should review signing workflows, key-ID assumptions, package-format selection, RPM output parsing, and RPM 6.0 compatibility notes. The upstream release notes identify several areas that can affect build systems even when Fedora’s default package output remains v4.
Signing and key-management scripts
Scripts that assume short key IDs may need adjustment because RPM 6.0 favors full key IDs or fingerprints in relevant operations. Custom %__gpg_sign_cmd overrides may not behave as they did with older RPM versions, especially when they depend on GnuPG-specific invocation details or output.
Signing pipelines should test key import, key updates, single-signature and multiple-signature packages, verification failures, and the exact diagnostics consumed by automation. A successful manual signing test is not enough if a build service parses command output or uses a custom signing wrapper.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- GOOD VALUE PACKAGE - 1 Pack 32GB Memory Stick USB 2.0 Flash Drives with great cost performance and high quality.
- BIG CAPACITY - The available capacity: 29.10GB-29.8GB, You can save the data of movies, music, photos, designs, programs, manuals, handouts in a high speed.Good performance in digital data storing, transferring and sharing with families, friends, workmates, clients and machines.
- EASY TO USE & PLUG AND WORK - Support windows 7 / 8 / 10 / Vista / XP / 2000 / ME / NT Linux and Mac OS, Compatible with USB2.0 and below.
- TWISTTURN DESIGN & EASY CARRY - The metal clip rotates 360° round the ABS plastic body which with rubber oil skin feeling finish. The capless design can avoid lossing of cap, and providing efficient protection to the USB port.
- WARRANTY & SUPPORT - SIMMAX logo is laser printed on the USB connector surface, our products are of good quality and we promise that any problem about the product within one year since you buy.
Package-format controls
Tools that create or inspect packages should account for the difference between the RPM implementation and the generated package format. The %_rpmformat macro is relevant when a build environment must intentionally control whether it produces an older v4 package or a v6 package.
Fedora 43’s default was v4, but an individual build system may have different settings or goals. Package consumers should also avoid assuming that an RPM 6.0-built package is necessarily an RPM v6 file.
Build dependencies and language behavior
Building RPM 6.0 itself requires a C++20 compiler along with other updated build dependencies. That requirement primarily affects people building RPM or maintaining RPM-based build environments, rather than ordinary Fedora package consumers.
RPM 6.0 also disables posix.fork() in Lua for packages built with RPM 6.0. The function remains available for packages built with RPM 4.20 or older. Lua-based package scripts that depend on process forking should therefore be reviewed and tested against the RPM version used to build the package.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteExternal dependency-generator mode is unsupported for v6 packages. Tool authors producing or analyzing v6 packages should consult the RPM 6.0 release notes rather than treating v6 as a transparent replacement for v4.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Who is Jef Spaleta?
Jef Spaleta is a longtime Fedora contributor who became Fedora Project Leader after Matthew Miller’s planned transition in 2025. Fedora announced Spaleta as Miller’s successor on April 2, 2025. Spaleta had participated in the early Fedora community, including the fedora.us era, and served on the Fedora Board from July 2007 through the end of 2008.
The transition was planned rather than an abrupt change in project ownership. Spaleta was expected to begin full-time at Red Hat in May, with the formal handoff planned for Flock in early June. Fedora’s announcement introducing Jef Spaleta gives the transition timeline and background.
By the 2025 Fedora conference, Fedora coverage referred to Matthew Miller as the former FPL and Jef Spaleta as the project’s new leader at that time. As of August 18, 2026, that wording should be understood historically: Spaleta’s appointment was part of the 2025 leadership transition associated with the Fedora 43 release period, not a new announcement.
Best Value
- 【16GB Flash Drive】USB flash drives with 16GB capacity, meet your needs of daily use on work, school, home and travelling for photos, music, videos, files storage and transfer. IMEASON thumb drives can be used to store different files, easy to data backup.
- 【Metal Swivel Cap Design】USB thumb drive is metal swivel cover provides extra protection for the usb thumbdrive connector, no usb drive cap to lose; keychain design makes it easier to carry without worrying lose it.
- 【Wide Compatibility】USB drive supports Windows 7/8/10/11 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, also Supports USB 2.0 and 1.1 ports. USB Stick support TV, desktop, notebook computer, car, audio and other device. The USB Memory Stick is your great data storage and transfer companion with traveling and working.
- 【Easy to use】usb memory stick is plug and play without any software installation. Just simply plug the Flashdrive into the port of your USB-compatible devices such as computer, laptop to start data storage or transmission.
- 【What You Get】16 GB USB Flash Drive Thumb Drive, The default format of the usb storage flash drive is FAT32.
Why did the leadership transition matter?
The leadership transition mattered because Fedora moved from one experienced community leader to another while continuing its broader work on contributor health, project direction, and technical modernization. Spaleta was not an outside executive brought in to direct the RPM implementation; he was an established Fedora participant returning to a leadership role.
The Fedora Project Leader represents Fedora’s community and helps coordinate project direction, but the FPL does not personally own every technical change. Fedora’s RPM 6.0 change proposal identifies Panu Matilainen as the owner of the RPM 6.0 work. The RPM implementation and the FPL transition should therefore be described as parallel developments, not as a technical project directed by Spaleta.
At Flock 2025, Spaleta presented a Fedora Strategy 2028 discussion focused on mentorship, contributor growth, and aligning community efforts. The Flock 2025 recap places that strategy discussion in the context of the conference and the leadership handoff.
The continuity is significant. Fedora’s leadership changed, but the project retained a leader with historical knowledge of Fedora’s community and governance. The strategic emphasis on mentorship and contributor growth also addresses a different layer of project health from RPM’s cryptographic and packaging work: one concerns how people participate and collaborate, while the other concerns how software is built, signed, verified, and delivered.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWas Fedora 43 a major RPM change?
Yes, Fedora 43 was a major RPM implementation and security-infrastructure milestone, but it was not a complete Fedora-wide migration to RPM v6 packages. The distinction explains why the release could be important to RPM developers and packagers without producing a dramatic change for a typical desktop user.
| Audience | Likely significance of Fedora 43’s RPM 6.0 adoption | Recommended response |
|---|---|---|
| Typical Fedora desktop user | Mostly an underlying security, signing, and compatibility improvement. | Use the normal update path and watch for third-party repository or key errors. |
| Server administrator | Greater relevance if systems use custom repositories, signing keys, old RPM integrations, or automation. | Test upgrades and verify repository and signing workflows. |
| Package maintainer | Potential changes to package signing, key identifiers, macros, Lua behavior, and format selection. | Review the RPM 6.0 compatibility notes and build/test packages in the target environment. |
| Tooling author | Potentially significant output, format, API, and compatibility changes. | Test v4 and v6 packages, full fingerprints, signature failures, and older RPM consumers. |
| Fedora contributor | A release-period combination of technical modernization and leadership continuity. | Track Fedora’s project direction and contributor-growth work separately from RPM implementation details. |
Fedora 43’s most important lesson is that a major version number does not by itself describe the entire migration policy. RPM 6.0 supplied the new capabilities; Fedora 43 deliberately introduced them while retaining v4 package generation and postponing the upstream enforced-signature default. That staged approach reduced immediate ecosystem disruption while giving Fedora and its tooling ecosystem time to adapt.
Frequently Asked Questions
Did Fedora 43 use RPM v6 packages by default?
No. Fedora 43 shipped the RPM 6.0 software stack but continued generating RPM v4 packages by default. RPM 6.0’s support for the RPM v6 format was separate from Fedora’s default package-generation policy.
What is the biggest practical benefit of RPM 6.0 in Fedora 43?
The biggest practical benefit is modernized package authenticity and integrity handling, including newer OpenPGP capabilities, multiple signatures, full key fingerprints, additional digests, and alternative signing support. Ordinary users are more likely to see the effects in verification and tooling than in the desktop interface.
Recommended Free Tools
Did RPM 6.0 make Fedora 43 reject unsigned packages automatically?
No. Upstream RPM 6.0 enabled enforced signature checking by default, but Fedora 43 explicitly deferred adopting that upstream default. Fedora’s actual verification behavior also depends on repository and package-management configuration.
Who replaced Matthew Miller as Fedora Project Leader?
Jef Spaleta replaced Matthew Miller as Fedora Project Leader during the 2025 transition. Fedora announced Spaleta as Miller’s successor on April 2, 2025, with the formal handoff planned around Flock 2025.
The Bottom Line
Bottom line: Fedora 43 introduced RPM 6.0 as a foundational packaging and security upgrade, not as an instant conversion of every Fedora package to RPM v6. Users received the newer RPM engine through the normal Fedora stack, while packagers and tooling authors faced the more important work of testing signatures, key handling, package formats, and compatibility. In the same 2025 release window, Jef Spaleta succeeded Matthew Miller as Fedora Project Leader—a related moment of project continuity, but not the cause or owner of the RPM implementation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
