|
From: Jamie C. <jca...@we...> - 2006-06-28 22:41:48
|
On 28/Jun/2006 16:19 Alan Dobkin wrote .. > On 6/28/2006 2:14 PM, Jamie Cameron wrote: > > Indeed .. I presume you aren't running the browser on the same host > > as your Webmin server? If not, Java shouldn't even be allowed to connect > > to localhost! > > > > No, I am running Webmin on a CentOS Linux server and the browser on my > Windows XP desktop. From a security standpoint, I think it is okay that > Java is connecting to localhost, since it is technically using an open > network port on my machine and prompts for authentication. It is not > connecting directly to the local machine filesystem from the Java applet. > > According to netstat, here is the connection from that applet to my > local ssh port: > > TCP Desktop:43556 localhost:ssh ESTABLISHED 2624 > [iexplore.exe] > > > Are you by any change accessing Webmin through some kind of proxy or > Apache > > forwarding virtual host? This may be confusing the module .. > > No, in this case I have a direct HTTPS connection to the Webmin server. > > On 6/28/2006 3:21 PM, Jamie Cameron wrote: > > What does the 'hostname -f' command output when run at the shell prompt > on > > your system? If it is returning localhost, this may be confusing Webmin.. > > The hostname -f command displays my system's fully-qualified domain > name, which is the same name I am using in the URL to connect to the > Webmin server. This is very strange then, especially if it only started happening in Webmin 1.280, as they only change in that release was the addition of proxying support, which you aren't using. Does this still occur if you change the 'SSH applet to use' option on the Module Config page to 'Old version' ? - Jamie |