Search results

= FPC meeting process = ...| This guide]] explains how to manage and run the [[Packaging_Committee | FPC]] IRC meeting.

* technical issues (FPC reports, features) are approved by FESCo == Revert the recently published Flag policy ==

= NSS enforces the system-wide crypto policy <!-- The name of your change proposal --> = ...Fedora, NSS is enhanced to respect the settings of the system-wide crypto policy as well.

= Standardized Passphrase Policy = .../passwords, others different rules. This change would create a common base policy for as many of these applications as possible, allowing for local users or

= Java/OpenJDK enforces the system-wide crypto policy <!-- The name of your change proposal --> = ...nes, OpenJDK is enhanced to respect the settings of the system-wide crypto policy as well.

= SELinux policy store migration = ...roject release 2015-02-02 includes a change of the location of the SELinux policy store, which defaults to /var/lib/selinux/.

= Crypto policy support for Kerberos <!-- The name of your change proposal --> = ...cies system wide crypto policy] and Kerberos (libkrb5) should respect that policy and adjust its crypto-related configuration based on it.

= Make selinux-policy up-to-date with the latest kernel <!-- The name of your change proposal --> ...gnizes them, can boot without an error message, and use them in the actual policy for confined services.

= OpenSSH Server Crypto Policy <!-- The name of your change proposal --> = OpenSSH clients follow the system-wide crypto policy [https://fedoraproject.org/wiki/Changes/OpenSSH_Crypto_Policy since Fedora

= OpenSSH Crypto Policy (Client) = For more information about Crypto Policy, see the appropriate wiki page [[Changes/CryptoPolicy]] describing the conc

...18] and by policy, presets are carried by the fedora-release package. This policy is now extended to user units. ** submit a proposal to FPC to update the guidelines (essentially to say "... and the same for user ser

= Move /var/run selinux-policy entries to /run = ...m runtime files moved from /var/run to /run some 10 years ago [1], but the policy has been managed since then in a way that keeps the old entries and have up

Both FESCo and FPC agreed to this process, which is in force for Fedora 31 ...thon2 is deprecated, so adding new dependencies on it is generally against policy).

= Make selinux-policy up-to-date with the latest kernel <!-- The name of your change proposal --> Add new permissions, classes, and capabilities to the selinux policy so that system recognizes them and boots without an error message.

* Discussion from fedora-devel-list about expanding [[PackageMaintainers/Policy]] | style="color: #42427e" | next topic [[PackageMaintainers/Policy]]

===[[Changes/MAC Address Policy none | MAC Address Policy none]]=== the policy so that we use Link.MACAddressPolicy=none for bond/bridge/team devices.

= Policy for Modules in Fedora and Fedora ELN = ...s, members of the Modularity WG and FESCo have been working to establish a policy for module inclusion in Fedora. We now have a proposal that FESCo requested

* Proposal owners: flip that switch in the DEFAULT policy, provide transitional policies for testing the change. Test your applications with TEST-FEDORA41 policy.

...ct.org/en-US/packaging-guidelines/#_brp_buildroot_policy_scripts buildroot policy] script by default. This will make the RPM build fail once a broken RPATH w ...ct.org/en-US/packaging-guidelines/#_brp_buildroot_policy_scripts buildroot policy scripts], if the script provides incorrect results for your package. Simply

...low the new rules. You can also see a list of packages breaking the naming policy on [http://fedora.portingdb.xyz/namingpolicy/ PortingDB]. ...ckage_naming guidelines], [https://pagure.io/packaging-committee/issue/685 fpc]