Conversation

Notices

1. Dave Lane 🇳🇿 (lightweight@mastodon.nzoss.nz)'s status on Wednesday, 29-Mar-2023 08:10:09 JST Dave Lane 🇳🇿

   @swansinflight CatalystCloud.nz? Nope, they're still NZ-owned, far as I know.

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 29-Mar-2023 08:10:07 JST Adrian Cochrane

     in reply to

     @lightweight @swansinflight They do know route all traffic to them through Cloudflare, presumably because they actually faced DDoS attacks. But as long as you encrypt, treating the network between you & CatalystCloud as being untrusted (good practice anyways!), there is no jurisdictional risk.

     I investigated this for a client...

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 29-Mar-2023 09:25:37 JST Adrian Cochrane

     in reply to

     • Richard Hector

     @richardh @lightweight @swansinflight Catalyst is handling all the details, but Cloudflare does now support e2e encryption. Where they drop connections for known bot addresses.

   • Richard Hector (richardh@mastodon.nz)'s status on Wednesday, 29-Mar-2023 09:25:38 JST Richard Hector

     in reply to

     • Adrian Cochrane

     @alcinnz @lightweight @swansinflight
     Cloudflare is generally for web traffic, isn't it? And doesn't it achieve its goals by caching, meaning it has to terminate the tls connection, generally with its own certificates? How do you use it with encryption right through?