The host manager is where you set up your connection to the mldonkey core.
Host = The IP address of the machine on which the mldonkey core is running.
Use "localhost" or "127.0.0.1" if it is the same machine as sancho.
Port = The port. mldonkey uses 4001 by default for its gui communication.
User/Pass: "admin/<empty>" is the default in mldonkey. Use the "add_user admin <newpass>"
command in mldonkey (telnet|web|console) to change it.
If you want to connect to your mldonkey core using an ssh2 tunnel, you can optionally enable this (advanced users).
This uses JSch and your JVM's internal crypto libraries.
A connection will be made to the remote host
Set the "SSH host" to the IP of the remote system, and set the "SSH user" to the login name of the user. The default port is 22.
Why would you want to store an ssh password here? Well, normally you wouldn't. If you leave it blank, you will be prompted for the password each time
you try to initiate a connection. If you store one here it will be written to disk as plain-text. I can't think of any way to reliabily store it -- and
pretending that it is encrypted by just encoding it would give a false sense of security.
One option is to store it on an encrypted disk (pgpdisk or similar), and run "sancho -j x:\" to save the pref file to the encrypted x: drive. Far from safe, but... you are in charge of your own security.
(Note: It uses ~/.ssh/known_hosts for the known_hosts file, unless you use -j, in which case it uses the directory you specify)
The "SSH local port" is the port you most likely set as "Port:" in the main settings since it will be the one sancho tries to connect with.
The remote host/remote port paramters set the interface to connect with on the remote host. If mldonkey core has a gui port open on 192.168.1.1:4001 then set it here. Most likely it is 127.0.0.1:4001.
The host manager also lets you add entries for other mldonkey cores and save them. The buttons should be pretty self explanatory.
To use ssh without a password:
"ssh-keygen -t dsa" and don't enter a password (creates ~/.ssh/id_dsa and id_dsa.pub)
cd ~/.ssh ; cat id_dsa.pub >> authorized_keys (appends public key to openssh authorized_keys file)
move id_dsa (private key) to the sancho machine and put it in ~/.ssh/id_dsa
(windows: c:\documents and settings\username\.ssh\id_dsa)
sancho will automatically read ~/.ssh/id_dsa (and/or id_rsa) if they exist
(** gcj compiled sancho might have problems with id_rsa, try id_dsa or the sancho-java version
if experiencing id_rsa problems **)
SSH2 NOTE: (might not be required if using 0.9.4-22 or newer and id_dsa)
In order for SSH2 tunneling to function correctly one must ensure that the
following line is uncommented in /etc/ssh/sshd_config :
--------------------------CUT-------------------------------
# Change to yes to enable tunnelled clear text passwords
PasswordAuthentication yes
--------------------------CUT-------------------------------
Otherwise the initiation of the tunnel will fail with
"SSH Initialization failed, try again?
com.jcraft.jsch.JSchException: Auth fail"
|