I don't know which is the best solution. The changes in wheezy regez seems backward compatible because the port and ssh2 tokens are optionals in the match, but as you say, the backage is unsupported.
My concern is that as now, it does not gives any protection but you can realize it is not working only watching on the logs.
Questions: 2.6-10+deb7u3 in more recente than 2.6-10.1?
Indeed you are right. A small research showed me denyhosts was removed from debian jessie: /packages. debian. org/search? keywords= denyhosts& searchon= names&suite= all§ion= all
https:/
The request of removal was due this bug report: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 732712
https:/
The project has been moved this this site and seems to be active (I think it is a fork): /github. com/denyhosts/ denyhosts
https:/
I don't know which is the best solution. The changes in wheezy regez seems backward compatible because the port and ssh2 tokens are optionals in the match, but as you say, the backage is unsupported.
My concern is that as now, it does not gives any protection but you can realize it is not working only watching on the logs.
Questions: 2.6-10+deb7u3 in more recente than 2.6-10.1?