← Policies/Security Policy You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. This policy describes how security related issues are handled after they have been reported to [mailto:email@example.com firstname.lastname@example.org]. Issues that are brought to the attention of email@example.com are handled discreetly. The issue will be verified and the author/maintainer of the affected code will usually be contacted. If the issue is indeed considered to be a problem the need for an immediate fix is assessed. The security team will also notify affected parties which are known to reuse the affected code. If an immediate fix is not considered necessary a security alert is issued via [mailto:firstname.lastname@example.org email@example.com]. If a fix is considered necessary, KDE release coordinators are contacted and KDE vendor packagers, Linux distributors and other prenotification mailing lists (including [https://mail.kde.org/mailman/listinfo/kde-security-preannounce firstname.lastname@example.org]) are informed once a fix is available that has passed review on [mailto:email@example.com firstname.lastname@example.org]. We then give them a reasonable amount of time to prepare binary packages. After that time we issue a security alert via [mailto:email@example.com firstname.lastname@example.org]. Patches in source form and any available updated binaries are published at the same time. All security alerts are published on http://www.kde.org/info/security/. KDE developers that want to join [mailto:email@example.com firstname.lastname@example.org] can send a motivated request to [mailto:email@example.com firstname.lastname@example.org]. Applications will be evaluated on a case by case basis by the current members. The main criteria is the extent to which someone can be helpful in executing the security policy as described here. That includes a willingness not to disclose issues prematurely. ==Process for the Security Team== * Answer incoming e-mails as soon as possible so people know we are listening to their report * If needed contact people that know the code in question to get the fix done/checked * Get a CVE https://github.com/RedHatProductSecurity/CVE-HOWTO * Contact [https://mail.kde.org/mailman/listinfo/kde-security-preannounce email@example.com] if we think it's important enough that binaries should be out the same moment of the security is disclosed to give distributors some heads up time * Add advisory announcement the website ** Check out svn+ssh://firstname.lastname@example.org/home/kde/trunk/www/sites/www/info/security ** Add new advisory as a txt file ** Edit index.php to add link to the new advisory, commit * Issue security alert via [mailto:email@example.com firstname.lastname@example.org] [[Category:Policies]] Return to Policies/Security Policy. Retrieved from "https://community.kde.org/Policies/Security_Policy"