]> git.ipfire.org Git - thirdparty/strongswan.git/blob - doc/mail.html
- import of strongswan-2.7.0
[thirdparty/strongswan.git] / doc / mail.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
2 <HTML>
3 <HEAD>
4 <TITLE>Introduction to FreeS/WAN</TITLE>
5 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-8859-1">
6 <STYLE TYPE="text/css"><!--
7 BODY { font-family: serif }
8 H1 { font-family: sans-serif }
9 H2 { font-family: sans-serif }
10 H3 { font-family: sans-serif }
11 H4 { font-family: sans-serif }
12 H5 { font-family: sans-serif }
13 H6 { font-family: sans-serif }
14 SUB { font-size: smaller }
15 SUP { font-size: smaller }
16 PRE { font-family: monospace }
17 --></STYLE>
18 </HEAD>
19 <BODY>
20 <A HREF="toc.html">Contents</A>
21 <A HREF="ipsec.html">Previous</A>
22 <A HREF="web.html">Next</A>
23 <HR>
24 <H1><A name="lists">Mailing lists and newsgroups</A></H1>
25 <H2><A name="list.fs">Mailing lists about FreeS/WAN</A></H2>
26 <H3><A name="projlist">The project mailing lists</A></H3>
27 <P>The Linux FreeS/WAN project has several email lists for user support,
28 bug reports and software development discussions.</P>
29 <P>We had a single list on clinet.fi for several years (Thanks, folks!),
30 then one list on freeswan.org, but now we've split into several lists:</P>
31 <DL>
32 <DT><A href="mailto:users-request@lists.freeswan.org?body=subscribe">
33 users</A></DT>
34 <DD>
35 <UL>
36 <LI>The general list for discussing use of the software</LI>
37 <LI>The place for seeking<STRONG> help with problems</STRONG> (but
38 please check the<A href="faq.html"> FAQ</A> first).</LI>
39 <LI>Anyone can post.</LI>
40 </UL>
41 </DD>
42 <DT><A href="mailto:bugs-request@lists.freeswan.org?body=subscribe">bugs</A>
43 </DT>
44 <DD>
45 <UL>
46 <LI>For<STRONG> bug reports</STRONG>.</LI>
47 <LI>If you are not certain what is going on -- could be a bug, a
48 configuration error, a network problem, ... -- please post to the users
49 list instead.</LI>
50 <LI>Anyone can post.</LI>
51 </UL>
52 </DD>
53 <DT><A href="mailto:design-request@lists.freeswan.org?body=subscribe">
54 design</A></DT>
55 <DD>
56 <UL>
57 <LI><STRONG>Design discussions</STRONG>, for people working on FreeS/WAN
58 development or others with an interest in design and security issues.</LI>
59 <LI>It would be a good idea to read the existing design papers (see this<A
60 href="intro.html#applied"> list</A>) before posting.</LI>
61 <LI>Anyone can post.</LI>
62 </UL>
63 </DD>
64 <DT><A href="mailto:announce-request@lists.freeswan.org?body=subscribe">
65 announce</A></DT>
66 <DD>
67 <UL>
68 <LI>A<STRONG> low-traffic</STRONG> list.</LI>
69 <LI><STRONG>Announcements</STRONG> about FreeS/WAN and related software.</LI>
70 <LI>All posts here are also sent to the users list. You need not
71 subscribe to both.</LI>
72 <LI>Only the FreeS/WAN team can post.</LI>
73 <LI>If you have something you feel should go on this list, send it to<VAR>
74 announce-admin@lists.freeswan.org</VAR>. Unless it is obvious, please
75 include a short note explaining why we should post it.</LI>
76 </UL>
77 </DD>
78 <DT><A href="mailto:briefs-request@lists.freeswan.org?body=subscribe">
79 briefs</A></DT>
80 <DD>
81 <UL>
82 <LI>A<STRONG> low-traffic</STRONG> list.</LI>
83 <LI><STRONG>Weekly summaries</STRONG> of activity on the users list.</LI>
84 <LI>All posts here are also sent to the users list. You need not
85 subscribe to both.</LI>
86 <LI>Only the FreeS/WAN team can post.</LI>
87 </UL>
88 </DD>
89 </DL>
90 <P>To subscribe to any of these, you can:</P>
91 <UL>
92 <LI>just follow the links above</LI>
93 <LI>use our<A href="http://www.freeswan.org/mail.html"> web interface</A>
94 </LI>
95 <LI>send mail to<VAR> listname</VAR>-request@lists.freeswan.org with a
96 one-line message body &quot;subscribe&quot;</LI>
97 </UL>
98 <P>Archives of these lists are available via the<A href="http://www.freeswan.org/mail.html">
99 web interface</A>.</P>
100 <H4><A name="which.list">Which list should I use?</A></H4>
101 <P>For most questions, please check the<A href="faq.html"> FAQ</A>
102 first, and if that does not have an answer, ask on the users list. &quot;My
103 configuration doesn't work.&quot; does not belong on the bugs list, and &quot;Can
104 FreeS/WAN do such-and-such&quot; or &quot;How do I configure it to...&quot; do not
105 belong in design discussions.</P>
106 <P>Cross-posting the same message to two or more of these lists is
107 discouraged. Quite a few people read more than one list and getting
108 multiple copies is annoying.</P>
109 <H4><A name="policy.list">List policies</A></H4>
110 <P><STRONG>US citizens or residents are asked not to post code to the
111 lists, not even one-line bug fixes</STRONG>. The project cannot accept
112 code which might entangle it in US<A href="politics.html#exlaw"> export
113 restrictions</A>.</P>
114 <P>Non-subscribers can post to some of these lists. This is necessary;
115 someone working on a gateway install who encounters a problem may not
116 have access to a subscribed account.</P>
117 <P>Some spam turns up on these lists from time to time. For discussion
118 of why we do not attempt to filter it, see the<A href="faq.html#spam">
119 FAQ</A>. Please do not clutter the lists with complaints about this.</P>
120 <H3><A name="archive">Archives of the lists</A></H3>
121 <P>Searchable archives of the old single list have existed for some
122 time. At time of writing, it is not yet clear how they will change for
123 the new multi-list structure.</P>
124 <UL>
125 <LI><A href="http://www.sandelman.ottawa.on.ca/linux-ipsec">Canada</A></LI>
126 <LI><A href="http://www.nexial.com">Holland</A></LI>
127 </UL>
128 <P>Note that these use different search engines. Try both.</P>
129 <P>Archives of the new lists are available via the<A href="http://www.freeswan.org/mail.html">
130 web interface</A>.</P>
131 <H2><A name="indexes">Indexes of mailing lists</A></H2>
132 <P><A href="http://paml.net/">PAML</A> is the standard reference for<STRONG>
133 P</STRONG>ublicly<STRONG> A</STRONG>ccessible<STRONG> M</STRONG>ailing<STRONG>
134 L</STRONG>ists. When we last checked, it had over 7500 lists on an
135 amazing variety of topics. It also has FAQ information and a search
136 engine.</P>
137 <P>There is an index of<A href="http://oslab.snu.ac.kr/~djshin/linux/mail-list/index.shtml">
138 Linux mailing lists</A> available.</P>
139 <P>A list of<A href="http://xforce.iss.net/maillists/otherlists.php">
140 computer security mailing lists</A>, with descriptions.</P>
141 <H2><A name="otherlists">Lists for related software and topics</A></H2>
142 <P>Most links in this section point to subscription addresses for the
143 various lists. Send the one-line message &quot;subscribe<VAR> list_name</VAR>
144 &quot; to subscribe to any of them.</P>
145 <H3><A NAME="28_3_1">Products that include FreeS/WAN</A></H3>
146 <P>Our introduction document gives a<A href="intro.html#products"> list
147 of products that include FreeS/WAN</A>. If you have, or are
148 considering, one of those, check the supplier's web site for
149 information on mailing lists for their users.</P>
150 <H3><A name="linux.lists">Linux mailing lists</A></H3>
151 <UL>
152 <LI><A href="mailto:majordomo@vger.kernel.org">
153 linux-admin@vger.kernel.org</A>, for Linux system administrators</LI>
154 <LI><A href="mailto:netfilter-request@lists.samba.org">
155 netfilter@lists.samba.org</A>, about Netfilter, which replaces IPchains
156 in kernels 2.3.15 and later</LI>
157 <LI><A href="mailto:security-audit-request@ferret.lmh.ox.ac.uk">
158 security-audit@ferret.lmh.ox.ac.uk</A>, for people working on security
159 audits of various Linux programs</LI>
160 <LI><A href="mailto:securedistros-request@humbolt.geo.uu.nl">
161 securedistros@humbolt.geo.uu.nl</A>, for discussion of issues common to
162 all the half dozen projects working on secure Linux distributions.</LI>
163 </UL>
164 <P>Each of the scure distribution projects also has its own web site and
165 mailing list. Some of the sites are:</P>
166 <UL>
167 <LI><A href="http://bastille-linux.org/">Bastille Linux</A> scripts to
168 harden Redhat, e.g. by changing permissions and modifying inialisation
169 scripts</LI>
170 <LI><A href="http://immunix.org/">Immunix</A> take a different approach,
171 using a modified compiler to build kernel and utilities with better
172 resistance to various types of overflow and exploit</LI>
173 <LI>the<A href="glossary.html#NSA"> NSA</A> have contractors working on
174 a<A href="glossary.html#SElinux"> Security Enhanced Linux</A>,
175 primarily adding stronger access control mechanisms. You can download
176 the current version (which interestingly is under GPL and not export
177 resrtricted) or subscribe to the mailing list from the<A href="http://www.nsa.gov/selinux">
178 project web page</A>.</LI>
179 </UL>
180 <H3><A name="ietf">Lists for IETF working groups</A></H3>
181 <P>Each<A href="glossary.html#IETF"> IETF</A> working group has an
182 associated mailing list where much of the work takes place.</P>
183 <UL>
184 <LI><A href="mailto:majordomo@lists.tislabs.com">ipsec@lists.tislabs.com</A>
185 , the IPsec<A href="http://www.ietf.org/html.charters/ipsec-charter.html">
186 working group</A>. This is where the protocols are discussed, new
187 drafts announced, and so on. By now, the IPsec working group is winding
188 down since the work is essentially complete. A<A href="http://www.sandelman.ottawa.on.ca/ipsec/">
189 list archive</A> is available.</LI>
190 <LI><A href="mailto:ipsec-policy-request@vpnc.org">IPsec policy</A>
191 list, and its<A href="http://www.vpnc.org/ipsec-policy/"> archive</A></LI>
192 <LI><A href="mailto:ietf-ipsra-request@vpnc.org">IP secure remote access</A>
193 list, and its<A href="http://www.vpnc.org/ietf-ipsra/mail-archive/">
194 archive</A></LI>
195 </UL>
196 <H3><A name="other">Other mailing lists</A></H3>
197 <UL>
198 <LI><A href="mailto:ipc-announce-request@privacy.org">
199 ipc-announce@privacy.org</A> a low-traffic list with announcements of
200 developments in privacy, encryption and online civil rights</LI>
201 <LI>a VPN mailing list's<A href="http://kubarb.phsx.ukans.edu/~tbird/vpn.html">
202 home page</A></LI>
203 </UL>
204 <H2><A name="newsgroups">Usenet newsgroups</A></H2>
205 <UL>
206 <LI>sci.crypt</LI>
207 <LI>sci.crypt.research</LI>
208 <LI>comp.dcom.vpn</LI>
209 <LI>talk.politics.crypto</LI>
210 </UL>
211 <HR>
212 <A HREF="toc.html">Contents</A>
213 <A HREF="ipsec.html">Previous</A>
214 <A HREF="web.html">Next</A>
215 </BODY>
216 </HTML>