<td>
<font face="Arial,Helvetica,Sans-serif">
<p>
-<font size=4>
<h1>Anonymous CVS Access</h1>
<p>
+<font size=4>
Anonymous CVS access is now available to SILC CVS repository. The
repository includes everything related to SILC project; source codes,
documentation and even these web pages. The CVS access is of course public
While it is our intention that the trunk would always at least compile
there might be situations when it will not.
+</font>
<p><br>
-<h1>Browsing the Source Tree</h1>
+<h2>Browsing the Source Tree</h2>
+<font size=4>
<p>
If you want to browse the source tree using web browser before checking
out the tree with CVS use following link:
updated once a day. If you want real-time access then checkout the CVS
repository.
+</font>
<p><br>
-<h1>Howto Checkout The Source Tree</h1>
+<h2>Howto Checkout The Source Tree</h2>
+<font size=4>
<p>
The repository can be checked out by using anonymous pserver with CVS.
<p>
branches thus this will check out the trunk. The size of the trunk is
currently about 11 MB but will grow in the future.
+</font>
<p><br>
-<h1>What SILC Source Tree Includes</h1>
+<h2>What SILC Source Tree Includes</h2>
<p>
SILC Source tree includes a lot more stuff that appears in public
distribution. The source tree includes, for example, internal scripts,
never appear in public distribution, such as, configuration files.
</pre>
-<font size=4>
+</font>
<p><br>
-<h1>Howto Compile SILC Source Tree</h1>
+<h2>Howto Compile SILC Source Tree</h2>
+<font size=4>
<p>
After checkout from CVS the SILC source tree must be prepared for
configuration and compilation. To compile the source three, give,
<p>
-<font size=3>
<pre>
+<font size=3>
./prepare
./configure --enable-debug
make
+</font>
</pre>
-<font size=4>
The ./prepare script is included in to the source tree and it never
appears in public distribution. The script prepares the source tree
by both cilent and server is very heavy, thus it is common to test
the programs as follows:
<p>
-<font size=3>
<pre>
- ./silc -f configfile 2>log
- ./silcd -f configfile 2>log
+<font size=3>
+ ./silc -d -f configfile 2>log
+ ./silcd -d -f configfile 2>log
+</font>
</pre>
-<font size=4>
+</font>
<p><br>
-<h1>Howto Clean SILC Source Tree</h1>
+<h2>Howto Clean SILC Source Tree</h2>
+<font size=4>
<p>
To entirely clear the source tree to the state after it was checked out
from CVS, give,
-<font size=3>
<pre>
+<font size=3>
./prepare-clean
+</font>
</pre>
-<font size=4>
This calls `make distclean' plus removes automatically generated files
by hand. It also removes *.log files. However, it will not remove
any other files you might have created.
+</font>
<p><br>
-<h1>Makefiles and configuration files</h1>
+<h2>Makefiles and configuration files</h2>
+<font size=4>
<p>
Developers should never directly write a Makefile. All Makefiles are
always automatically generated by ./prepare and later by ./configure
<td>
<font face="Arial,Helvetica,Sans-serif">
<p>
+<h2>SILC Documentation</h2>
<font size=4>
-<h1>SILC Documentation</h1>
<p>
Currently the SILC documentation is under work and the software does not
have that much of a documentation.
<p>
[Coming later: Software manual, SILC Library Reference manual]
+</font>
<p><br>
-<h1>SILC Protocol Internet Drafts</h1>
+<h2>SILC Protocol Internet Drafts</h2>
<p>
+<font size=4>
SILC Protocol is documented and three Internet Drafts exists. These
Internet Drafts are also available from
<a href="http://www.ietf.org">IETF</a>.
<p>
+<b>Note: These drafts are already pretty much outdated. If you really need
+to know what is happening in the protocol designing I suggest checking out
+the drafts from the CVS. They are updated constantly.</b>
+<p>
<li>Secure Internet Live Conferencing (SILC), Protocol Specification
<p>
Abstract