1 |
Had a conversation with aoz in the hardened IRC room yesterday, |
2 |
discussing how non-tech types such as I might help the hardened effort; |
3 |
|
4 |
1. He suggested that Bugzilla took a lot of time. How could some of that |
5 |
time be outsource to a non-techie? |
6 |
|
7 |
2. We discussed the possibility of incorporating links to white-paper |
8 |
"status reports" within the current, very-high-quality, |
9 |
reluctant-to-tamper-with Gentoo http pages. |
10 |
|
11 |
STM that Gentoo newbies and others simply checking Gentoo Hardened out |
12 |
first, go first to http://www.gentoo.org/proj/en/hardened/. So that |
13 |
would be an ideal place to put a link(s) to a white paper summary of |
14 |
where the project is, and what its next step is. |
15 |
|
16 |
That white paper could be easily updated by a newbie, helping with the |
17 |
proof reading!? |
18 |
|
19 |
3. IIUC, the current status is to wait for "upstream" (the gcc folks?) |
20 |
to successfully incorporate ssp into c++ compilations? And also that |
21 |
with rare exception, little is loss using the older 3.4.6 compiler? |
22 |
In those rare cases, gcc can be "slotted" so that 3.4.6 would be the |
23 |
default, but 4.x could be called to duty when 3.4.6 won't work? |
24 |
|
25 |
Might be useful to note this in the white paper. |
26 |
|
27 |
|
28 |
|
29 |
|
30 |
|
31 |
-- |
32 |
gentoo-hardened@l.g.o mailing list |