Mirando los feeds, he visto un articulo/tecnica/script que me ha parecido muy interesante:
su web escribió:This utility dynamically adds a source address to be approved to access the SSH port on my home computer. It uses a property similar to "port knocking" that I will call "page knocking". For this example, a client accesses http:/access.html and this causes the source address of the http page request to be added to an approved list. (Of course, the page 'access.html' is not the same as the page on my production computer). This client can then access my SSH port.This utility dynamically adds a source address to be approved to access the SSH port on my home computer. It uses a property similar to "port knocking" that I will call "page knocking". For this example, a client accesses http:/access.html and this causes the source address of the http page request to be added to an approved list. (Of course, the page 'access.html' is not the same as the page on my production computer). This client can then access my SSH port.
While my web server is intentionally always available to the Internet, I also like to be able to SSH into my computer. I consider the SSH access a higher security risk due to the fact that SSH is not chrooted. Since the web server is accessible anyway, having more accessible interfaces just increased the targets available for attack. Finally, it may be policy in some places not to expose administrative interfaces directly to the Internet. While this last point could be called 'security by obscurity', it is still effective at managing any untargetted (worm, etc) attack directed to the SSH port at my site.
