clm — yes it is impossible for FTP servers to determine which “virtual domain” you are connecting to, as unlike HTTP the hostname is never sent — unless it is part of the username.
For the FTP servers I manage, I just have policy of having “username@hostname” as the full username. With Pure-FTP it is easy to write an external authenticator that maps the user into the correct unix user + base directory.
And only one IP address used :)
Btw, I think FTP should die. It’s persistent and stateful (i.e. taking up server resources while idling), and the hard to configure the firewall.
anonymous — yes I have mentioned HTTPS. Maybe when HTTP implements TLS?
clm — yes it is impossible for FTP servers to determine which “virtual domain” you are connecting to, as unlike HTTP the hostname is never sent — unless it is part of the username.
For the FTP servers I manage, I just have policy of having “username@hostname” as the full username. With Pure-FTP it is easy to write an external authenticator that maps the user into the correct unix user + base directory.
And only one IP address used :)
Btw, I think FTP should die. It’s persistent and stateful (i.e. taking up server resources while idling), and the hard to configure the firewall.
anonymous — yes I have mentioned HTTPS. Maybe when HTTP implements TLS?