updates.

diff --git a/doc/whitepaper/Makefile.am b/doc/whitepaper/Makefile.am
new file mode 100644 (file)
index 0000000..1eba181
--- /dev/null
+++ b/doc/whitepaper/Makefile.am
@@ -0,0 +1,29 @@
+#
+#  Makefile.am
+#
+#  Author: Pekka Riikonen <priikone@silcnet.org>
+#
+#  Copyright (C) 2001 Pekka Riikonen
+#
+#  This program is free software; you can redistribute it and/or modify
+#  it under the terms of the GNU General Public License as published by
+#  the Free Software Foundation; either version 2 of the License, or
+#  (at your option) any later version.
+#
+#  This program is distributed in the hope that it will be useful,
+#  but WITHOUT ANY WARRANTY; without even the implied warranty of
+#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#  GNU General Public License for more details.
+#
+
+AUTOMAKE_OPTIONS = 1.0 no-dependencies foreign
+
+HTML2PS = ../../scripts/html2ps -f ../../scripts/html2psrc
+
+all:   make-html2ps make-ps2pdf
+
+make-html2ps:
+       ($HTML2PS) -o silc_protocol.ps silc_protocol.html
+
+make-ps2pdf:
+       ps2df silc_protocol.ps

diff --git a/doc/whitepaper/silc_protocol.html b/doc/whitepaper/silc_protocol.html
index 613580742b8e507c50bbb22ab23af73b3eebd84b..1549f7e7e68abd177b0ba897e56d8d325aaf3e31 100644 (file)
--- a/doc/whitepaper/silc_protocol.html
+++ b/doc/whitepaper/silc_protocol.html
@@ -100,7 +100,9 @@ The cell can also have backup routers in case the private router becomes
 unresponsive.
 
 <p><br>
+<object data="silc_network.jpg" type="application/postscript">
 <img src="silc_network.png" alt="SILC Network" align="center" border"0">
+</object>
 <p><br>
 
 The diagram above illustrates a portion of the SILC network.  It shows
@@ -223,7 +225,9 @@ the ring is closed by the last router using the first router in the
 network as its primary route.
 
 <p><br>
+<object data="silc_routers.jpg" type="application/postscript">
 <img src="silc_routers.png" alt="SILC Routers" align="center" border"0">
+</object>
 <p><br>
 
 The diagram above illustrates how the routers forms a ring in the network.
@@ -258,7 +262,9 @@ of the packet.  Hence, the actual data in the packet is the packet payload
 defined in the protocol.
 
 <p><br>
+<object data="silc_packet.jpg" type="application/postscript">
 <img src="silc_packet.png" alt="Typical SILC Packet" align="center" border"0">
+</object>
 <p><br>
 
 As the diagram above illustrates the SILC packet is constructed from the
@@ -439,9 +445,9 @@ the cell the channel key is known by the router and all servers that
 have clients on the channel and all clients that have joined the channel.
 
 <p><br>
-<OBJECT data="silc_channel.jpg" type="application/postscript">
+<object data="silc_channel.jpg" type="application/postscript">
 <img src="silc_channel.png" alt="Channel Message Delivery" align="center" border"0">
-</OBJECT>
+</object>
 <p><br>
 
 The diagram above illustrates typical delivery of channel messages inside
@@ -563,7 +569,9 @@ receiving client.  This also means that the message is decrypted and
 re-encrypted everytime it is sent further to the receiving client.
 
 <p><br>
+<object data="silc_priv1.jpg" type="application/postscript">
 <img src="silc_priv1.png" alt="Basic Private Message Delivery" align="center" border"0">
+</object>
 <p><br>
 
 As the above diagram shows the private messages sent by Client A to the
@@ -604,7 +612,9 @@ does not matter whether the clients trust or do not trust the servers and
 routers in the SILC network.
 
 <p><br>
+<object data="silc_priv2.jpg" type="application/postscript">
 <img src="silc_priv2.png" alt="Private Messages with Private Message Key" align="center" border"0">
+</object>
 <p><br>
 
 As the above diagram shows the Client A encrypts the message with private
@@ -664,7 +674,9 @@ receiver's private key.  The receiver on the other hand has the private
 key which it uses to decrypt the message.
 
 <p><br>
+<object data="silc_priv3.jpg" type="application/postscript">
 <img src="silc_priv3.png" alt="Private Messges with Public Key Cryptosystem" align="center" border"0">
+</object>
 <p><br>
 
 As the above diagram shows the Client A has the Client B's public key.