Business Community > All Threads > Feature request for VPN/IPSec, HMAC-SHA2 and AES-GCM, the current is not secure!
< All Threads
 
9
Votes

Feature request for VPN/IPSec, HMAC-SHA2 and AES-GCM, the current is not secure!

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
9
Votes

Feature request for VPN/IPSec, HMAC-SHA2 and AES-GCM, the current is not secure!

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Feature request for VPN/IPSec, HMAC-SHA2 and AES-GCM, the current is not secure!
Feature request for VPN/IPSec, HMAC-SHA2 and AES-GCM, the current is not secure!
2021-07-08 07:50:38 - last edited 2021-07-09 10:33:36
Model: ER7206 (TL-ER7206)  
Hardware Version: V1
Firmware Version: 1.0.1 Build 20210113 Rel.35468

Dear TP-Link,

 

The MD5 and SHA1 is not safe anymore. Please use/implement HMAC-SHA1/SHA2  and AES-GCM (compatible) or ChaCha20-Poly1305 (faster on ARM than AES) more info here. The TL-SG3428 V2 switch already has AES-GCM and SHA2 (SHA256, SHA384) implementation, so it should not be a big effort.

 

Sincerely,

Gergely

#1
Options

Information

Helpful: 9

Views: 1155

Replies: 0

Voters 4

voter's avatar
voter's avatar
voter's avatar
voter's avatar
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.