On Tuesday 12 Oct 2010, John Cooper wrote:
> Great news. Sounds like a good plan to use the internal network server.
> Although I don't recommend using telnet to logon (unencrypted, password
> in clear text), it is great for diagnostics, like telnet ipaddress
We're not too worried about using telnet, because nothing will ever be
transmitted in clear text apart from within our very secure internal network.
Everything else will be through VPN.
> OpenSSH is a great tool, particularly for securing traffic like X using
> tunnelling. Saved a lot of hassle where very restrictive firewall rules
> are applied as you just need SSH port 22 open.
We thought about using SSH, but it was another hassle so we decided not to
bother.
> Good luck fixing the script ;-)
The script is OK now; I watched it run from end to end from my Windows laptop.
It's just getting remote access to work for all the corner cases. Hopefully
Terminal Services will solve all that.
--
Terry Coles
64 bit computing with Kubuntu Linux
--
Next meeting: Crown Hotel, Blandford Forum, Tuesday 2010-11-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://goo.gl/4Xue
