opiousk, I did a little searching and dug up<a href="http://forums.linksys.com/linksys/board/message?board.id=Wired_Routers&thread.id=15592">[/A this web link for you.] It answers your question directly that yes, the RVS4000 VPN does indewed use AES-256 encryption, but the site also goes into detail on some things that the author(s) found when setting up the quick VPN setup with this unit. I hope you find the information useful.
Last Wiki Answer Submitted: April 1, 2009 3:50 pm by CRagsdale32755 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Searching the web I had seen that blog – and it confused me – because on the one hand it suggests that are doing AES-256 … yet AES-256 is not one of the options in the menu.
It was this blog entry that sent me searching from software updates that might add this feature to the RVS4000.
Does anyone have any other suggestions?
From the blog …
2. The setup begins with an https (TLS) authentication protocol, using the router’s PEM certificate for authentication, assuming you have sent that client certificate to whoever is going to be logging on, so they can install it in their install directory. (Otherwise, they will have to answer “no” to the question of whether to disconnect. This in turns leaves them vulnerable to a man-in-the-middle hijacking attack.) This authentication protocol is carried out with AES-256, which is certainly good, but with RSA-1024 and SHA-1, both of which are now deprecated as not being strong enough
Searching the web I had seen that blog – and it confused me – because on the one hand it suggests that are doing AES-256 … yet AES-256 is not one of the options in the menu.
It was this blog entry that sent me searching from software updates that might add this feature to the RVS4000.
Does anyone have any other suggestions?
From the blog …
2. The setup begins with an https (TLS) authentication protocol, using the router’s PEM certificate for authentication, assuming you have sent that client certificate to whoever is going to be logging on, so they can install it in their install directory. (Otherwise, they will have to answer “no” to the question of whether to disconnect. This in turns leaves them vulnerable to a man-in-the-middle hijacking attack.) This authentication protocol is carried out with AES-256, which is certainly good, but with RSA-1024 and SHA-1, both of which are now deprecated as not being strong enough
I felt like I was listening to a friend when I read your story posted on your blog.