+++ /dev/null
-<b>About SILC</b>
-<font size="2">
-<br /><br />
-SILC (Secure Internet Live Conferencing) is a protocol which provides
-secure conferencing services in the Internet over insecure channel. SILC
-superficially resembles IRC, although they are very different internally.
-They both provide conferencing services and have almost same set of
-commands. Other than that, they are nothing alike. The SILC is secure and
-the network model is entirely different compared to IRC.
-<br /><br />
-SILC provides security services that any other conferencing protocol does
-not offer today. The most popular conferencing service, IRC, is entirely
-insecure. If you need secure place to talk to some person or to group of
-people over the Internet, IRC or any other conferencing service, for that
-matter, cannot be used. Anyone can see the messages and their contents in
-the IRC network. And the most worse case, some bad guy is able to change
-the contents of the messages. Also, all the authentication data, such as,
-passwords are sent plaintext.
-<br /><br />
-SILC is much more than just about `encrypting the traffic'. That is easy
-enough to do with IRC and SSL hybrids, but even then the entire network
-cannot be secured, only part of it. SILC provides security services, such
-as sending private messages entirely secure; no one can see the message
-except you and the real receiver of the message. SILC also provides same
-functionality for channels; no one except those clients joined to the
-channel may see the messages destined to the channel. Communication
-between client and server is also secured with session keys and all
-commands, authentication data (such as passwords etc.) and other traffic
-is entirely secured. The entire network, and all parts of it, is secured.
-We are not aware of any other conferencing protocol providing same
-features at the present time.
-<br /><br />
-SILC has secure key exchange protocol that is used to create the session
-keys for each connection. SILC also provides strong authentication based
-on either passwords or public key authentication. All authentication data
-are always encrypted in the SILC network. Each connection has their own
-session keys, all channels have channel specific keys, and all private
-messages can be secured with private message specific keys.
-<br /><br />
-</font>
-
-<b>Availability</b>
-<font size="2">
-<br /><br />
-The SILC is distributed currently in three different packages. The SILC
-Client package, the SILC Server package and the SILC Toolkit package. Each
-package has its intended audience.
-<br /><br />
-- SILC Client package is intended for end users who are looking for a good
-and full featured SILC client. The SILC Client package currently includes
-Irssi-SILC client that supports all SILC features, themes and much more.
-It is curses based but has a possibility of adding various other frontends
-to it. The Irssi-SILC client's user interface is based on the Irssi client
-(see <a href="http://irssi.org/">Irssi project</a>).
-<br /><br />
-- SILC Server package is intended for system administrators who would like
-to run their own SILC server or SILC router. The package includes the
-actual server but not the client. If you are running a server and would
-like to connect it to the silc.silcnet.org router you can contact us.
-<br /><br />
-- SILC Toolkit package is intended for developers and programmers who
-would like to create their own SILC based applications or help in the
-development of the SILC protocol. The actual development of the SILC is
-done in the Toolkit and all the other packages are based on the Toolkit
-releases. The Toolkit includes SILC Protocol Core library, SILC Crypto
-library, SILC Key Exchange (SKE) library, SILC Math library, SILC Modules
-(SIM) library, SILC Utility library, SILC Client library and few other
-libraries. It also includes the Irssi-SILC Client, another client as an
-example how to program with the Toolkit and the SILC Server.
-<br /><br />
-</font>
-
-<b>Licensing</b>
-<font size="2">
-<br /><br />
-SILC is an Open Source (or Free Software) project and it has been released
-under the GNU General Public License. The SILC is free to use and everyone
-is allowed to freely redistribute and change the SILC under the terms of the
-GNU GPL. While there is no guarantee for the product, SILC is made as secure
-as possible. The fact that the software and the protocol is open for public
-analysis is a good thing for end user.
-<br /><br />
-Specification of SILC protocol is available for anyone to look at. There
-exist four Internet Drafts that have been submitted to the <a
-href="http://www.ietf.org">IETF</a>. See <a
-href="index.php?page=docs">documentation page</a> for more information.
-<br /><br /></font>
-<b>Contact</b>
-<font size="2">
-<br /><br />
-Feedback and comments are welcome. You can reach me at the following address:
-<br /><br />
-Pekka Riikonen<br />
-<a href="mailto:priikone at silcnet.org">priikone at silcnet.org</a>
-</font>
+++ /dev/null
-<b>Contributing</b>
-<font size="2">
-<br /><br />
-Developers are needed in SILC project. Everyone who has the time and
-ability is welcome to join the project. We need C coders and technical
-writers (to write documentation). Feel free to start narrowing down the TODO
-list.
-<br /><br />
-Interested people are also welcome to give new ideas to the SILC protocol
-that is still in its draft phase. You should probably go and read the SILC
-protocol specification Internet Drafts to get the idea about what SILC
-actually is. The current software version might not give the whole picture
-of the SILC. The Internet Drafts are available in
-<a href="index.php?page=docs">documentation page.</a>
-<br /><br />
-Who wants to send code to the project should read the <a
-href="docs/CodingStyle">CodingStyle</a>
-documentation. New code must comply with the coding style conventions
-described in that document.
-<br /><br />
-There is anonymous CVS acccess for those who want to participate the
-development process. See the <a href="index.php?page=cvs">CVS page.</a>
-</font>
+++ /dev/null
-<b>GNU GENERAL PUBLIC LICENSE<br />
-Version 2, June 1991</b>
-<font size="2">
-<br /><br />
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.<br />
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-<br /><br />
-Everyone is permitted to copy and distribute verbatim copies<br />
-of this license document, but changing it is not allowed.
-<br /><br />
-<b>Preamble</b>
-<br /><br />
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-<br /><br />
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-<br /><br />
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-<br /><br />
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-<br /><br />
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-<br /><br />
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-<br /><br />
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-<br /><br />
- The precise terms and conditions for copying, distribution and
-modification follow.
-<br /><br />
-<b>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</b>
-<br /><br />
-<strong>0.</strong>
- This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-<br /><br />
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-<br /><br />
-<strong>1.</strong>
- You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-<br /><br />
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-<br /><br />
-<strong>2.</strong>
- You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-<br /><br />
-<strong>a)</strong>
- You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-<br /><br />
-<strong>b)</strong>
- You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-<br /><br />
-<strong>c)</strong>
- If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-<br /><br />
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-<br /><br />
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-<br /><br />
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-<br /><br />
-<strong>3.</strong>
- You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-<br /><br />
-<strong>a)</strong>
- Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-<br /><br />
-<strong>b)</strong>
- Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-<br /><br />
-<strong>c)</strong>
- Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-<br /><br />
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-<br /><br />
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-<br /><br />
-<strong>4.</strong>
- You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-<br /><br />
-<strong>5.</strong>
- You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-<br /><br />
-<strong>6.</strong>
- Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-<br /><br />
-<strong>7.</strong>
- If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-<br /><br />
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-<br /><br />
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-<br /><br />
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-<br /><br />
-<strong>8.</strong>
- If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-<br /><br />
-<strong>9.</strong>
- The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-<br /><br />
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-<br /><br />
-<strong>10.</strong>
- If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-<br /><br />
-<strong>NO WARRANTY</strong>
-<br /><br />
-<strong>11.</strong>
- BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-<br /><br />
-<strong>12.</strong>
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-<br /><br />
-<b>END OF TERMS AND CONDITIONS</b>
-</font>
+++ /dev/null
-<?php
-//test 2
-
-function Hits() {
-
-// $datafile has to be writable by http server user uid
-// else hits count will not be increased, only printed out
-
- $datafile = $DocRoot."COUNTER";
-
- if (Is_Writable($datafile)) {
- $fp = FOpen($datafile, "r+");
- $writable = "true";
- }
- else
- if (Is_Readable($datafile)) $fp = FOpen($datafile,"r");
- else return;
-
- $hits = FGets($fp,255) + 1;
- if(!$hits) $hits = 1;
-
- if($writable) {
- Rewind($fp);
- FPuts($fp, $hits);
- }
-
- FClose($fp);
- echo $hits." hits";
-}
-
-Hits();
-
-?>
-
-$silc: $
+++ /dev/null
-<b>Anonymous CVS access</b>
-<font size="2">
-<br /><br />
-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
-but it is intended for developers. After you have checked out the SILC
-source tree you should read README.CVS file from the source tree or rest
-of this web page.
-<br /><br />
-Also note that this is the closest to real time development you can get
-thus you cannot expect that the source tree would work or even compile.
-While it is our intention that the trunk would always at least compile
-there might be situations when it will not.
-
-<br /><br />
-
-<b>Browsing the Source Tree</b>
-<br /><br />
-If you want to browse the source tree using web browser before checking
-out the tree with CVS use following link:
-<br /><br />
-<a href="http://cvs.silcnet.org/">Web Access to CVS repository
-</a>
-<br /><br />
-Note that this is not real-time access to the CVS repository. It is
-updated once a day. If you want real-time access then checkout the CVS
-repository.
-
-<br /><br />
-
-<b>Howto Checkout The Source Tree</b>
-<br /><br />
-The repository can be checked out by using anonymous pserver with CVS.
-<br /><br />
-For those who are using sh/ksh/bashi/zsh the check out is done as follows:
-<br /><br />
-<font size="3">
-<tt>
-export CVSROOT=:pserver:cvs@cvs.silcnet.org:/cvs/silc
-<br /><br />
-cvs login<br />
-cvs co silc<br />
-cvs logout<br />
-</tt>
-</font>
-
-<br /><br />
-For those who are using csh/tcsh the check out is done as follows:
-<br /><br />
-<font size="3">
-<tt>
-setenv CVSROOT :pserver:cvs@cvs.silcnet.org:/cvs/silc
-<br /><br />
-cvs login<br />
-cvs co silc<br />
-cvs logout<br />
-</tt>
-</font>
-<br /><br />
-If you don't want to set $CVSROOT environment variable you can set the
-path to the cvs as command line option:
-<br /><br />
-<font size="3">
-<tt>
-cvs -d:pserver:cvs@cvs.silcnet.org:/cvs/silc login<br />
-cvs -d:pserver:cvs@cvs.silcnet.org:/cvs/silc co silc<br />
-cvs -d:pserver:cvs@cvs.silcnet.org:/cvs/silc logout
-</tt>
-</font>
-<br /><br />
-Whatever method you will decide to use, after you have done cvs login you will
-be prompted for password:
-<br /><br />
-<b>CVS password: </b>silc
-<br /><br />
-Type the password "silc" and press <ENTER>
-<br /><br />
-The actual SILC source tree is checked out using the cvs co silc command,
-described above. This command will fetch the source tree and save it into
-directory named silc. SILC CVS repository currently does not have any
-branches thus this will check out the trunk. The size of the trunk is
-currently about 13 MB but will grow in the future.
-
-<br /><br />
-
-<b>What SILC Source Tree Includes</b>
-<br /><br />
-SILC Source tree includes a lot more stuff that appears in public
-distribution. The source tree includes, for example, internal scripts,
-configuration files, SILC webpages etc. These never appear on a public
-distribution.
-<br /><br />
-Following directories currently exist in SILC source tree.
-<br /><br />
-<font size="3">
-<tt>
-doc/
-<br /><br />
-Includes all the SILC documentation. Few parts of the documentation
-are generated when distribution is generated. The automatically
-generated files should never be commited to CVS.
-<br /><br />
-includes/
-<br /><br />
-Includes SILC include files.
-<br /><br />
-lib/
-<br /><br />
-Includes SILC libraries. There are maybe libraries in the CVS which
-are not inclduded in public distribution.
-<br /><br />
-public_html/
-<br /><br />
-Includes the official SILC web pages and everything related to them.
-This directory will never appear in public distribution.
-<br /><br />
-silc/
-<br /><br />
-Includes SILC client. There can be some extra files that will
-never appear in public distribution, such as configuration files.
-<br /><br />
-silcd/
-<br /><br />
-Includes SILC server. There can be some extra files that will
-never appear in public distribution, such as configuration files.
-</tt>
-</font>
-
-<br /><br />
-
-<b>Howto Compile SILC Source Tree</b>
-<br /><br />
-After checkout from CVS the SILC source tree needs to be prepared for
-configuration and compilation. To compile the source tree, type:
-<br /><br />
-<font size="3">
-<tt>
-./prepare<br />
-./configure --enable-debug<br />
-make<br /><br />
-note: on non-Linux operating systems GNU make (gmake) is prefered
-</tt>
-</font>
-<br /><br />
-
-The ./prepare script is included in the source tree and it will never
-appears in public distribution. The script prepares the source tree
-by creating configuration scripts and Makefiles. The prepare must be
-run every time you made any changes to configuration scripts (however,
-making changes to Makefile.am's does not require running ./prepare).
-<br /><br />
-As a developer you should read the ./configure script's help by typing
-./configure --help and study all of its different options. Also you
-should configure the script with --enable-debug option as it compiles
-SILC with -g (debugging) option and it enables the SILC_LOG_DEBUG*
-scripts. Warning is due here: The debugging produced by both cilent
-and server is very huge, thus it is common to test the programs as
-follows:
-<br /><br />
-<font size="3">
-<tt>
-./silc -d -f configfile 2>log<br />
-./silcd -d -f configfile 2>log
-</tt>
-</font>
-
-<br /><br />
-
-<b>How to clean SILC Source Tree</b>
-<br /><br />
-To entirely clear the source tree to the state after it was checked out
-from CVS, type:
-<br /><br />
-<font size="3">
-<tt>
-./prepare-clean
-</tt>
-</font><br /><br />
-
-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.
-
-<br /><br />
-
-<b>Makefiles and configuration files</b>
-<br /><br />
-Developers should never directly write a Makefile. All Makefiles are
-always automatically generated by ./prepare and later by ./configure
-scripts. Instead, developers have to write Makefile.am files. There
-are plenty of examples what they should look like. If you changed
-Makefile.am during development you do not need to run ./prepare, just
-run normal make.
-<br />
-Configuration files are the files that ./prepare automatically generates
-and which will be included into public distribution. ./prepare creates
-for example the ./configure script that is not commited to the CVS.
-`configure.in' is the file that developers have to edit to change ./configure
-script. After doing changes you need to run ./prepare.
-</font>
+++ /dev/null
-<b>SILC Documentation</b>
-<font size="2">
-<br /><br />
-Currently working on the SILC documentation is in progress and the software
-does not have extensive documentation at all.
-<br /><br />
-README file from packages: <a href="docs/README">README</a>
-<br />
-Coding Style in SILC source tree: <a href="docs/CodingStyle">CodingStyle</a>
-<br /><br />
-<i>Coming later: Software manual, SILC Library Reference manual</i>
-
-<br /><br /><br />
-
-</font>
-<b>SILC Protocol Internet Drafts</b>
-<br /><br />
-<font size="2">
-SILC Protocol is documented and four Internet Drafts exist. These
-Internet Drafts are also available from
-<a href="http://www.ietf.org">IETF</a>.
-<br><b>Updated on Sun Jul 22 22:01:38 EEST 2001</b>: These new
-updated drafts will be submitted to the IETF after the August 14th 2001.
-<br /><br />
-
-<b>Secure Internet Live Conferencing (SILC), Protocol Specification</b>
-<br /><br />
-Abstract
-<br /><br />
- This memo describes a Secure Internet Live Conferencing (SILC)
- protocol which provides secure conferencing services over insecure
- network channel. SILC is IRC [IRC] like protocol, however, it is
- not equivalent to IRC and does not support IRC. Strong cryptographic
- methods are used to protect SILC packets inside the SILC network.
- Three other Internet Drafts relates very closely to this memo;
- SILC Packet Protocol [SILC2], SILC Key Exchange and Authentication
- Protocols [SILC3] and SILC Commands [SILC4].
-<br /><br />
-<a href="docs/draft-riikonen-silc-spec-03.txt">
-draft-riikonen-silc-spec-03.txt</a>
-<br /><br /><br />
-
-<b>SILC Packet Protocol</b>
-<br /><br />
-Abstract
-<br /><br />
- This memo describes a Packet Protocol used in the Secure Internet Live
- Conferencing (SILC) protocol, specified in the Secure Internet Live
- Conferencing, Protocol Specification Internet Draft [SILC1]. This
- protocol describes the packet types and packet payloads which defines
- the contents of the packets. It provides secure binary packet protocol
- that assures that the content of the packets is secured and authenticated.
-<br /><br />
-<a href="docs/draft-riikonen-silc-pp-03.txt">
-draft-riikonen-silc-pp-03.txt</a>
-<br /><br /><br />
-
-<b>SILC Key Exchange and Authentication Protocols</b>
-<br /><br />
-Abstract
-<br /><br />
- This memo describes two protocols used in the Secure Internet Live
- Conferencing (SILC) protocol, specified in the Secure Internet Live
- Conferencing, Protocol Specification internet-draft [SILC1]. The
- SILC Key Exchange (SKE) protocol provides secure key exchange between
- two parties resulting into shared secret key material. The protocol
- is based on Diffie-Hellman key exchange algorithm and its functionality
- is derived from several key exchange protocols. SKE uses best parts
- of the SSH2 Key Exchange protocol, Station-To-Station (STS) protocol
- and the OAKLEY Key Determination protocol [OAKLEY].
-<br /><br />
- The SILC Connection Authentication protocol provides user level
- authentication used when creating connections in SILC network. The
- protocol is transparent to the authentication data which means that it
- can be used to authenticate the user with, for example, passphrase
- (pre-shared-secret) or public key (and certificate).
-<br /><br />
-<a href="docs/draft-riikonen-silc-ke-auth-03.txt">
-draft-riikonen-silc-ke-auth-03.txt</a>
-<br /><br /><br />
-
-<b>SILC Commands</b>
-<br /><br />
-Abstract
-<br /><br />
- This memo describes the commands used in the Secure Internet Live
- Conferencing (SILC) protocol, specified in the Secure Internet Live
- Conferencing, Protocol Specification Internet Draft [SILC1]. The
- SILC Commands are very important part of the SILC protocol. Usually
- the commands are used by SILC clients to manage the SILC session, but
- also SILC servers may use the commands. This memo specifies detailed
- command messages and command reply messages.
-<br /><br />
-<a href="docs/draft-riikonen-silc-commands-01.txt">
-draft-riikonen-silc-commands-01.txt</a>
-<br />
-</font>
+++ /dev/null
-Coding Style in SILC source tree
-================================
-
-This documents describes the coding style and coding conventions used
-in the SILC source tree. The purpose of the document is to describe the
-common way to program for SILC and thus should be learned when programming
-new code. The document describes various conventions regarding variable
-naming, function naming, indentation, overall appearance of a piece of
-code and how some of the technical issues has been done in the SILC and
-should be done in the future.
-
-
-Naming
-======
-
-Generic naming
-
-All identifiers, whether they defines, functions or something else, with
-execption of variables, has a common naming convention. Usually all
-identifiers use `silc' prefix to indicate that the identifier is part of
-SILC distribution. For example, silc_server_init(), SILC_PACKET_TYPE_ERROR,
-etc. As mentioned however, variables, local or global, does not use this
-naming convention.
-
-Lower lever routines, usually some library routines, may use their
-own naming convention if generic API is defined over them. The API uses
-the common naming convention while the lower level routines uses what
-ever they want. For example, ciphers are implemented currently in this
-way. They define common SILC Cipher API but the actual implementation
-of algorithms uses their own naming convention. Another example is
-the GMP math library that uses its own function naming but we have our
-own SILC MP API over it that has been defined using common SILC naming
-convention.
-
-
-Variables
-
-Variable names are always in lowercase and any mixed-case or totally
-uppercase variable names should be avoided. Variable names may include
-underscore if it is necessary. For example, `unsigned char *id_string;'.
-
-The same name convention is used in structure field names. All fields
-in structures should be in lowercase. Global variables should have some
-sort of prefix to indicate that the variable is global. Although, global
-variables should be avoided if possible.
-
-Local variable names should be as short as possible without losing
-meaning of the name. For example there is no reason to call loop
-counter as `loop_counter' when `i' is commonly used instead. Using
-variable name `tmp' is also ok and should be used when some temporary
-value is used.
-
-
-#define's and Macros
-
-All #define's should always be in uppercase to indicate that it is
-a define, for example, `#define SILC_PACKET_TYPE_NONE 0'. As mentioned
-previously #define's and macros always use the `SILC' prefix. The
-names also uses always underscores.
-
-Names of #define's and macros should be self explanatory. This may
-lead to long names but it is better than having some `#define SILC_KE1_SX'
-which does not tell you anything.
-
-
-Type definitions
-
-Type definitions (typedefs) uses some what different naming convention
-from variables and macros. Typedefs has mixed-case names and they
-never use underscores. For example, `SilcSomeStruct', `SilcServerObject'.
-Like in any other case the names should be self explanatory which may
-lead to long names but that is not a problem.
-
-The names should tell what the typedef is about. If it is a typedef
-of a structure it should tell what the structure is for in the first
-place. For example `SilcClientStruct', `SilcCipherObject',
-`SilcConfigSection´, etc.
-
-
-Structures
-
-Same naming convention used in typedefs applies to names of structures as
-well. Same as with typedef, structure names should be self explanatory
-and should tell what the structure is made for.
-
-Structures are used a lot in SILC. They are used as simple structures
-and as objects as well. When normal structures are needed they are
-defined as follows,
-
- struct SilcDummyStruct {
- unsigned char *dummy;
- };
-
-And used as `struct SilcDummyStruct *dummy'. However, this is quite
-rarely used in the SILC, instead structures are typedef'd as following
-later. When structure is used as object they are defined as follows,
-
- typedef struct SilcDummyStruct {
- unsigned char *dummy;
- unsigned int flags;
- void (*callback)(void *, unsigned int);
- } SilcDummyObject;
-
-If the SilcDummyStruct is not needed it may be omitted (which is very
-common in SILC code), leaving,
-
- typedef struct {
- unsigned char *dummy;
- unsigned int flags;
- void (*callback)(void *, unsigned int);
- } SilcDummyObject;
-
-Finally, it is common that structures are typedef'd pointers as they
-are very flexible to use,
-
- typedef SilcDummyObject *SilcDummy;
-
-It is common in SILC to typedef structures instead of defining name
-for the structure. In this case the structure may be used without
-defining `struct' to the code, For example,
-
- SilcDummyObject dummy_obj;
- SilcDummyObject *dummy;
-
-If the structure has a pointer typedef then they are defined as normal
-variables but for real they are pointers, For example,
-
- SilcDummy dummy;
- dummy = silc_calloc(1, sizeof(*dummy));
- dummy->flags = 0;
-
-This convention is very common in SILC code and has been used consistently
-throughout the code. The pattern here is that all structures are named
-as `SilcXxxStruct', all objects are named as `SilcXxxObject' and when
-they are typedef'd pointers they are named as `SilcXxx'.
-
-
-Functions
-
-Function naming uses the common naming convention used in the SILC. All
-functions are always lowercase and they use underscores. The name of
-the function always starts with prefix `silc_'. The name of the function
-should be self explanatory which may lead to long names. The name of
-a function is constructed from following parts,
-
- silc_<application>_<module>_<function>
-
-The <application> is for example <client> or <server>, however, it is
-always omitted (and must be omitted) when programming library code.
-
-The <module> is the module you are programming currently. You should
-have a pretty good idea what you are programming and what the module
-does. For example, <cipher>, <config>, <command>, <packet>, etc.
-
-The <function> is the describtion of the functionality of the function
-you are writing. Naturally it should be self explanatory and weird
-short names should be avoided. It is better to have long function
-names than some odd name that does not tell what it is about. Function
-naming could be for example, <read>, <new_id>, <register>, <find_by_name>,
-etc.
-
-So, it is common in SILC to have function names, such as,
-
- silc_server_packet_send
- silc_server_packet_send_to_channel
- silc_client_packet_process
- silc_idcache_del_by_id
- silc_task_unregister_by_fd
- silc_protocol_excute_final
- silc_buffer_alloc
-
-When function registers something the name of the function should
-generally be `silc_function_register' and unregistering should happen
-with `silc_function_unregister'. When function allocates something it
-should be called `silc_function_alloc' and when freeing it should be
-called `silc_function_free'. Respectively, with init/uninit functions.
-
-When this naming convention is used consistently it is easy to remember
-what the name of the function is. For example, if you need buffer it
-is easy to figure out that the routines are most likely called
-`silc_buffer_*', and if you need to allocate buffer it is most likely
-called `silc_buffer_alloc'. This sort of naming makes the programming,
-in the long run, much cleaner, simpler and faster.
-
-
-Inline functions
-
-SILC uses quite a bit inline functions to optimize the code. The
-naming of inline functions must follow same convention as any normal
-function. All inline functions in SILC are defined and written into
-header files. Inline functions must be defined in following manner
-in the header file,
-
-extern inline void silc_dummy_inline(unsigned int flags)
-{
- doing_little_dummy_things;
-}
-
-Because the function is defined as extern they can be included into
-public header files. Do not forget to define inline function as extern.
-There are no any explicit prototype definitions for inline functions.
-
-
-Indentation
-===========
-
-SILC has been coded with Emacs so standard indentation of Emacs is used
-in the SILC code. The indentation is always 2 characters, not a
-tabulator. If you use Emacs then this should not be a problem. So,
-if you code for SILC be sure to format the code to the standard way
-used in the SILC before submitting the code.
-
-A tip for those who think that these long function names etc are just
-too long to type, consider using dynamic abbreviation found in Emacs.
-With this cool feature you only have type some part of the string and
-then use the dabbrev to find the rest of the string. I guess, by
-default it is M-/ in Emacs but I have binded it into Shift-TAB so it
-is fast to use when typing.
-
-
-Placing Braces
-==============
-
-The common fight about how the braces should be placed in the C code
-is probably going on in the SILC code as well. However, SILC code
-is consistent about this. The placing uses K&R style thus the opening
-of the brace is put to the last on the line and the closing brace is
-on first on its own line,
-
- if (condition) {
- silc_something();
- silc_something_more();
- }
-
-The function's braces are as follows,
-
- int silc_client_function()
- {
- return 0;
- }
-
-More examples,
-
- if (condition) {
- something;
- silc_something_more();
- } else {
- something_else;
- }
-
- if (condition) {
- something;
- silc_something_more();
- } else if (other_condition) {
- something;
- silc_something_more();
- } else {
- something_else;
- }
-
-
-Commenting
-==========
-
-SILC code is usually pretty well commented and this should be the way
-in the future as well. However, the comments should not tell how the
-code works, it should be apparent by looking at the code. Instead the
-commenting should tell what the function does. All functions should
-be commented. If nothing more a line of comment telling what the function
-is about helps a lot when you go back to it after six months. Static
-functions should be commented as well.
-
-The commenting of functions in SILC has been made into the source files,
-and not in the header files where the function prototypes reside. Header
-files usually includes structure comments, macro comments and perhaps
-some other relevant commenting but usually not function comments.
-It is also Ok to comment the code inside function when it is needed.
-
-Comments should use normal C-language comments /* */ and not C++ comments.
-
-
-General Appearance
-==================
-
-The code should be clean and good to eye, although the function of it
-must always supersede the appearance. However, it is nice to read code
-that looks good. Here are some issues on general appearance.
-
- o Use empty lines when appropriate but not too much. There
- should not be excess empty lines at the end of file. However,
- using some empty lines in the code makes the code better
- looking.
-
- o The line is 79 characters long and not one character longer.
- Longer lines must be cut in two, or three, or ...
-
- o Use spaces very much. Do not write things like `if(!k)',
- instead write `if (!k)'. Same with `for', `while', etc.
- Spaces should be put around all binary operators like `*',
- `==', `+', etc. Also, when setting a value to variable be
- sure to set spaces around `='. When writing argument list
- to a function, space should follow each of the comma in the
- list. However, do not use spaces with parenthesis, for
- example, `if ( !k )' is not accepted.
-
- o If you are not sure about how something should be done or
- the code you've done is not finished, it should be commented
- with XXX plus explanation what is going on.
-
-
-Source Files
-
-All source files starts with header that includes the name of the author,
-copyright notice and the copyright policy, usually part of GNU GPL licence.
-Now, this really isn't that important but some sort of header should be in
-all source files.
-
-In the start of the source files should include the #include's that are
-needed. All library source files must include `silcincludes.h', this is
-a must. Client source file must include at least `clientincludes.h' and
-server source file must include `serverincludes.h'. Additional include's
-may be added as well, however, system specific includes should not be
-added directly (unless it is really a special case). Go see any source
-file as an example.
-
-
-Header Files
-
-As with source files, header files should include same file header at
-the start of the file.
-
-Header files are usually divided in three parts in SILC. At the start
-of header files should include all definitions, typedefs, structure
-definitions etc. After definitions should include macros and inline
-functions if any of those exist. After macros should include the
-public prototypes of the functions. Go see any header file as an example.
-
-
-Debug Messages
-==============
-
-When writing new code it is recommended that the code produces some sort
-of debug messages. SILC has own debug logging system that must be used
-in the generic SILC code. Few macros exist,
-
- SILC_LOG_DEBUG
- SILC_LOG_HEXDUMP
- SILC_LOG_INFO
- SILC_LOG_WARNING
- SILC_LOG_ERROR
- SILC_LOG_FATAL
-
-When doing debugging the most used macros are SILC_LOG_DEBUG and
-SILC_LOG_HEXDUMP. With first macro you can print out any sort of debug
-messages with variable argument list, for example,
-
- SILC_LOG_DEBUG(("Start"));
- SILC_LOG_DEBUG(("Packet length %d", packet_len));
-
-Note the extra parenthesis that are required for the macro so that the
-variable argument list formatting would work correctly.
-
-When you need to dump some data into screen you should use SILC_LOG_HEXDUMP
-macro. For example,
-
- SILC_LOG_HEXDUMP(("Packet"), packet->data, packet->len);
- SILC_LOG_HEXDUMP(("Packet, size %d", size), packet->data, packet->len);
-
-In SILC_LOG_HEXDUMP the data to be dumped are set between the second last
-and last parenthesis in order that the data is first and the length of the
-data is next. If arguments are used they are used the same way as in
-SILC_LOG_DEBUG and the data to be dumped are set after the argument list
-is closed with the parenthesis.
-
-
-Memory Allocation
-=================
-
-Naturally, memory allocation is a big part of SILC. However, there are
-few things that must be noted on the issue. SILC has defined its own
-memory allocation functions that must be used. System specific functions
-must not be used directly. There are functions like,
-
- silc_malloc
- silc_calloc
- silc_realloc
- silc_free
-
-You should always use silc_calloc instead of silc_malloc because
-silc_calloc automatically zeroes the allocated memory area. This is
-important especially with structures because generally we want that all
-fields, by default, are zero.
-
-So, instead of doing
-
- SilcStruct *ptr;
-
- ptr = silc_malloc(sizeof(*ptr));
-
-You should do
-
- SilcStruct *ptr
-
- ptr = silc_calloc(1, sizeof(*ptr));
-
-
-When freeing memory it should be zero'ed when appropriate. All memory
-allocations that handle sensitive data such as keys should be zero'ed
-by memset() before freeing the memory. Common way to do is,
-
- memset(ptr, 'F', sizeof(*ptr));
- silc_free(ptr);
-
-Where 'F' indicates free'd memory if you ever check it with debugger.
-Other choice is to use 0 instead of 'F'. The pointer after freeing
-should be set to NULL if appropriate, ptr = NULL.
-
-Note that some functions in the SILC library handles the zeroing of
-the memory area automatically, like for example, silc_buffer_free.
-
-
-Callback Programming
-====================
-
-SILC uses pretty much programming convention called callback programming.
-This is a programming style that extensively uses function pointers
-which are usually called inside some other function.
-
-Typical scenario is this; You are performing some task that most likely
-is asynchronous. You need to be able get some structure context when
-the operation finishes. Most common way in this case is to pass the
-structure context to the operation function with a callback function
-that is called when the operation has finished. Following code explains
-probaly better.
-
-
-/* Prototypes */
-static silc_callback(void *context);
-void silc_start();
-void silc_async_operation_register(int fd, SilcAsyncCb callback,
- void *context);
-void silc_async_operation(int fd, SilcAsyncCb callback, void *context);
-
-/* Type definition of the callback function */
-typedef (*SilcAsyncCb)(void *context);
-
-/* Registers async operation and passes callback function and context
- to it as arguments. */
-
-void silc_start()
-{
- SilcDummyStruct *ctx;
-
- ctx = silc_calloc(1, sizeof(*ctx));
- ctx->fd = 30;
-
- silc_async_operation_register(30, silc_callback, (void *)ctx);
-}
-
-/* The callblack function that is called from the operation function */
-
-static void silc_callback(void *context)
-{
- SilcDummyStruct *ctx = (SilcDummyStruct *)context;
-
- ctx->fd = 10;
-}
-
-/* Register async operation */
-
-void silc_async_operation_register(int fd, SilcAsyncCb callback,
- void *context)
-{
- /* Register and return immediately */
- silc_register_async_operation_internal(fd, callback, context);
-}
-
-/* Operation function that will call the callback function after it
- has finished. */
-
-void silc_async_operation(int fd, SilcAsyncCb callback, void *context)
-{
- here_this_function_does_what_ever_it_wants;
-
- here_something_more;
-
- /* We are finished, call the callback */
- if (callback)
- (*callback)(context);
-}
-
-
-Now, after the registeration of the async operation in this dumb example
-the silc_start returns immediately. Lets say, 10 seconds later the
-async operation is executed (it would have been better to call it just
-timeout) by calling silc_async_operation which on the other hand will
-call the callback function after it has finished. The context that
-was passed to the registeration function is now passed back to the
-callback function. Thus, you will get the context you wanted. This is
-the typical scenario where callback functions come in very handy. This
-is also the best way to pass context's that are needed later without
-making them global context's. And as long as the context's are defined
-as void * they can be what ever contexts making the functions, that
-takes in the context, generic. Like in above example, you could pass
-what ever context to the registeration function if you'd want to.
-
-Callback programming is also used when making generic API's of some
-operation. For example, if you want generic hooks to the API so that
-something could be done while doing the operation (maybe to collect
-statistics or something else) just get the functions accept a callback
-function and context and call them when appropriate, then continue
-as normally.
-
-Callback functions has been used a lot in SILC code. The scheduler
-and task system implemented in core library uses extensively callback
-functions. Timeout's uses callbacks as well. SILC Key Exchange protocol
-uses callback functions too. The callback function in SKE provides
-packet sending without defining into the SKE code how the packets
-should be sent thus making it generic for both client and server
-(and actually to any application for that matter).
-
-There are some technical issues on callback programming that are
-common in SILC code.
-
- o Callback functions are usually defined as void functions
- as the routine that calls them usually don't care about
- what the callback function does. Many times it doesn't
- actually know what it does nor would it be interested to
- know that. It doesn't care about return values.
-
- o Many times the callback functions are static functions
- because they are not wanted to be called in anyway else
- than as callback functions.
-
- o Callback function names usually have the `_cb' or `_callback'
- at the end of function name, eg. silc_client_cb.
-
- o Type of callback functions should be typedef'd instead of
- defining them directly to the function. See above example.
- This makes the code much cleaner.
-
- o Callback function types has usually the suffix `Cb' or
- ´Callback' in the type name, eg. SilcAsyncCallback.
-
- o You must explicitly cast the void * context's to correct
- type in the callback function. Of course you must be careful
- to cast them to the correct type as they are void * they
- could be anything. Many times this causes problems when you
- forget what was the type you passed to it. Callback
- programming may get very complex.
-
- o You cannot use inline functions as callback functions,
- naturally.
-
-Callback programming may be hard to understand from first standing if
-you haven't done these before, and debugging them may be pain in the
-ass sometimes. But after the grand idea behind callback functions
-becomes clear they are a wonderful tool.
-
-
-Copyrights of the Code
-======================
-
-The original code in SILC is GPL licensed. GMP is GPL licensed as well
-and zlib is with free license as well. New code will be accepted to
-the official SILC source tree if it is coded in GPL or similiar free
-license as GPL is, and of course if it is public domain. Code with
-restricting licenses will not be accepted to the SILC source tree.
-SILC is free software, open source, what ever, project and will remain
-as such.
-
-Also, about authoring; If you write code to SILC don't forget to add
-yourself as author at the start of the file. The reason for this is
-of course that everybody should get the credits they deserve but also
-if problems occur we know who to blame. :)
+++ /dev/null
-<b>Download SILC</b>
-<font size="2">
-<br /><br />
-The SILC is distributed in three different packages; the SILC Client, the
-SILC Server and the SILC Toolkit. The SILC Client is intended for end
-users, the SILC Server for system administrators and the SILC Toolkit for
-developers.
-<br /><br />
-
-<b>SILC Client <?php echo $latestc; ?></b>
-<br /><br />
-The SILC Client package is inteded for end users who need only the SILC
-client. The package includes the new Irssi-SILC client.
-<br /><br />
-Sources HTTP:
-<a href="download/silc-client-<?php echo $latestc; ?>.tar.gz">
-tar.gz</a> (<?php echo
-div(FileSize($DownloadRoot."silc-client-".$latestc.".tar.gz"),1024); ?> KB),
-<a href="download/silc-client-<?php echo $latestc; ?>.tar.bz2">
-tar.bz2</a> (<?php echo
-div(FileSize($DownloadRoot."silc-client-".$latestc.".tar.bz2"),1024); ?> KB)
-<br />
-Sources FTP: <a href="ftp://ftp.silcnet.org/pub/silc/">tar.gz and tar.bz2</a>
-<br /><br />
-
-<b>SILC Server <?php echo $latests; ?></b>
-<br /><br />
-The SILC Server package is intended for system administrators who wants to
-setup their own SILC server or router. The package includes only the
-server and not the client. People who is running SILC servers and are
-interested to get the server linked to the new router on silc.silcnet.org
-contact <a href="mailto:priikone at silcnet.org">me</a> now.
-<br /><br />
-Sources HTTP:
-<a href="download/silc-server-<?php echo $latests; ?>.tar.gz">
-tar.gz</a> (<?php echo
-div(FileSize($DownloadRoot."silc-server-".$latests.".tar.gz"),1024); ?> KB),
-<a href="download/silc-server-<?php echo $latests; ?>.tar.bz2">
-tar.bz2</a> (<?php echo
-div(FileSize($DownloadRoot."silc-server-".$latests.".tar.bz2"),1024); ?> KB)
-<br />
-Sources FTP: <a href="ftp://ftp.silcnet.org/pub/silc/">tar.gz and tar.bz2</a>
-<br /><br />
-
-<b>SILC Toolkit <?php echo $latest; ?></b>
-<br /><br />
-The SILC Toolkit package is intended for developers and programmers who
-would like to create their own SILC applications or help in the
-development of the SILC protocol.
-<br /><br />
-Sources HTTP:
-<a href="download/silc-toolkit-<?php echo $latest; ?>.tar.gz">
-tar.gz</a> (<?php echo
-div(FileSize($DownloadRoot."silc-toolkit-".$latest.".tar.gz"),1024); ?> KB),
-<a href="download/silc-toolkit-<?php echo $latest; ?>.tar.bz2">
-tar.bz2</a> (<?php echo
-div(FileSize($DownloadRoot."silc-toolkit-".$latest.".tar.bz2"),1024); ?> KB)
-<br />
-Sources FTP: <a href="ftp://ftp.silcnet.org/pub/silc/">tar.gz and tar.bz2</a>
-<br /><br />
-
-<b>CVS Snapshots</b>
-<br /><br />
-Daily CVS snapshots are available. These are generated 22:00 GMT every
-night. Read the <a href="index.php?page=cvs">CVS page</a> for more
-information.
-<br /><br />
-HTTP: <a href="download/silc.tar.gz">CVS Snapshot</a>
-<br /><br />
-<b>Portability</b>
-<br /><br />
-The SILC has been reported to work on, at least:
-<br /><br />
- - Linux<br />
- - FreeBSD<br />
- - NetBSD<br />
- - OpenBSD<br />
- - HP-UX<br />
- - Solaris<br />
- - Windows<br />
- - Cygwin & MinGW<br />
-</font>
+++ /dev/null
-<b>Frequently Asked Questions</b><br /><br />
-<font size="2">
-<a href="#f1_0">1. General Questions</a><br />
- <a href="#f1_1">1.1 What is SILC?</a><br />
- <a href="#f1_20">1.2 When was SILC Project started?</a><br />
- <a href="#f1_30">1.3 Why SILC in the first place?</a><br />
- <a href="#f1_40">1.4 What license covers the SILC release?</a><br />
- <a href="#f1_50">1.5 Why SILC? Why not IRC3?</a><br />
- <a href="#f1_55">1.6 What platforms SILC supports?</a><br />
- <a href="#f1_60">1.7 Where can I find more information?</a><br />
- <a href="#f1_70">1.8 I would like to help out, what can I do?</a><br />
-<br />
-<a href="#f2_0">2. Protocol Questions</a><br />
- <a href="#f2_10">2.1 What is the status of SILC protocol in the IETF?</a><br />
- <a href="#f2_20">2.2 How much the SILC protocol is based on IRC?</a><br />
- <a href="#f2_30">2.3 Why use SILC? Why not IRC with SSL?</a><br />
- <a href="#f2_40">2.4 Can I talk from SILC network to IRC network?</a><br />
- <a href="#f2_45">2.5 Does SILC support file transfer?</a><br />
- <a href="#f2_47">2.6 I am behind a firewall, can I use SILC?</a><br />
- <a href="#f2_50">2.7 How secure SILC really is?</a><br />
- <a href="#f2_60">2.8 Does SILC support instant messaging?</a><br />
- <a href="#f2_80">2.9 I have suggestions to SILC Protocol, what can I do?</a><br />
-<br />
-<a href="#f3_0">3. Client Questions</a><br />
- <a href="#f3_10">3.1 Where can I find SILC clients?</a><br />
- <a href="#f3_20">3.2 Can I use SILC with IRC client and vice versa?</a><br />
-<br />
-<a href="#f4_0">4. Server Questions</a><br />
- <a href="#f4_10">4.1 Where can I find SILC servers?</a><br />
- <a href="#f4_20">4.2 Can I run own SILC server?</a><br />
- <a href="#f4_30">4.3 What is the difference between SILC server and SILC router?</a><br />
-<br />
-<a href="#f5_0">5. Toolkit Questions</a><br />
- <a href="#f5_10">5.1 What is SILC Toolkit?</a><br />
-<br /><br />
-
-<a name="f1_0"></a>
-<b>1. General Questions</b><br /><br />
-
-<a name="f1_10"></a>
-<font color="#2f486f">Q: What is SILC?</font><br />
-A: SILC (Secure Internet Live Conferencing) is a protocol which provides
-secure conferencing services in the Internet over insecure channel. SILC
-is IRC like although internally they are very different. Biggest
-similarity between SILC and IRC is that they both provide conferencing
-services and that SILC has almost same commands as IRC. Other than that
-they are nothing alike.
-<br /><br />
-Biggest differences are that SILC is secure what IRC is not in any way.
-The network model is also entirely different compared to IRC.
-<br /><br />
-
-<a name="f1_20"></a>
-<font color="#2f486f">Q: When was SILC Project started?</font><br />
-A: The SILC development started in 1996 and early 1997. But, for various
-reasons it suspended many times until it finally got some wind under its
-wings in 1999. First public release was in summer 2000.
-<br /><br />
-
-<a name="f1_30"></a>
-<font color="#2f486f">Q: Why SILC in the first place?</font><br />
-A: Simply for fun, nothing more. And actually for need back in the days
-when it was started. When SILC was first developed there really did not
-exist anything like this. SILC has been very interesting and educational
-project.
-<br /><br />
-
-<a name="f1_40"></a>
-<font color="#2f486f">Q: What license covers the SILC release?</font><br />
-A: The SILC software developed here at silcnet.org, the SILC Client, the
-SILC Server and the SILC Toolkit are covered by the GNU General Public
-License.
-<br /><br />
-
-<a name="f1_50"></a>
-<font color="#2f486f">Q: Why SILC? Why not IRC3?</font><br />
-A: Question that is justified no doubt of that. SILC was not started to
-become a replacement for IRC. SILC was something that didn't exist in 1996
-or even today except that SILC is now released. However, I did check out
-the IRC3 project in 1997 when I started coding and planning the SILC protocol.
-<br /><br />
-But, IRC3 is problematic. Why? Because it still doesn't exist. The
-project is almost at the same spot where it was in 1997 when I checked it
-out. And it was old project back then as well. That's the problem of IRC3
-project. The same almost happened to SILC as well as I wasn't making real
-progress over the years. I talked to the original author of IRC, Jarkko
-Oikarinen, in 1997 and he directed me to the IRC3 project, although he
-said that IRC3 is a lot of talking and not that much of anything else. I
-am not trying to put down the IRC3 project but its problem is that no one
-in the project is able to make a decision what is the best way to go about
-making the IRC3 and I wasn't going to be part of that. The fact is that
-if I would've gone to IRC3 project, nor IRC3 or SILC would exist today. I
-think IRC3 could be something really great if they just would get their
-act together and start coding the thing.
-<br /><br />
-
-<a name="f1_55"></a>
-<font color="#2f486f">Q: What platforms SILC supports?</font><br />
-A: The SILC Client is available on various Unix systems and is reported to
-work under cygwin on Windows. The SILC Server also works on various Unix
-systems. However, the server has not been tested under cygwin as far as we
-know. The SILC Toolkit is distributed for all platforms, Unix, Cygwin
-and native Windows.
-<br /><br />
-
-<a name="f1_60"></a>
-<font color="#2f486f">Q: Where can I find more information?</font><br />
-A: For more technical information we suggest reading the SILC Protocol
-specifications. You might also want to take a look at the <a
-href="?page=docs">documentation </a> page on the web page.
-<br /><br />
-
-<a name="f1_70"></a>
-<font color="#2f486f">Q: I would like to help out, what can I do?</font><br />
-A: You might want to take a look at the <a
-href="?page=contribute">Contributing</a> page and the <a
-href="?page=todo">TODO</a> list. You might also want to join the
-SILC development mailing list.
-<br /><br />
-
-<a name="f2_0"></a>
-<b>2. Protocol Questions</b><br /><br />
-
-<a name="f2_10"></a>
-<font color="#2f486f">Q: What is the status of SILC protocol in the IETF?</font><br />
-A: The SILC protocol specifications has been submitted currently as
-individual submissions. There does not currently exist a working group
-for this sort of project. Our goal is to fully standardize the SILC and
-thus submit it as RFC to the <a href="http://www.ietf.org/">IETF</a> at a
-later time.
-<br /><br />
-
-<a name="f2_20"></a>
-<font color="#2f486f">Q: How much SILC Protocol is based on IRC?</font><br />
-A: SILC is not based on IRC. The client superficially resembles IRC
-client but everything that happens under the hood is nothing alike IRC.
-SILC could *never* support IRC because the entire network toppology is
-different (hopefully more scalable and powerful). So no, SILC protocol
-(client or server) is not based on IRC. Instead, We've taken good things
-from IRC and left all the bad things behind and not even tried to burden
-the SILC with the IRCs problems that will burden IRC and future IRC
-projects till the end. SILC client resembles IRC client because it is
-easier for new users to start using SILC when they already know all the
-commands.
-<br /><br />
-
-<a name="f2_30"></a>
-<font color="#2f486f">Q: Why use SILC? Why not IRC with SSL?</font><br />
-A: Sure, that is possible, although, does that secure the entire IRC
-network? And does that increase or decrease the lags and splits in the
-IRC network? Does that provide user based security where some specific
-private message are secured? Does that provide security where some
-specific channel messages are secured? And I know, you can answer yes to
-some of these questions. But, security is not just about applying
-encryption to traffic and SILC is not just about `encrypting the
-traffic`. You cannot make insecure protocol suddenly secure just by
-encrypting the traffic. SILC is not meant to be IRC replacement. IRC is
-good for some things, SILC is good for same and some other things.
-<br /><br />
-
-<a name="f2_40"></a>
-<font color="#2f486f">Q: Can I talk from SILC network to IRC network?</font><br />
-A: Simple answer for this is No. The protocols are not compatible which
-makes it impossible to directly talk from SILC network to IRC network or
-vice versa. Developing a gateway between these two networks would
-technically be possible but from security point of view strongly not
-recommended. We have no plans for developing such a gateway.
-<br /><br />
-
-<a name="f2_45"></a>
-<font color="#2f486f">Q: Does SILC support file transfer?</font><br />
-A: Not yet. This is a feature that will be added to the SILC protocol.
-The exact file transfer protocol is undefined.
-<br /><br />
-
-<a name="f2_47"></a>
-<font color="#2f486f">Q: I am behind a firewall, can I use SILC?</font><br />
-A: Yes. If your network administrator can open the port 706 (TCP) you can
-use SILC without problems. You may also compile your SILC client with
-SOCKS support which will proxy your SILC session through the firewall.
-<br /><br />
-
-<a name="f2_50"></a>
-<font color="#2f486f">Q: How secure SILC really is?</font><br />
-A: A good question which I don't have an answer for. We have tried to make
-SILC as secure as possible. However, there is no security protocol or
-security software that has not been vulnerable to some sort of attacks.
-SILC is in no means different from this. So, it is suspected that there
-are security holes in the SILC. These holes just need to be found so
-that they can be fixed.
-<br /><br />
-But to give you some parameters of security SILC uses the most secure
-crytographic algorithms such as AES(Rijndael), Twofish, Blowfish, RC5,
-etc. SILC does not have DES or 3DES as DES is insecure and 3DES is just
-too slow. SILC also uses cryptographically strong random number generator
-when it needs random numbers. Public key cryptography uses RSA (PKCS #1)
-and Diffie-Hellman algorithms. Key lengths for ciphers are initially set
-to 256. For public key algorithms the starting key length is 1024 bits.
-<br /><br />
-But the best answer for this question is that SILC is as secure as its
-weakest link. SILC is open and the protocol is open and in public thus
-open for security analysis.
-<br /><br />
-To give a list of attacks that are ineffective against SILC:
-<br /><br />
-- Man-in-the-middle attacks are ineffective if proper public key
-infrastructure is used. SILC is vulnerable to this attack if the public
-keys used in the SILC are not verified to be trusted (as any other
-protocol for that matter).<br />
- - IP spoofing is ineffective (because of encryption and trusted keys).<br />
- - Attacks that change the contents of the data or add extra data to the
-packets are ineffective (because of encryption and integrity checks).<br />
- - Passive attacks (listenning network traffic) are ineffective (because
-of encryption). Everything is encrypted including authentication data
-such as passwords when they are needed.<br />
- - Any sort of cryptanalytic attacks are tried to make ineffective by
-using the best cryptographic algorithms out there.
-<br /><br />
-
-<a name="f2_60"></a>
-<font color="#2f486f">Q: Does SILC support instant messaing?</font><br />
-A: SILC is not an instant message (IM) system, like ICQ and the others.
-SILC is more IRC like system, "real-time" chat and that kind of
-stuff.
-<br /><br />
-
-<a name="f2_80"></a>
-<font color="#2f486f">Q: I have suggestions to SILC Protocol,
-what can I do?</font><br />
-A: All suggestions and improvements are of course welcome. You should read
-the protocol specifications first to check out whether your idea is
-covered by them already. The best place to make your idea public is the
-SILC development mailing list.
-<br /><br />
-
-<a name="f3_0"></a>
-<b>3. Client Questions</b><br /><br />
-
-<a name="f3_10"></a>
-<font color="#2f486f">Q: Where can I find SILC clients?</font><br />
-A: The SILC client is available for free download from the silcnet.org web
-page. Some people have also mentioned words Java and Perl when talking
-about SILC clients. Nothing has appeared yet, though.
-<br /><br />
-
-<a name="f3_20"></a>
-<font color="#2f486f">Q: Can I use SILC with IRC client and vice versa?</font><br />
-A: Generally the answer would be no for both. However, there exist already
-at least one IRC client that supports SILC, the <a
-href="http://irssi.org/">Irssi client</a>. The current SILC client is
-actually based on the user interface of the Irssi client. So, yes it is
-possible to use SILC with some IRC clients and vice versa. But, this
-does not mean that you can talk from SILC network to IRC network, that is
-not possible.
-<br /><br />
-
-<a name="f4_0"></a>
-<b>4. Server Questions</b><br /><br />
-
-<a name="f4_10"></a>
-<font color="#2f486f">Q: Where can I find SILC servers?</font><br />
-A: The SILC server is available for free download from the silcnet.org
-web page. We are not aware of any other SILC server implementations, so far.
-<br /><br />
-
-<a name="f4_20"></a>
-<font color="#2f486f">Q: Can I run own SILC server?</font><br />
-A: Yes of course. Download the SILC server package, compile and install
-it. Be sure to check out the installation instructions and the README
-file. You also should decide whether you want to run SILC server or SILC
-router.
-<br /><br />
-
-<a name="f4_30"></a>
-<font color="#2f486f">Q: What is the difference between SILC
-server and SILC router?</font><br />
-A: The topology of the SILC network includes SILC routers and the SILC
-servers (and SILC clients of course). Normal SILC server does not have
-direct connections with other SILC servers. They connect directly to the
-SILC router. SILC Routers may have several server connections and they
-may connect to several SILC routers. The SILC routers are the servers in
-the network that know everything about everything. The SILC servers know
-only local information and query global information from the router when
-necessary.
-<br /><br />
-If you are running SILC server you want to run it as router only if you
-want to have server connections in it and are prepared to accept server
-connections. You also need to get the router connected to some other
-router to be able to join the SILC network. You may run the server as
-normal SILC server if you do not want to accept other server connections
-or cannot run it as router.
-<br /><br />
-
-<a name="f5_0"></a>
-<b>5. Toolkit Questions</b><br /><br />
-
-<a name="f5_10"></a>
-<font color="#2f486f">Q: What is SILC Toolkit?</font><br />
-A: SILC Toolkit is a package intended for software developers who would
-like to develope their own SILC based applications or help in the
-development of the SILC. The Toolkit includes SILC Protocol Core library,
-SILC Crypto library, SILC Key Exchange (SKE) library, SILC Math
-library, SILC Modules (SIM) library, SILC Utility library, SILC Client
-library and few other libraries.
-</font>
+++ /dev/null
-<b>Features</b>
-<font size="2">
-<br /><br />
-- Normal conferencing services such as private messages, channels, channel messages, etc. All traffic is secured and authenticated.
-<br /><br />
-- No unique nicknames. There can be same nicknames in SILC without collisions. SILC has unique Client ID's, Server ID's and Channel ID's to assure that there are no collisions. The maximum length of the nickname is 128 characters. The maximum length of the channel name is 256 characters.
-<br /><br />
-- Channels can have channel operators and a channel founder which is the client who created the channel. Channel founder privileges supersedes the channel operator privileges. Also, channel founder privileges may be regained even if the founder leaves the channel. The requirement for this is that the client is connected to the same server it was originally connected. The channel founder cannot be removed (kicked) from the channel using force.
-<br /><br />
-- Channel messages are protected by channel key, generated by the server. The key is re-generated once in an hour. It is possible to set a private key for the channel so that even the servers does not know the key. Actually, it is possible to set several private keys so that only specific users on the channel may decrypt some specific messages. Adding the private key significantly increases the security as nobody else but the users on the channel know the key.
-<br /><br />
-- Private messages are protected using session keys, generated when connecting to the server. This means that the private messages are decrypted and re-encrypted enroute to the true receiver of the message. However, it is possible to set a private key between two clients and protect the private messages with that key. In this case no server enroute can decrypt the message since they don't have the key. The SILC protocol provides an automatic key negotiation between two clients using the SKE protocol. This makes it very easy to negotiate a shared secret key with another client in the network.
-<br /><br />
-- All the other traffic, like commands between client and the server are protected using the session keys. Session keys are re-generated once in an hour. The re-key may be done with or without the PFS (Perfect Forward Secrecy).
-<br /><br />
-- Secure key exchange and authentication protocol. SILC Key Exchange (SKE) protocol provides key material used in the SILC sessions in secure manner. The protocol is immune for example to man-in-the-middle attacks and is based on the Diffie-Hellman key exchange algorithm. The SILC Authentication protocol provides strong authentication. Authentication may be based on passphrase or public key (RSA) authentication. For clients there is an option not to use authentication when connecting to servers.
-<br /><br />
-- All traffic is encrypted and authenticated using the best cryptographic algorithms out there. Cipher keys are, by default, 256 bits in length and public keys, by default, 1024 bits in length.
-<br /><br />
-- Supports the following ciphers: AES(Rijndael), Twofish, Blowfish, Mars, Cast-256, RC5 and RC6. Supports the following hash functions: MD5 and SHA1. Supports the PKCS #1 (RSA) for public key cryptography.
-<br /><br />
-- Supports data compression with GZIP to improve performance.
-<br /><br />
-- Supports SOCKS4 and SOCKS5 firewall traversal protocols.
-<br /><br />
-- SIM (SILC Module) support. Support for loading of shared objects at run-time that provides new and extended features to both SILC client and server. These can provide extra ciphers and extra features to the software.
-<br /><br />
-- SILC client can be installed and used without root privileges.
-<br /><br />
-- SILC client can be configured by system wide configuration files but with user specific configuration files as well.
-</font>
+++ /dev/null
-<b>History</b>
-<font size="2">
-<br /><br />
-SILC was released in the summer 2000 to the public, but the idea and the
-protocol itself is quite old. The SILC was designed by Pekka Riikonen in
-the year 1996 and first lines of codes were written in the early 1997. The
-SILC has been rewritten three times since its very first version in 1997.
-The first version included SILC client, very preliminary SILC server, RSA
-implementation and 3DES implementation. The server actually was not
-usable but the client looked pretty much the same as the first client
-released in the summer 2000. The first version had also random number
-generator which were based on the SSH's random number generator. The
-current RNG is based on the first RNG but has been rewritten twice since
-the first version.
-<br /><br />
-The development of SILC was suspended in 1997 when Pekka got busy at
-school and in work. The pause laster several months. The development
-resumed in 1998 when Juha Räsänen and Pekka implemented the ElGamal
-algorithm. However, for the same reasons as previously the development
-stopped again, and was resumed again later in 1998 by doing rewrite of
-ther SILC in C++. This was obviously a mistake but at that time it seemed
-like a good idea. Again, in the winter 1999 the development suspended when
-Pekka got busy writing his thesis and was forced to stop the development.
-<br /><br />
-Later, in 1999, it was decided that this time SILC will be rewritten from
-scratch in the right way. C++ was obviously a bad choice so plain C
-language was selected again. The protocol itself faced some rework by
-redesigning some core parts of the protocol. The protocol was also fully
-documented and the protocol specifications were submitted to the IETF.
-The result of this development effort is the release now in public. Since
-the release in the summer 2000 several other people have contributed to
-the project as well. And, the development continues.
-</font>
+++ /dev/null
-<b>Public SILC Mailing Lists</b>
-<font size="2">
-<br /><br />
-<b><font color="#2f486f">Available since Sat Jul 22 17:23:48 EEST 2000</font></b>
-<br /><br />
-There is currently one mailing list available. The mailing list is the
-main SILC development mailing list. To subscribe to the mailing list
-visit the following link and follow the instructions on the web page.
-<br /><br />
-<a href="http://lists.sourceforge.net/lists/listinfo/silc-devel">
-SILC-devel mailing list</a>
-<br /><br />
-After you have subscribed as instructed on the web site you will receive
-email for further instructions. To send email to the list the email must
-be destined to: <a href="mailto:silc-devel at lists.sourceforge.net">silc-devel at
-lists.sourceforge.net</a> address.
-</font>
+++ /dev/null
-<b>SILC Client <?php echo $latestc; ?> Is Now Available!</b>
-<br /><font size="1" color="#2f486f"><?php echo $latest_datec ?></font>
-<font size="2">
-<br /><br />
-The new version <?php echo $latestc; ?> of SILC Client is available!
-Read the README and INSTALL files after downloading for instructions how
-to compile and use SILC. Report bugs to the
-<a href="index.php?page=lists">SILC development mailing list</a>.
-<br /><br />
-Download: <a href="index.php?page=download">SILC Client <?php echo
-$latestc; ?> Version</a>
-<br />
-Changes: <a href="changes-client.txt">SILC Client <?php echo $latestc; ?>
-Changes</a>
-</font>
-
-<br /><br /><br />
-
-<b>SILC Server <?php echo $latests; ?> Is Now Available!</b>
-<br /><font size="1" color="#2f486f"><?php echo $latest_dates ?></font>
-<font size="2">
-<br /><br />
-The new version <?php echo $latests; ?> of SILC Server is available!
-Read the README and INSTALL files after downloading for instructions how
-to compile and use SILC. Report bugs to the
-<a href="index.php?page=lists">SILC development mailing list</a>.
-<br /><br />
-This version has the functional server and router linking support.
-People who is running SILC servers and are interested to get the server
-linked to the new router on silc.silcnet.org contact
-<a href="mailto:priikone at silcnet.org">me</a> now.
-<br /><br />
-Download: <a href="index.php?page=download">SILC Server <?php echo
-$latests; ?> Version</a>
-<br />
-Changes: <a href="changes-server.txt">SILC Server <?php echo $latests; ?>
-Changes</a>
-</font>
-
-<br /><br /><br />
-
-<b>SILC Toolkit <?php echo $latest; ?> Is Now Available!</b>
-<br /><font size="1" color="#2f486f"><?php echo $latest_date ?></font>
-<font size="2">
-<br /><br />
-The new version <?php echo $latest; ?> of SILC Toolkit is available! This
-package is intended for developers and programmers who would like to
-create their own SILC applications or help in the development of SILC
-protocol.
-<br /><br />
-Download: <a href="index.php?page=download">SILC Toolkit <?php echo
-$latest; ?> Version</a>
-<br />
-Changes: <a href="changes.txt">SILC Toolkit <?php echo $latest; ?>
-Changes</a>
-</font>
-
-<br /><br /><br />
-
-<b>SILC Server Available For Testing</b>
-<font size="2">
-<br /><br />
-There is SILC server up and running that can be tested. Just give command
-<font color="#2f486f">/server silc.silcnet.org</font> to connect to the
-server. There may be some action on channel #silc (unless everybody is
-sleeping) so you might want to give command <font color="#2f486f">/join
-#silc</font>.
-<br /><br />
-Available servers: silc.silcnet.org on port 706 is SILC Router and
-silc.silcnet.org on port 707 is normal SILC server connected to the
-router. Both are available for free use.
-</font>
+++ /dev/null
-<br />
-<tt>
-<font face="courier" size="3">
-<?php
-
-if (Is_Readable($DocRoot."todo.txt")) {
- $fp = FOpen($DocRoot."todo.txt", "r");
-
- while($line = FGets($fp, 255)) {
- $newline = Ereg_Replace("^[ ]{2,4}"," ",$line);
- $line = Ereg_Replace("^([\t]|[ ][\t])"," ",$newline);
- printf("%s", nl2br($line));
- }
-
- FClose($fp);
- }
-?>
-</font>
-</tt>
projects / silc.git / commitdiff
