Monte Goulding wrote: > You probably want to make sure the remote user is pretty restricted > too. Anyone that has control of your web server user will have > control of that account too.
Good thought. I try to keep in mind all connection points between servers I manage, and on my own I also completely disable password login, lock out root, and move SSH to a non-standard port (the latter isn't for security of course, just to keep logs readable by reducing script kiddie noise).
In this case both servers only live within the client company's internal network, and given their annoyingly well-enforced password policies I feel okay with this setup for now.
I'd still prefer a wrapper solution, if only I could find one that works. But for now at least a deadline is met, and with both machines on the same rack the transfer speed is wonderfully fast.
-- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ [email protected] http://www.FourthWorld.com _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
