Linux security workgroup usage of kernel-hardening mailing list
There was a discussion about forming a Linux security workgroup at the 2012 Linux Security Summit: http://kernsec.org/wiki/index.php/Linux_Security_Summit_2012.
The charter of the workgroup is to provide on-going security verification of Linux kernel subsystems in order to assist in securing the Linux Kernel and maintain trust and confidence in the security of the Linux ecosystem.
This may include, but is not limited to, topics such as tooling to assist in securing the Linux Kernel, verification and testing of critical subsystems for vulnerabilities, security improvements for build tools, and providing guidance for maintaining subsystem security.
Would it be okay if we used the kernel-hardening mailing list for communication? If our traffic ever gets to be too much we could get our own list.
Signature · 2 lines
Regards, Corey Bryant
Quoted 5 lines · Corey Bryant
The charter of the workgroup is to provide on-going security verification of Linux kernel subsystems in order to assist in securing the Linux Kernel and maintain trust and confidence in the security of the Linux ecosystem.
Quoted 7 lines
This may include, but is not limited to, topics such as tooling to assist in securing the Linux Kernel, verification and testing of critical subsystems for vulnerabilities, security improvements for build tools, and providing guidance for maintaining subsystem security.
Would it be okay if we used the kernel-hardening mailing list for communication?
Of course! Please do.
Quoted 1 line
If our traffic ever gets to be too much
This would be a good problem to have (well, assuming that list traffic correlates with actual progress).
Alexander
Quoted 11 lines · Solar Designer
Quoted 10 lines · Corey Bryant
The charter of the workgroup is to provide on-going security verification of Linux kernel subsystems in order to assist in securing the Linux Kernel and maintain trust and confidence in the security of the Linux ecosystem.
This may include, but is not limited to, topics such as tooling to assist in securing the Linux Kernel, verification and testing of critical subsystems for vulnerabilities, security improvements for build tools, and providing guidance for maintaining subsystem security.
Quoted 5 lines
Quoted 2 lines
Would it be okay if we used the kernel-hardening mailing list for communication?
Of course! Please do.
Excellent, thanks! Should we tag our subjects with anything? I was thinking "lswg: ".
Quoted 4 lines
Quoted 1 line
If our traffic ever gets to be too much
This would be a good problem to have (well, assuming that list traffic correlates with actual progress).
:)
Quoted 5 lines
Alexander
Signature · 2 lines
Regards, Corey Bryant
Quoted 2 lines · Corey Bryant
Excellent, thanks! Should we tag our subjects with anything? I was thinking "lswg: ".
It's your call, but I doubt that such tagging would be of much/any use. The topics you have listed are some of what's supposed to be discussed on this list, and some of the threads may proceed to other related topics, which are not limited to the focus of lswg (but the tags would remain). Similarly, postings by non-lswg folks may be relevant to you. I think it'd be too difficult/unreasonable to keep the separation.
Alexander
Quoted 4 lines · Solar Designer
Quoted 2 lines · Corey Bryant
Excellent, thanks! Should we tag our subjects with anything? I was thinking "lswg: ".
Quoted 11 lines
It's your call, but I doubt that such tagging would be of much/any use. The topics you have listed are some of what's supposed to be discussed on this list, and some of the threads may proceed to other related topics, which are not limited to the focus of lswg (but the tags would remain). Similarly, postings by non-lswg folks may be relevant to you. I think it'd be too difficult/unreasonable to keep the separation.
Alexander
Ok we'll go without the tag then. Thanks again!
Signature · 2 lines
Regards, Corey Bryant