KnowledgeBase
| Size: 1927 Comment: add links to feature details | Size: 2971 Comment:  | 
| Deletions are marked like this. | Additions are marked like this. | 
| Line 5: | Line 5: | 
| == Security updates == | |
| Line 6: | Line 7: | 
| === Announcements === * Official [[https://www.ubuntu.com/usn/|Ubuntu Security Announcements]] * Unofficial translations of Ubuntu Security Announcements: * [[http://blogs.media-tips.com/bernard.opic/category/ubuntu-security-notices/|French]] | |
| Line 7: | Line 12: | 
| {{{ This page is still very much place-holder. If you have time, please update it with more information. }}} | === Media coverage === In order to stay secure, Ubuntu users should simply apply all Ubuntu security updates to their systems when they become available. | 
| Line 11: | Line 15: | 
| == Security updates == | For some vulnerabilities that are highlighted by the media, we've provided additional information as part of our !KnowledgeBase: * [[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GHOST|GHOST (CVE-2015-0235)]] | 
| Line 15: | Line 20: | 
| * [[http://people.canonical.com/~ubuntu-security/cve/|Ubuntu CVE Tracker]] (web view) | |
| Line 20: | Line 26: | 
| * [[SecurityUpdateProcedures| Security Update Procedures]] | * [[SecurityTeam/UpdateProcedures| Security Update Procedures]] | 
| Line 26: | Line 32: | 
| * [[https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures#Preparing%20an%20update|How to prepare an updated package]] | |
| Line 27: | Line 34: | 
| * [[SecurityTeam/BuildEnvironment|schroot/sbuild setup]] * [[SecurityTeam/TestingEnvironment|virtual machine setup]] | |
| Line 35: | Line 44: | 
| (FAQ could link to Knowledge{{{}}}Base) * policy on local DoS * policy on root passwords/sudo * policy on open network ports * policy on sudo * policy on home directory permissions | * [[SecurityTeam/Policies|Ubuntu Security Policies]] * [[ApparmorProfileMigration|Creating enforcing AppArmor profiles policy]] | 
| Line 43: | Line 48: | 
| * [[Security/Features|Feature Matrix]] (for all releases since Dapper, see the [[Security/Features/Historical|Historical Feature Matrix]].) | |
| Line 48: | Line 54: | 
| == Process == * [[SecurityTeam/BugTriage|Bug Triage]] * [[SecurityTeam/ReleaseCycle|Release Cycle Actions]] | 
Security updates
Announcements
- Official Ubuntu Security Announcements 
- Unofficial translations of Ubuntu Security Announcements:
Media coverage
In order to stay secure, Ubuntu users should simply apply all Ubuntu security updates to their systems when they become available.
For some vulnerabilities that are highlighted by the media, we've provided additional information as part of our KnowledgeBase:
Vulnerability Resources
- Ubuntu CVE Tracker (web view) 
Update processes
- StableReleaseUpdates (SRU) 
Update techniques
- How to handle backporting security updates
- How to test the update - Proof of Concept (PoC)
- Build test suites (eg, 'make check')
 
- ABI compatibility (eg, check-symbols, nm)
- Checklists
Policies
Features
- Feature Matrix (for all releases since Dapper, see the Historical Feature Matrix.) 
- AppArmor docs 
- SELinux docs 
Process
Problems
- DebuggingSecurity for bug reports 
- DebuggingApparmor for bug reports dealing with AppArmor profiles 
SecurityTeam/KnowledgeBase (last edited 2025-04-17 11:05:59 by yhontyk)