diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-April/000402.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-April/000402.html')
| -rw-r--r-- | pipermail/nel/2001-April/000402.html | 123 |
1 files changed, 123 insertions, 0 deletions
diff --git a/pipermail/nel/2001-April/000402.html b/pipermail/nel/2001-April/000402.html new file mode 100644 index 00000000..feee946b --- /dev/null +++ b/pipermail/nel/2001-April/000402.html @@ -0,0 +1,123 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] A small document for your consumption</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000401.html"> + <LINK REL="Next" HREF="000403.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] A small document for your consumption</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] A small document for your consumption">archer@nevrax.com</A><BR> + <I>Fri, 13 Apr 2001 11:34:53 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000401.html">[Nel] proposed control changes</A></li> + <LI> Next message: <A HREF="000403.html">[Nel] A small document for your consumption</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#402">[ date ]</a> + <a href="thread.html#402">[ thread ]</a> + <a href="subject.html#402">[ subject ]</a> + <a href="author.html#402">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>While waiting for the whole load, here's a quick and short document. Look +at it, and critique your hearts out... + +Client server connect + +This document describes quickly the connection process of a client to a world +running a NeL-based system. + +Abbreviations +------------- + +LS: The login service (one overall) +WS: The welcome service (one for each world) +FES: The front-end service (N per world) + +Steps +----- + +1: The client initiates a connection to the login service, using the supplied + IP and port from the configuration file, with the help of the DNS for IP + resolution. + + Note: DNS spoofing or configuration file modification can lead to LS + spoofing and hacking of the login/password information of the client. + However, DNS is needed for flexibility of the login service location. + +2: The client submits its login, password, and system capabilities. + +3: The LS checks the login/password validity, and builds the list of all + available worlds according to account information and current system + settings. This list contains world names and the IP for the WS of that + world. + + Note: DNS is not used in that step. + +4: The client selects the world it wants to log on, and submits the IP address + of its world service to the LS. + +5: The LS sends a notification to the selected WS of the client's connection + desires. It generates and submits a single-use cookie to validate the + incoming connection. + + Note: The cookie includes the client's IP, as seen by the LS (to avoid + address translation problems) for validation. + +6: The WS selects a FES to accept the client connexion, and submits the cookie + to the FES. + +7: The FES acknowledges its capacity to accept the client to the WS. + +8: The WS acknowledges its capacity to accept the client to the LS, and + indicates the IP/port of the selected FES. + +9: The LS acknowledges the login request to the client, and indicates the + IP/port of the selected FES. + +10: The client disconnects from the LS. + +11: The client initiates a connection to the indicated FES. + +12: The client sends the submitted cookie to the FES. + +13: The FES validates and acknowledges the cookie. + +Side notes +---------- + +Whenever a world starts, the WS establishes a permanent link with the LS, +using an encrypted link (it is assumed that the LS and WS are located on two +physically and probably geographically distinct networks). A 'SHARD' message +serves as authentification, and the WS then updates the LS with its state, +name and IP address. The WS may have a list of valid IP/port address for WS +to avoid the occasional pirate server registration. + +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000401.html">[Nel] proposed control changes</A></li> + <LI> Next message: <A HREF="000403.html">[Nel] A small document for your consumption</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#402">[ date ]</a> + <a href="thread.html#402">[ thread ]</a> + <a href="subject.html#402">[ subject ]</a> + <a href="author.html#402">[ author ]</a> + </LI> + </UL> +</body></html> |