AWS wickr documentation change
Summary
Updated network troubleshooting documentation to clarify UDP blocking behavior and added administrative option to force TCP calling
Security assessment
The change describes protocol behavior (UDP fallback to TCP) and administrative controls for network configuration. No security vulnerabilities or weaknesses are mentioned. The TCP enforcement option is a network reliability feature, not a security control.
Diff
diff --git a/wickr/latest/adminguide/troubleshoot-network.md b/wickr/latest/adminguide/troubleshoot-network.md index 0f117fac3..45b2e50f0 100644 --- a//wickr/latest/adminguide/troubleshoot-network.md +++ b//wickr/latest/adminguide/troubleshoot-network.md @@ -148 +148 @@ Resolution -Wickr uses UDP for voice and video calls. If your network blocks UDP, calls will fail to connect or drop immediately, while messaging continues to work normally. +Wickr uses UDP for voice and video calls by default and falls back to TCP. If your network blocks UDP, calls will fail to connect right away and will fall back to TCP with potentially degraded performance, while messaging continues to work normally. You can enable (force) TCP calling within the Wickr Network Security Group to skip UDP entirely, forcing all calls to TCP. @@ -153 +153 @@ Diagnostic -Ask the affected user to enable TCP calling as a test: **Settings** , **Calling** , enable **TCP calling**. If calls succeed with TCP enabled, UDP is blocked. +Ask the affected user to enable TCP calling as a test (or administratively enable/force TCP through the console for all users): **Settings** , **Calling** , enable **TCP calling**. If calls succeed with TCP enabled, UDP is blocked.