In an ongoing effort to improve our security we have decided to disallow
any ssh private keys from being housed on any fedora-maintained system.
No user should have ever needed to upload an ssh private key, the public
keys are, of course just fine and required. However, on the off-chance
that someone has done this, we'll be performing audits of user homedirs
looking for ssh private keys.
If we find them we'll remove them and then remove the owning-user's ssh
public key from the Fedora Account System (FAS), forcing them to upload
a new one. We're taking this additional step to make sure that the
public key in FAS is not vulnerable due to their private key being
potentially exposed on a shared system.
You can refer to the allowable content section of the fedorapeople faq.
https://fedoraproject.org/wiki/Infrastructure/fedorapeople.org#Allowable_co…
These rules (and more), apply to our administrative systems and home
directories.
Thank You,
Fedora Infrastructure Team
Here are the latest changes to the Fedora Packaging Guidelines:
---
The section of the Packaging Guidelines regarding Compiler Flags has
been updated and improved, most notably, to document handling of PIE
enabled packages.
https://fedoraproject.org/wiki/Packaging:Guidelines#Compiler_flags
---
The prohibition against unnecessary explicit library requires has been
updated with an example of when explicit library requires are useful and
allowed. The example addresses packages that use features of a library
added after the library initially adopted its current SONAME.
https://fedoraproject.org/wiki/Packaging:Guidelines#Explicit_Requires
---
An additional md5 implementation was added to the list of bundling
exceptions:
https://fedoraproject.org/w/index.php?title=Packaging:No_Bundled_Libraries&…
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
Many thanks to Kevin Fenzi, Adam Jackson, and all of the members of the
FPC, for assisting in drafting, refining, and passing these guidelines.
As a reminder: The Fedora Packaging Guidelines are living documents! If
you find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
Thanks,
~spot
It is once again time to choose the release name for the next Fedora
release. Potential names will be accepted for consideration beginning
September 13th (in other words, NOW) through September 10. Please
submit your best ideas to the Fedora wiki at the address below:
https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_17
Please note that you *must* follow the instructions and guidelines at
the page listed above if you want your name to be considered. For
instance, there must be an "is-a" link between the name Verne (from
Fedora 16) and the name you suggest. That link must be different than
previous links for Fedora release names. Also, we ask that you please
conduct the required searches for brand and trademark names that might
cause us problems.
Read the full guidelines at the wiki page listed above, where you can
also find full schedule details for the release naming process.
For those of you interested in reviewing the history of Fedora release
names, there is an appropriately named wiki page for doing so at
http://fedoraproject.org/wiki/History_of_Fedora_release_names
Please try to pick a name that is fun and creative. Don't delay... do
it today! We all want an awesome name for Fedora 17!
--
Jared Smith
Fedora Project Leader