Blaze (he/him)@lemmy.zip to Privacy@programming.dev · 5 days agoIntroducing QUIC Obfuscation for WireGuardmullvad.netexternal-linkmessage-square10fedilinkarrow-up146arrow-down10
arrow-up146arrow-down1external-linkIntroducing QUIC Obfuscation for WireGuardmullvad.netBlaze (he/him)@lemmy.zip to Privacy@programming.dev · 5 days agomessage-square10fedilink
minus-squaretenchiken@anarchist.nexuslinkfedilinkEnglisharrow-up3·3 days agoAll the examples in the spec itself are https.
minus-squarenomad@infosec.publinkfedilinkarrow-up2·2 days agoI guess that’s a magic bullet then… Just ensure you are using a certificate chain that’s not issued by a authority inside the country.
minus-squaretenchiken@anarchist.nexuslinkfedilinkEnglisharrow-up2·2 days agoAlong that line, I’d be self signing and requiring a specific client cert to allow connection. But yes absolutely good point
All the examples in the spec itself are https.
I guess that’s a magic bullet then… Just ensure you are using a certificate chain that’s not issued by a authority inside the country.
Along that line, I’d be self signing and requiring a specific client cert to allow connection.
But yes absolutely good point