Re: rssh.el interactions with ange-ftp/efs

rms> ssh is particularly nasty, because it is not free software, rms> but people are being lured into using it anyway. ssh-1.2.x is freely distributable and the author has repeatedly clarified a broad interpretation of "non-commercial" use that IIRC extends to practically anything short of selling the code outright, but IANAL. Anyway, ssh-1.2.x is widely deployed. ssh-2.x has a restrictive license, is viewed by many as being problematical in other ways, and probably will not soon have anything like the following that ssh-1.2.x has had. The GPLed LSH implementation of the ssh protocols does not look like it will be ready for non-combatant use for some time. In the interim having efs use the GPLed ftpsshd or a work-alike (or _be_ a work-alike) would let folks use strong encryption _now_ and, it would seem, should be easy to make work with a rudimentary LSH until such time as LSH has its own secure ftp. Having this established and working would also seem to help encourage future secure ftp implementations to remain compatible with classic ftp rather than follow only the approach taken by the ssh-2.x sftp. Is it better to cut off the nose to spite the face of ssh-1.x being freely distributed and used without the GPL or to go ahead with a capability that is wanted by many and that will help to establish the routine use strong cryptography by everyone? Would it be better to continue to force those with hard security requirements to find solutions outside their Emacsen and without Open Source? Who will that benefit? FWIW IMHO the worsening developments with ssh-2.x make a strong case for the GPL over and above quasi open/free licenses. Providing an alternative to the sftp of the commercial ssh-2.x can not be all bad. jam