|
Research
Skip Research Menus
Research MenuSecurity Enhanced Linux What's New Frequently Asked Questions Background Documents License Download Participating Mail List Archives Remaining Work Contributors Related Work Press Releases Information Assurance Research NIARL In-house Research Areas Mathematical Sciences Program Sabbaticals Computer & Information Sciences Research Technology Transfer Advanced Computing Advanced Mathematics Communications & Networking Information Processing Microelectronics Other Technologies Technology Fact Sheets Publications Related Links |
SELinux Mailing ListRe: Sourceforge
From: Will Dye <willdye_at_dsndata.com>
Date: Wed, 11 Apr 2001 13:16:58 -0500
Mr. Westerman, Thanks for taking this one. I'd love to help, but I'm overextended already. One suggestion: you might want to create a CVS subdirectory reserved for ad-hoc file submissions by people who are not registered developers. Then just put instructions on the web page for making an anonymous CVS submission. Ah, I just thought of another suggestion. You'll probably also want to disable most of the SourceForge services, such as the surveys, until you have a use for them. Unused services tend to confuse new folks. You may even want to disable the SourceForge-hosted mailing lists, and just point people to the NSA list instead. The NSA list is low-volume enough that we probably don't want to split up the conversation yet. Oh, yes; you will probably want a link on your web page to Grant Bayley's Australian mirror site:
http://the.wiretapped.net/security/operating-systems/selinux/
ftp://ftp.wiretapped.net/pub/security/operating-systems/selinux/
I can't think of any other suggestions offhand, but I hope these were at least worth reading. I wish I could help more. Thanks again,
--Will P.S. I just thought of another idea. Contact the NSA guys about this, and see what they think. They might want to join you as admins of the project, so that they can help keep it in sync with new releases from their main site. You probably also want to talk about how to handle multiple variants, by different coders, which may or may not be compatable with other variants. I'm running into a similar situation with my Sourceforge project for tweaks to "Freedom", a well-funded Internet privacy system that was released under the Mozilla 1.1 license. The commercial code is in wide use already, so I don't want to release a variant that has dumb security holes in it. On the other hand, some of the coders just want to experiment freely, and produce demonstrations of principle. The compromise was to make a sort of meta-project, called Tweakdom ("Tweaks to Freedom", http://tweakdom.sourceforge.net). It's just getting underway, so for now it's just one project; but the idea is that it will split off variants as needed. The main project site will point to the various sub-projects, and serve as a unified place for security alerts and such for all the different versions. That's the idea anyway. It's too soon to tell if it will work.
-- |
|
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |












