You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless allow connect to ocsp.digicert.com, crl4.digicert.com, crl3.digicert.com currently stuck on 'This server can't be reached' window. https://github.com/wireapp/wire/issues/338 however i noticed app keep consume 8-10MB bandwidth per client for wire domains regularly only for an hour
DNSSEC on wire.com wireapp/wire#328 @raphaelrobert
You are right, it is a limitation of AWS. We use certificate pinning at the leaf level to make sure the Wire apps connect to the right servers.
This discussion was converted from issue #3897 on May 31, 2021 14:26.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Unless allow connect to ocsp.digicert.com, crl4.digicert.com, crl3.digicert.com currently stuck on 'This server can't be reached' window. https://github.com/wireapp/wire/issues/338 however i noticed app keep consume 8-10MB bandwidth per client for wire domains regularly only for an hour
There're ways to accomplish DNSSEC requirement.
Beta Was this translation helpful? Give feedback.
All reactions