Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

radar.cloudflare.com

Post reply on HN
Print view View original

271–280 of 351 posts

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#271

Post by wl »

Mogzol wrote: post #119
JasonADrury wrote: post #78

Earlier quoted context omitted.

Jani Patokallio who runs gyrovague.com published a blog post attempting to dox the owner of archive.today. Jani justifies his doxing as follows "I found it curious that we know so little about this widely-used service, so I dug into it" [1] Archive.today on the other hand is a charitable archival project offered to the public for free. The operator of Archive.today risks significant legal liability, but still offers…

All your comments are painting archive.today as an innocent victim in all this, but in addition to the DDoS, they have been caught modifying archived pages as well as sending actual threats to Patokallio [1] which in my opinion seem far worse than the "doxxing". Just the fact alone that they modified archived pages has completely ruined their credibility, and over what? A blog post about them that (a) wasn't even an…

Which pages have they been caught modifying? And where's the evidence? I've seen this accusation multiple times but never with concrete details.

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#272

Post by Permit »

JasonADrury wrote: post #143
gyrovague-com wrote: post #110

Earlier quoted context omitted.

Jani here. What you describe as "doxxing" consisted of a) a whois lookup for archive.is and b) linking to a StackExchange post from 2020 called "Who owns archive.today" [1]. There is literally no new information about the site's owner in the post, all names have been dug up before and are clearly aliases, and the post states as much. [1] https://webapps.stackexchange.com/questions/145817/who-owns-...

I don't see how this description changes the fundamental nature of your actions. Even a half-assed attempt at doxing is still an attempt at doxing. It'd be much easier to accept that you're acting in good faith had you deleted the post when it became obvious that the target doesn't appreciate it. You could still do that, and it would very simply be the right thing to do.

You are attempting to perform a rhetorical sleight of hand here. You are well aware that linking to a Stack Exchange post and running WHOIS is not grounds for a DDoS as a measured response. In light of this fact, you attempt to portray it as “doxxing” to mislead people into thinking that someone’s identity or address was published against their will.

I encourage everyone to read the original article and make their own conclusion. Do not take this poster at their word.

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#273

Post by sillysaurusx »

1vuio0pswjnm7 wrote: post #212

Some time ago, probably at least a year, likely more, I read a blog post by someone working for Google in Europe who loved using Archive.today and out of curiosity tried to determine who was running it. In the end he gave up, offered to buy the operator a beer or something like that, but if I recall correctly he went to even greater lengths in his research than the blogger discussed in this thread I wish I could find…

https://gyrovague.com/2023/08/05/archive-today-on-the-trail-...

Sparked a controversial subthread elsewhere here. I don’t think this counts as doxxing, but some people apparently see it that way. It was an entertaining read though.

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#274

Post by zahlman »

stuffoverflow wrote: post #10

Archive.today's attack on https://gyrovague.com is still on-going btw. It started just over two months ago. Some IPs get through normally but for example finnish residential IPs get stuck on endless captchas. The JS snippet that starts spamming gyrovague appears after solving the first captcha.

To be clear, if I have JavaScript blocked for archive.today (which is my default with NoScript; and really there is no site functionality that really needs JS on the user's end), then I don't participate in the DDOS, right?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#275

Post by saaaaaam »

ranger_danger wrote: post #226
surgical_fire wrote: post #138

Earlier quoted context omitted.

Quad9. Many years ago I used Cloudflare, and more than once I had issues with them blocking websites I wanted to access. I absolutely despise that. I want my DNS to resolve domain names, nothing else. For blocking things I have Pi-Hole, which is under my control for that reason. I can blacklist or whitelist addresses to my needs, not to the whims of a corporation that wants to play gatekeeper to what I can browse.

Why give all your queries to a single company with an interest in tracking you and selling your data?

But don’t most ISPs do this? And if you use google’s DNS, for example, are they not doing this? Does cloudflare sell the data?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#276

Post by zahlman »

cuu508 wrote: post #177
croes wrote: post #176

Earlier quoted context omitted.

It‘s not a C&C/Botnet

It is C&C -- it instructs their site visitors to DOS a specific site.

By this logic, all malicious JavaScript (obvious example is cryptominers I guess, assuming no JS sandbox escape) is C&C, yeah? As it "instructs site visitors" to do something harmful locally?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#277

Post by viktoresku »

woopsn wrote: post #260
JasonADrury wrote: post #78

Earlier quoted context omitted.

Jani Patokallio who runs gyrovague.com published a blog post attempting to dox the owner of archive.today. Jani justifies his doxing as follows "I found it curious that we know so little about this widely-used service, so I dug into it" [1] Archive.today on the other hand is a charitable archival project offered to the public for free. The operator of Archive.today risks significant legal liability, but still offers…

As of now the site is in-fact a C&C/botnet. Cloudflare naturally fixates on such risks, not speech (generally). The basic purpose of 1.1.1.2 is to not wind up part of botnet.

Cloudflare strikes back for AT's blocking 1.1.1.1 for years. How did 1.1.1.2 managed to work when 1.1.1.1 did not?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#278

Post by echoangle »

wl wrote: post #271
Mogzol wrote: post #119

Earlier quoted context omitted.

All your comments are painting archive.today as an innocent victim in all this, but in addition to the DDoS, they have been caught modifying archived pages as well as sending actual threats to Patokallio [1] which in my opinion seem far worse than the "doxxing". Just the fact alone that they modified archived pages has completely ruined their credibility, and over what? A blog post about them that (a) wasn't even an…

Which pages have they been caught modifying? And where's the evidence? I've seen this accusation multiple times but never with concrete details.

https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment...

Under „Altering of archived pages“

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#279

Post by echoangle »

dgxyz wrote: post #104
JasonADrury wrote: post #78

Earlier quoted context omitted.

Jani Patokallio who runs gyrovague.com published a blog post attempting to dox the owner of archive.today. Jani justifies his doxing as follows "I found it curious that we know so little about this widely-used service, so I dug into it" [1] Archive.today on the other hand is a charitable archival project offered to the public for free. The operator of Archive.today risks significant legal liability, but still offers…

I'm wondering if Jani is possibly going to walk into the wrong party here and get burned. I did some public archival stuff about a decade ago and it was state sponsored and for the intelligence community. I'm not suggesting this is but it'll be very much of interest to competing intelligence services as it's an information control point. None of those are the sort of people you start pissing off by sticking your dick…

Why would stuff for the intelligence community be made public? Wouldn’t it make more sense for them to keep it private?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#280

Post by baobabKoodaa »

JasonADrury wrote: post #86
henearkr wrote: post #73

Earlier quoted context omitted.

I doubt it. You may have mixed it up with archive.org.

I suggest you double-check that. Archive.today/archive.is is the one which bypasses paywalls and makes unreadable content readable, not archive.org

Archive.is links have not worked for me for over a year. Infinite captcha loop.
Post reply on HN