| Sign In/My Account | View Cart |
| Article: |
Inside SSH, Part 4 | |
| Subject: | I return often . . . | |
| Date: | 2006-05-27 05:05:07 | |
| From: | rbannon@mac.com | |
|
. . . to this wonderful four-part series on using ssh under Mac OS X. I hope it never disappears, and I'm sure once 10.5 is released we're all going to need an ssh configuration update . . . I hope you're willing to do so.
|
||
Showing messages 1 through 3 of 3.
I return often . . .Feb 11 08:21:12 beelzebub Firewall[57]: Allow sshd-keygen-wrapper connecting from 220.225.110.237:39098 uid = 0 proto=6". Not just one entry, but repeated and persistent entries coming from multiple IPs. Yikes!http://it.slashdot.org/article.pl?sid=07/01/20/1936257
Thank you for your kind words, they are much appreciated! I am glad the article is of interest to you.
The article you link to is indeed most interesting. It is true that the advice I endeavored to outline here, while good for a start, certainly should not be considered as the ultimate in security for state secrets and it would be dangerous to enable SSH on all secure servers, even by using a strong key-based authentication mechanism.
The article you mention however mostly mention misuse of SSH tunnels by users who forget that, even though SSH encrypts the connection between two machines, it does create a connection. In this regard, linking a secure server to an insecure server, no matter how strong the channel is still opens up ways for an attacker already "owning" the insecure server to crawl its way up into the secure zone of your network (if I am permitted to use such an image).
The advice outlined there certainly is not to be downplayed. It remains however (at least in this part of the series) focused on one problem that has much to do with carefree port forwarding.
FJ