Allow differing uam configuration for clients by transport/interface/subnet

[alohawolf]

I have a mix of vintage mac's using AppleTalk, modern macs that use afp over iP, and frequently use AFPoIP over the public internet (I know, not recommended).

What I'd like to have one set of uams for the DDP interface which use very simple uam's that will support system 7, and then modern high security ones for IP based AppleTalk. It would also be nice to allow less secure UAM's by IP subnet.

[NJRoadfan]

I think Netatalk 2.x used to have this flexibility, but the re-architecture of the configuration code in 3.x eliminated that ability. In theory, configuring separate UAMs for AppleTalk and TCP/IP are possible with the current code. Realistically nobody should be running AFP over the Internet without some sort of VPN. Besides the authentication stages (which aren't that secure by today's standards), the rest is completely unencrypted.