Pierre Sahores psahores at
Mon Jan 17 10:49:04 EST 2011

Andre and Folks,

I used the same way but, frankly, it was no far from unusable...

On the other hand, i prefer to see the mothership use this policy to avoid possible sad holes in the on-rev servers security.

But, i would really like to see the same mothership close all our unsecure FTP accesses and replace them by a FTP-SSL + password + PKEY or SFTP + password + PKEY  accounts access policy.

In between, to control the integrity of my on-rev account files on a daily basis and along other irev+MD5 dir scan scripts, i make a backup each night and scan then it from my dev box at home, in using ClamXav to be sure of the full integrity of my files. (As tested against real corrupted data set i own and use to choose and update antivirus tools, ClamXav is realy an usefull way to go on both the windows and os x platforms...)

All the best,


Le 17 janv. 2011 à 13:27, Andre Garzia a écrit :

> Folks,
> SSH is enabled only after request and the bad side is, they allow it only
> from fixed ip. So if you don't have a fixed ip, then you're lost. what I do
> is ssh to my vps server on jaguarpc which has a static ip then ssh from
> there to on-rev... lots of hops.

Pierre Sahores
mobile : (33) 6 03 95 77 70

More information about the Use-livecode mailing list