3 <meta http-equiv=
"Content-Type" content=
"text/html">
4 <title>FreeS/WAN mailing lists
</title>
6 content=
"Linux, IPsec, VPN, security, FreeSWAN, mailing, list">
9 Written by Sandy Harris for the Linux FreeS/WAN project
10 Freely distributable under the GNU General Public License
12 More information at www.freeswan.org
13 Feedback to users@lists.freeswan.org
16 RCS ID: $Id: mail.html,v 1.1 2004/03/15 20:35:24 as Exp $
17 Last changed: $Date: 2004/03/15 20:35:24 $
18 Revision number: $Revision: 1.1 $
20 CVS revision numbers do not correspond to FreeS/WAN release numbers.
25 <h1><a name=
"lists">Mailing lists and newsgroups
</a></h1>
27 <h2><a name=
"list.fs">Mailing lists about FreeS/WAN
</a></h2>
29 <h3><a name=
"projlist">The project mailing lists
</a></h3>
31 <p>The Linux FreeS/WAN project has several email lists for user support, bug
32 reports and software development discussions.
</p>
34 <p>We had a single list on clinet.fi for several years (Thanks, folks!), then
35 one list on freeswan.org, but now we've split into several lists:
</p>
38 href=
"mailto:users-request@lists.freeswan.org?body=subscribe">users
</a></dt>
40 <li>The general list for discussing use of the software
</li>
41 <li>The place for seeking
<strong>help with problems
</strong> (but
42 please check the
<a href=
"faq.html">FAQ
</a> first).
</li>
43 <li>Anyone can post.
</li>
47 href=
"mailto:bugs-request@lists.freeswan.org?body=subscribe">bugs
</a></dt>
49 <li>For
<strong>bug reports
</strong>.
</li>
50 <li>If you are not certain what is going on -- could be a bug, a
51 configuration error, a network problem, ... -- please post to the
52 users list instead.
</li>
53 <li>Anyone can post.
</li>
57 href=
"mailto:design-request@lists.freeswan.org?body=subscribe">design
</a></dt>
59 <li><strong>Design discussions
</strong>, for people working on
60 FreeS/WAN development or others with an interest in design and
62 <li>It would be a good idea to read the existing design papers (see
63 this
<a href=
"intro.html#applied">list
</a>) before posting.
</li>
64 <li>Anyone can post.
</li>
68 href=
"mailto:announce-request@lists.freeswan.org?body=subscribe">announce
</a></dt>
70 <li>A
<strong>low-traffic
</strong> list.
</li>
71 <li><strong>Announcements
</strong> about FreeS/WAN and related
73 <li>All posts here are also sent to the users list. You need not
74 subscribe to both.
</li>
75 <li>Only the FreeS/WAN team can post.
</li>
76 <li>If you have something you feel should go on this list, send it to
77 <var>announce-admin@lists.freeswan.org
</var>. Unless it is obvious,
78 please include a short note explaining why we should post it.
</li>
82 href=
"mailto:briefs-request@lists.freeswan.org?body=subscribe">briefs
</a></dt>
84 <li>A
<strong>low-traffic
</strong> list.
</li>
85 <li><strong>Weekly summaries
</strong> of activity on the users
87 <li>All posts here are also sent to the users list. You need not
88 subscribe to both.
</li>
89 <li>Only the FreeS/WAN team can post.
</li>
94 <p>To subscribe to any of these, you can:
</p>
96 <li>just follow the links above
</li>
97 <li>use our
<a href=
"http://www.freeswan.org/mail.html">web
99 <li>send mail to
<var>listname
</var>-request@lists.freeswan.org with a
100 one-line message body
"subscribe"</li>
103 <p>Archives of these lists are available via the
<a
104 href=
"http://www.freeswan.org/mail.html">web interface
</a>.
</p>
106 <h4><a name=
"which.list">Which list should I use?
</a></h4>
108 <p>For most questions, please check the
<a href=
"faq.html">FAQ
</a> first, and
109 if that does not have an answer, ask on the users list.
"My configuration
110 doesn't work." does not belong on the bugs list, and
"Can FreeS/WAN do
111 such-and-such" or
"How do I configure it to..." do not belong in design
114 <p>Cross-posting the same message to two or more of these lists is
115 discouraged. Quite a few people read more than one list and getting multiple
116 copies is annoying.
</p>
118 <h4><a name=
"policy.list">List policies
</a></h4>
120 <p><strong>US citizens or residents are asked not to post code to the lists,
121 not even one-line bug fixes
</strong>. The project cannot accept code which
122 might entangle it in US
<a href=
"politics.html#exlaw">export
123 restrictions
</a>.
</p>
125 <p>Non-subscribers can post to some of these lists. This is necessary;
126 someone working on a gateway install who encounters a problem may not have
127 access to a subscribed account.
</p>
129 <p>Some spam turns up on these lists from time to time. For discussion of why
130 we do not attempt to filter it, see the
<a href=
"faq.html#spam">FAQ
</a>.
131 Please do not clutter the lists with complaints about this.
</p>
133 <h3><a name=
"archive">Archives of the lists
</a></h3>
135 <p>Searchable archives of the old single list have existed for some time. At
136 time of writing, it is not yet clear how they will change for the new
137 multi-list structure.
</p>
139 <li><a href=
"http://www.sandelman.ottawa.on.ca/linux-ipsec">Canada
</a></li>
140 <li><a href=
"http://www.nexial.com">Holland
</a></li>
143 <p>Note that these use different search engines. Try both.
</p>
145 <p>Archives of the new lists are available via the
<a
146 href=
"http://www.freeswan.org/mail.html">web interface
</a>.
</p>
148 <h2><a name=
"indexes">Indexes of mailing lists
</a></h2>
150 <p><a href=
"http://paml.net/">PAML
</a> is the standard reference for
151 <strong>P
</strong>ublicly
<strong>A
</strong>ccessible
152 <strong>M
</strong>ailing
<strong>L
</strong>ists. When we last checked, it had
153 over
7500 lists on an amazing variety of topics. It also has FAQ information
154 and a search engine.
</p>
156 <p>There is an index of
<a
157 href=
"http://oslab.snu.ac.kr/~djshin/linux/mail-list/index.shtml">Linux
158 mailing lists
</a> available.
</p>
161 href=
"http://xforce.iss.net/maillists/otherlists.php">computer security
162 mailing lists
</a>, with descriptions.
</p>
164 <h2><a name=
"otherlists">Lists for related software and topics
</a></h2>
166 <p>Most links in this section point to subscription addresses for the various
167 lists. Send the one-line message
"subscribe <var>list_name</var>" to
168 subscribe to any of them.
</p>
170 <h3>Products that include FreeS/WAN
</h3>
172 <p>Our introduction document gives a
<a href=
"intro.html#products">list of
173 products that include FreeS/WAN
</a>. If you have, or are considering, one of
174 those, check the supplier's web site for information on mailing lists for
177 <h3><a name=
"linux.lists">Linux mailing lists
</a></h3>
180 href=
"mailto:majordomo@vger.kernel.org">linux-admin@vger.kernel.org
</a>,
181 for Linux system administrators
</li>
183 href=
"mailto:netfilter-request@lists.samba.org">netfilter@lists.samba.org
</a>,
184 about Netfilter, which replaces IPchains in kernels
2.3.15 and later
</li>
186 href=
"mailto:security-audit-request@ferret.lmh.ox.ac.uk">security-audit@ferret.lmh.ox.ac.uk
</a>,
187 for people working on security audits of various Linux programs
</li>
189 href=
"mailto:securedistros-request@humbolt.geo.uu.nl">securedistros@humbolt.geo.uu.nl
</a>,
190 for discussion of issues common to all the half dozen projects working on
191 secure Linux distributions.
</li>
194 <p>Each of the scure distribution projects also has its own web site and
195 mailing list. Some of the sites are:
</p>
197 <li><a href=
"http://bastille-linux.org/">Bastille Linux
</a> scripts to
198 harden Redhat, e.g. by changing permissions and modifying inialisation
200 <li><a href=
"http://immunix.org/">Immunix
</a> take a different approach,
201 using a modified compiler to build kernel and utilities with better
202 resistance to various types of overflow and exploit
</li>
203 <li>the
<a href=
"glossary.html#NSA">NSA
</a> have contractors working on a
204 <a href=
"glossary.html#SElinux">Security Enhanced Linux
</a>, primarily
205 adding stronger access control mechanisms. You can download the current
206 version (which interestingly is under GPL and not export resrtricted) or
207 subscribe to the mailing list from the
<a
208 href=
"http://www.nsa.gov/selinux">project web page
</a>.
</li>
211 <h3><a name=
"ietf">Lists for IETF working groups
</a></h3>
213 <p>Each
<a href=
"glossary.html#IETF">IETF
</a> working group has an associated
214 mailing list where much of the work takes place.
</p>
217 href=
"mailto:majordomo@lists.tislabs.com">ipsec@lists.tislabs.com
</a>,
219 href=
"http://www.ietf.org/html.charters/ipsec-charter.html">working
220 group
</a>. This is where the protocols are discussed, new drafts
221 announced, and so on. By now, the IPsec working group is winding down
222 since the work is essentially complete. A
<a
223 href=
"http://www.sandelman.ottawa.on.ca/ipsec/">list archive
</a> is
225 <li><a href=
"mailto:ipsec-policy-request@vpnc.org">IPsec policy
</a> list,
226 and its
<a href=
"http://www.vpnc.org/ipsec-policy/">archive
</a></li>
227 <li><a href=
"mailto:ietf-ipsra-request@vpnc.org">IP secure remote
228 access
</a> list, and its
<a
229 href=
"http://www.vpnc.org/ietf-ipsra/mail-archive/">archive
</a></li>
232 <h3><a name=
"other">Other mailing lists
</a></h3>
235 href=
"mailto:ipc-announce-request@privacy.org">ipc-announce@privacy.org
</a>
236 a low-traffic list with announcements of developments in privacy,
237 encryption and online civil rights
</li>
238 <li>a VPN mailing list's
<a
239 href=
"http://kubarb.phsx.ukans.edu/~tbird/vpn.html">home page
</a></li>
242 <h2><a name=
"newsgroups">Usenet newsgroups
</a></h2>
245 <li>sci.crypt.research
</li>
246 <li>comp.dcom.vpn
</li>
247 <li>talk.politics.crypto
</li>