1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
Agenda for Security Team Meeting
--------------------------------
Workflow
========
- Opening up the security process further to allow maintainers of packages with
frequent issues to release updates themselves
- Updates need to be reviewed/acked by sec team members
- Requires changes to dak to no longer require access to security-master,
e.g. by using a mechanism similar to allowing a DM to upload and sending
error messages to the signer of the upload (already requested by Thijs)
- Requires changes to debian-security-announce
- Is dsa-needed an improvement? What shall we do with embargoed issues?
- Ditch RT?
- Draft new people, possible candidates
- Drop "Problem type" and "Vulnerability" from DSAs? Mostly
duplicating information from vulnerability databases
Archive tools
=============
- Compile a list of issues we want to see fixed
- Do we really need the embargo queue? This would simplify dak/FTP situations immensely.
- Or rather, do we need an unembargoed queue? we still have different
UNIX groups and nowadays all uploads end up in the embargoed queue
- Make it simple to release packages for others to test, e.g. an aptable security queue
Tracker
=======
- Add a new status to differentiate between "no-dsa, if the maintainer wants
to fix in a point update go ahead" and "no-dsa, was ignored because it's
possible to backport".
- Automatic weekly status on open issues sent to maintainers (catches
issues which fell through the cracks, like CVE-2013-2236)
- Check open bugs in the BTS, check bugs against security-tracker pseudo package
- Support for consistency checks on source package names, e.g linux-2.6/linux
or all of the ruby packages
Infrastructure
==============
- Availability in general. sec-master going down, alioth going down
(again), what are the implications and what can be done about it.
- Migrate to git?
Documentation
=============
- Work on proper documentation how people can contribute
Others
======
- d-d-a mail for file collecting willing testers for exotic setups
- Compile a list of test instructions for key packages
- Compile a list of problemtic packages in jessie for the release team
Distribution hardening
======================
- hardening build flags:
- release goal status
- PIC/PIE situation
- adding new flags to dpkg-buildflags? (-fstack-protector-strong, others?)
- planning for release goal speedup? [corsac: what does it means?]
- hidepid by default
- mount flags and default partitioning
- default open ports
- kernel hardening: memory protections (heap/stack/...), reducing the attack surface
- Require fs.protected_symlinks? (enabled by default in Wheezy, kfreebsd doesn't support it)
LTS
===
- Setup and organisation
- Gather a specific list of people interested in contributing (e.g. credative already stepped forward)
.. vim: filetype=rst:
|
