I would like to open the web interface up to the internet so that I can schedule torrent downloads anywhere. However, I do not feel that it is secure enough. My biggest problem at the moment is with brute force attacks. What is printed in the log when there is an authentication failure is nowhere near sufficient for utilities such as fail2ban. If the log was beefed up to include IP addresses and time-stamps, that would be enough for others like me to solve this particular problem. Another option is to improve the security in house and add the applicable security and configurations to KTorrent's settings.

Please note that feature requests made on the forum may be missed. As a workaround, I would suggest using Apache or Nginx in front of KTorrent, as they should both be more than capable of producing the needed logs for fail2ban.