1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<!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:thierry%40mallard.com">
<LINK REL="Previous" HREF="000402.html">
<LINK REL="Next" HREF="000407.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] A small document for your consumption</H1>
<B>Thierry Mallard</B>
<A HREF="mailto:thierry%40mallard.com"
TITLE="[Nel] A small document for your consumption">thierry@mallard.com</A><BR>
<I>Mon, 16 Apr 2001 21:59:43 +0200</I>
<P><UL>
<LI> Previous message: <A HREF="000402.html">[Nel] A small document for your consumption</A></li>
<LI> Next message: <A HREF="000407.html">[Nel] A small document for your consumption</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#403">[ date ]</a>
<a href="thread.html#403">[ thread ]</a>
<a href="subject.html#403">[ subject ]</a>
<a href="author.html#403">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Fri, Apr 13, 2001 at 11:34:53AM +0200, Vincent Archer wrote:
><i> Steps
</I>><i> -----
</I>><i>
</I>><i> 1: The client initiates a connection to the login service, using the supplied
</I>><i> IP and port from the configuration file, with the help of the DNS for IP
</I>><i> resolution.
</I>><i>
</I>><i> Note: DNS spoofing or configuration file modification can lead to LS
</I>><i> spoofing and hacking of the login/password information of the client.
</I>><i> However, DNS is needed for flexibility of the login service location.
</I>
Possibly this can be partially avoided by providing your own DN Server's IP ?
(dunno precisly how the client would connect to it, but still...)
><i> 2: The client submits its login, password, and system capabilities.
</I>
In plaintext ?
><i> 3: The LS checks the login/password validity, and builds the list of all
</I>><i> available worlds according to account information and current system
</I>><i> settings. This list contains world names and the IP for the WS of that
</I>><i> world.
</I>
Maybe the use of challenges would be more secure, but i'm not a specialist in
this matter :-(
><i> 4: The client selects the world it wants to log on, and submits the IP address
</I>><i> of its world service to the LS.
</I>
Would it be good if the client could select several worlds ?
(then the negociation following could use this to get a good WS)
><i> [...]
</I>><i> 10: The client disconnects from the LS.
</I>><i>
</I>><i> 11: The client initiates a connection to the indicated FES.
</I>
I wonder if it couldn't be more interesting if the client disconnects from LS
_after_ having initiated the connection to the FES. Then, if something goes
wrong, the client could goto 4 directly.
Best regards,
--
Thierry Mallard | <A HREF="http://vawis.net">http://vawis.net</A>
GnuPG key on wwwkeys.pgp.net | <A HREF="http://erlang-fr.org">http://erlang-fr.org</A> (new)
key 0xA3D021CB | <A HREF="http://worldforge.org">http://worldforge.org</A>
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000402.html">[Nel] A small document for your consumption</A></li>
<LI> Next message: <A HREF="000407.html">[Nel] A small document for your consumption</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#403">[ date ]</a>
<a href="thread.html#403">[ thread ]</a>
<a href="subject.html#403">[ subject ]</a>
<a href="author.html#403">[ author ]</a>
</LI>
</UL>
</body></html>
|
