Rev 5513 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 5513 | Rev 5903 | ||
|---|---|---|---|
| Line 2... | Line 2... | ||
| 2 | <p> |
2 | <p> |
| 3 | Definition of hosts in WIMS can be made either through host name or IP |
3 | Definition of hosts in WIMS can be made either through host name or IP |
| 4 | number. But we highly recomment that you use IP numbers whenever possible. |
4 | number. But we highly recomment that you use IP numbers whenever possible. |
| 5 | Host names are not as secure. |
5 | Host names are not as secure. |
| 6 | <p> |
6 | <p> |
| 7 | You can also define global host names in the usual way: <tt>127 |
7 | You can also define global host names in the usual way: <span class="tt">127.0.0.</span> |
| 8 | (but not <tt>127. |
8 | (but not <span class="tt">127.0.0</span>) |
| 9 | matches 127.0.0.1 to 127.0.0.255, and < |
9 | matches 127.0.0.1 to 127.0.0.255, and <span class="tt">.unice.fr</span> |
| 10 | (but not < |
10 | (but not <span class="tt">unice.fr</span>) matches any host in the domain <em>unice.fr</em>. |
| 11 | <p> |
11 | <p> |
| 12 | <p> |
12 | <p> |
| 13 | Finally, the word < |
13 | Finally, the word <span class="tt">all</span> matches every host in the world. This is hugely |
| 14 | insecure, but if you choose it, that is your problem. |
14 | insecure, but if you choose it, that is your problem. |
| 15 | 15 | ||
| 16 | 16 | ||