|
|
 |
| WiredX HowTo |
Requirements
To use WiredX, you need
- Windows 95/98/NT/2000 machine,
- InternetExplorer or NetscapeNavigator,
- Java2 Plug-in(v 1.3.* is preferable) and
- of course, Unix machines on your LAN for running x clients.
If you use Gnome and KDE on the WiredX,
Celeron 400MHz, 64MB RAM machine is preferable.
|
|
|
Step 1. Registration
First of all, please sign up.
It is easy and free.
|
| |
Step 2.
Download and install Java2 Plug-in if you have not done yet.
Java2 Plug-in(J2SE 1.3.*) can be downloaded from
JavaSoft.
|
| |
Step 3.
Grant WiredX the socket access permissions.
WiredX is just a Java applet, so WiredX can't accept any socket
connections from X clients without your granting.
Java2 introduces policy-based, fine-grained access control.
When code is loaded, it is assigned "permissions" based on
security policy rules and policy rules are described in policy files.
A brief introduction about new security features of Java2
is available at
Sun Microsystems.
| |
Step 3.1.
Open the file 'java.policy' in a text editor.
This file is located in the directory ./lib/security,
where "." is the directory you installed the JRE in.
Windows: The default directory is
c:\Program Files\JavaSoft\JRE\1.3\lib\security\.
The easiest way to locate and open the file is to select
"search/files or folders" from the Start Menu and
search for java.policy. Then doubleclick the file, and
select "wordpad" from the list that appears.
|
| |
|
| |
Step 3.2.
Add following lines to 'java.policy'.
grant codeBase "http://wiredx.net/-" {
permission java.lang.RuntimePermission "usePolicy";
permission java.net.SocketPermission "*", "accept,listen,connect,resolve";
};
Make sure you get the case correct.
By this policy rule, byte-codes from "http://wiredx.net/"
are granted to accept connections from any host
and to connect to any host.
We strongly recommend to replace "*" with hosts on your LAN,
for example "*.foo.com".
You can generate policy files by yourself, using policytool.
Its nice tutorial is available at
Sun Microsystems.
|
| |
Note 1: WiredX will be brought to your browser as a signed applet,
so if above first rule(usePolicy) is missing, above policy rule
will be ignored and
you will be prompted to grant 'AllPermission' or not.
|
| |
Note 2: To apply above rule correctly,
your JVM must be able to resolve 'wiredx.net' to
an ip-address(125.101.47.164).
Please check DNS configurations of
your desktop machine if you are accessing the Web via proxies.
If you don't have a DNS server on your LAN,
please add a next line to \windows\hosts file,
125.101.47.164 wiredx.net
|
|
|
| |
Step 4.
Sign-in, fill the form on your personal page
and submit it.
In the default, if you sign-in,
you will be on your personal page for WiredX.
At first time, just click start button on your personal page.
In responding to your request,
WiredX.net will send WiredX to your web browser
in a jar format file(about 200KBytes) immediately.
If everything works well, WiredX will start and
a white window will appear on your web browser.
It is a root window of WiredX.
Now, you can run X clients on Unix machines with appropriate -display option. In the default, display name is a 'hostname_of_your_PC:0'.
So telnet to the unix machine and
exec 'xlogo -display hostname_of_your_PC:0'.
Of course, if you use XDMPC/REXEC functionalities,
you don't have to telnet to somewhere to start x clients.
Tips:
If you are using IE on Window9X and you have encountered the crash of
IE in starting up WiredX,
enable Java Console on Java Plug-in control panel and try again.
We don't know the reason, but this trick works.
It seems there are reproducible problems
in the combination of Java Plug-in v.1.3 and IE, Windows9X.
|
|
|
|
