– IP (range) limits as of where the server serves its music and lists to
– Something like a relogin delay on 5x wrong password or so
Some address based stuff will probably go in there, but that will be more for setting configuration — transcoding to mp3 based on destination ip address, for example.
From the standpoint of security, if I do implement something, it will probably to enable optional compilation with libwrap.
On the other hand, it’s never really meant to be an internet accessible server. I certainly wouldn’t use it in that capacity. I haven’t really given it the hard look that it would have to have for me to feel comfortable using it exposed on the public internet. That’s why all the documentation refers to using ssh tunnels.