Like rfugger, I also had Tomato installed, but had never known about its SSH daemon. After Firesheep was released, I went looking for a cheap way to secure my computers' traffic. Originally, I intended to use EC2, since Amazon is giving it away for free for a year, but this solution seemed like a better route for me. If the ISP (Cox Communications) does get grumpy, I'll probably go the EC2 route.
As for the dynamic IP issue, Tomato can also be setup to work with a DynDNS account.
Comments
Like rfugger, I also had Tomato installed, but had never known about its SSH daemon. After Firesheep was released, I went looking for a cheap way to secure my computers' traffic. Originally, I intended to use EC2, since Amazon is giving it away for free for a year, but this solution seemed like a better route for me. If the ISP (Cox Communications) does get grumpy, I'll probably go the EC2 route.
As for the dynamic IP issue, Tomato can also be setup to work with a DynDNS account.