Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
T
tails
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
947
Issues
947
List
Boards
Labels
Service Desk
Milestones
Merge Requests
12
Merge Requests
12
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
tails
tails
Commits
fe65fafd
Commit
fe65fafd
authored
Mar 08, 2016
by
anonym
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add security advisory for Tails 2.2.
parent
be294703
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
24 additions
and
0 deletions
+24
-0
wiki/src/security/Numerous_security_holes_in_2.0.1.mdwn
wiki/src/security/Numerous_security_holes_in_2.0.1.mdwn
+24
-0
No files found.
wiki/src/security/Numerous_security_holes_in_2.0.1.mdwn
0 → 100644
View file @
fe65fafd
[[!meta date="Sun, 6 Mar 2016 12:34:56 +0000"]]
[[!meta title="Numerous security holes in Tails 2.0.1"]]
[[!tag security/fixed]]
Several security holes that affect Tails 2.0.1 are now fixed in Tails 2.2.
We **strongly** encourage you to [[upgrade to Tails 2.2|news/version_2.2]] as soon as possible.
Details
=======
* Tor Browser: [[!mfsa2016 XXX_TBA_XXX]]
* graphite2: [[!debsa2016 3479]]
* glibc: [[!debsa2016 3481]]
* libreoffice: [[!debsa2016 3482]]
* cpio: [[!debsa2016 3483]]
* libssh2: [[!debsa2016 3487]]
* pillow: [[!debsa2016 3499]]
* openssl: [[!debsa2016 3500]]
* perl: [[!debsa2016 3501]]
* linux: [[!debsa2016 3503]]
* libav: [[!debsa2016 3506]]
* jasper: [[!debsa2016 3508]]
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment