Re: Tramp 2.0 -> 2.1 migration woes

[Michael Albinus]

"Trent W. Buck" <address@hidden> writes:

> On Mon, Jan 28, 2008 at 05:31:32PM +0100, Michael Albinus wrote:
>>> I'm also not sure that middling to complicated proxying
>>> arrangements can even be set up with the current
>>> tramp-default-proxies-alist.  For example, suppose a host allows
>>> ssh from anywhere, but locks down its internal staff-only FTP
>>> upload area to sites on the corporate subnet?  You'd need to have
>>> the /ftp:appdev:/incoming use an /ssh:gw: proxy, but /ssh:appdev:
>>> should not use any proxy (although it would still work with one,
>>> it would just waste gw's bandwidth).

[...]

> I think I haven't been clear.  In the example above, it's desirable to
> dispatch on method as well as hostname and userename.

The example above couldn't be handled by Tramp, because it does not
support multi hops with an ftp method at the end. Tramp forwards all
ftp related actions to ange-ftp, which opens a *local* ftp client
subprocess.

Best regards, Michael.