<a href=showthread.php?s=&postid=9855020#post9855020 target=_blank>Originally posted</a> by lvreefer
None taken. But at first I was a little flamed at;“Being a network engineer, you of all people should know betterâ€Â. Okay, I’m over it. I didn’t mean have none. I simply meant that every networking product on the shelf has wide open security out of the box. The user has to implement some form of security in which the product supports. SSL and/or SSH would be a good idea but I can not see how an Aqua Controller could handle these request. You would have to turn the controller into a fat client. At that point you might as well move all of the code off of the AC and have it only as a TTL interface.
The original point that I DID NOT make clear, was to leave the top level security to the gear that can handle it; firewalls (soft and hardware), router(s), antivirus/malware scanner, and a web server (well apache). Adding this additional functionality to an Aqua controller would either make it slower to respond or raise the price dramatically. Since most of us that are using the AC’s web interface are broadband online as well, I figure we already have the gear.
