Technology

37712 readers

182 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

Los@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

138

Blocked by Cloudflare (jrhawley.ca)

submitted 1 year ago by trashhalo@beehaw.org to c/technology@beehaw.org

29 comments fedilink hide all child comments

The author was blocked from accessing a work website due to issues with Cloudflare's browser integrity checks. Despite having credentials to prove his identity, an attempt to bypass the checks by disabling fingerprinting in Firefox resulted in Cloudflare blocking all access. He could still access the site on Chrome, showing the block was based on his browser configuration. This left the author unable to complete important work tasks and questioning how much control individuals really have over authentication in an increasingly centralized web ecosystem dependent on remote attestation. It highlights the need for transparency and user agency in how identity verification is implemented online.

you are viewing a single comment's thread
view the rest of the comments

[–] upstream@beehaw.org 1 points 1 year ago (1 children)

Someone I know who works in payments told me they had to go to CF because of the insane amount of DDoS attacks they were facing.

While having three ISPs and mitigating a boatload of DDoS on their own infrastructure they were simply unable to cope with the persistence.

They first tried another provider, but they handled less DDoS than their own internal systems.

Cloudflare wasn’t even sure they wanted them as a customer.

Some of the biggest attacks mitigated by Cloudflare last year (they wrote about it) was this client.

[–] tiwenty@jlai.lu 1 points 1 year ago (1 children)

I guess we can say we're not in the selfhosted circles anymore haha

[–] upstream@beehaw.org 1 points 1 year ago (1 children)

Depends on what you mean by self-hosted. Because basically they are. No cloud providers meet their security requirements (required for their level of PCI certification).

[–] tiwenty@jlai.lu 1 points 1 year ago

Fair enough, I may have confused selfhosted with homelabs in my answers.