News for hackers. Stuff that matters.
Re:Malicious attack on Wikipedia – what we know and what we’... by judge2020 on Saturday September 07, 2019 @10:04AM (#20903812)
Someone claimed the attack on twitter with some details (DDoS) - and proved it later by stopping the attack for x minutes then restarting it at a specific time. https://twitter.com/fs0c131y/status/1170093562878472194?s=20 - the attacker also went on to DDoS the twitch ingest servers (not twitch.tv itself) knocking some big streamers offline.
Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Saturday September 07, 2019 @01:14PM (#20905113)
It looks like a volumetric attack from this tweet. Wikipedia needs to use Verisign BGP mitigation. They create GRE tunnels to your routers and are capable of handling 2Tbps. During an attack, you make a BGP announcement and the traffic goes via Verisign scrubbing/tunnels. No application changes are required, no Matthew Prince selectively and benevolently enforcing CF neutrality. It's used by large banks.
Re:Malicious attack on Wikipedia – what we know and what we’... by lkoolma on Saturday September 07, 2019 @02:05PM (#20905461)
After working with a few large corporations and their DDoS protection solutions, I did not have a good experience with Verisign, and they were not able to handle attacks or get things working. However, I have great experiences with Akamai and Cloudflare. I trust the people at Wikimedia will choose wisely. I would I have learned that Verisign has one of the worst BGP mitigation/scraping solutions out there. There are a few alternatives that have more experience and provide much better uptime, include solutions from Cloudflare and Akamai.
Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Saturday September 07, 2019 @02:13PM (#20905522)
Any serious mitigation solution must be BGP based, not proxy. Besides its technical merits and convenience, it also minimizes the risk of a benevolent controller (e.g. Matthew Prince of Cloudflare) ruining your company, because it becomes your upstream provider only during the attacks. Otherwise the GRE tunnels are not in use. The IP addresses are still yours always.

We used Verisign for mitigation of a 44Gbps volumetric attack and it worked very well. We also evaluated Neustar, but Verisign's infrastructure seemed to be more robust.

Re:Malicious attack on Wikipedia – what we know and what we’... by aftbit on Saturday September 07, 2019 @04:58PM (#20906471)
That's your requirement, but it might not be Wikipedia's requirement. Ownership of IPs is really a technical detail invisible to most people; ownership of eyeballs by way of the domain name and top Google result is probably more important. Cloudflare doesn't impact that ownership other than being able to temporarily take you offline if they choose to terminate your site.

Still, large proxy-based CDNs do have the ability to completely bypass all the same-origin protections in the browser. Even if they are angels and don't abuse this trust for identity theft and surveillance, it makes them a juicy target for bad actors, state sponsored and otherwise.

Re:Malicious attack on Wikipedia – what we know and what we’... by snazz on Saturday September 07, 2019 @03:38PM (#20906001)
A proxy is a perfectly acceptable “serious” solution for this type of problem, as well as nearly all of the rest. Wikipedia is not the kind of website that would warrant being removed from Cloudflare. What’s wrong with having an upstream provider for caching close to the user and other features when you’re not under attack?
Re:Malicious attack on Wikipedia – what we know and what we’... by SahAssar on Saturday September 07, 2019 @06:22PM (#20906999)
> What’s wrong with having an upstream provider for caching close to the user and other features when you’re not under attack?

The problem is that you are basically mitm:ed all the time.

Re:Malicious attack on Wikipedia – what we know and what we’... by acdha on Saturday September 07, 2019 @08:44PM (#20907757)
That’s not what MITM means. I get that you don’t like Cloudflare but voluntary use of a CDN isn’t a MITM any more than, say, Amazon is a MITM because you host on EC2.
Re:Malicious attack on Wikipedia – what we know and what we’... by SahAssar on Sunday September 08, 2019 @08:55AM (#20910278)
Cloudflare is in between the client and the server, decrypting, rewriting and (if set up right) re-encrypting the request/response. It masquerades as the server by presenting a proper certificate for the domain even though it is not the entity that is actually controlling the domain.

That to me sounds very much like MITM, although it is not a MITM attack since the entity controlling the domain opted into it, so basically it is voluntary MITM.

Using a VPS like EC2 is a different story since the decryption happens within the layer that you control. Of course you need to make sure that you choose a vendor for that layer that you trust, but on EC2 the traffic that amazon sees is encrypted with keys they don't have and decrypted with keys stored on a layer that I control. Amazon could read out the memory of my EC2 to get the keys but their business depends on not doing so, so in this case either I have a vendor that always will decrypt and read traffic (Cloudflare), or a vendor whose business depends on hypothetically being able to but not doing it. There is a clear difference to me.

That is the same for most CDN's (including CloudFront and all the other major offerings), so I'm not trying to single out Cloudflare.

Re:Malicious attack on Wikipedia – what we know and what we’... by acdha on Sunday September 08, 2019 @10:28AM (#20910737)
If you don’t trust Cloudflare, don’t use them but there’s no meaningful security distinction between what they do and what AWS does: in both cases you have a vendor with the capability of violating your security and a promise that they won’t abuse that access.

This is why having a threat model is so important: it keeps you from wasting effort on things which sound like security but aren’t actually changing anything meaningful.

Re:Malicious attack on Wikipedia – what we know and what we’... by SahAssar on Sunday September 08, 2019 @02:02PM (#20912169)
There is a security distinction, and this has been shown by for example cloudbleed. Every step that has access to plaintext data is a potential attack vector and might be logging/leaking information.

There has also been times where cloudflare (when setup improperly as I mentioned in the previous comment) has misrepresented the security of a connection, as shown by https://www.theregister.co.uk/2016/07/14/cloudflare_investig...

Re:Malicious attack on Wikipedia – what we know and what we’... by cramforce on Sunday September 08, 2019 @10:06AM (#20910616)
The MITM can be avoided by using Signed Exchanges. https://developers.google.com/web/updates/2018/11/signed-exc...
Re:Malicious attack on Wikipedia – what we know and what we’... by SahAssar on Sunday September 08, 2019 @02:04PM (#20912183)
That only works for static content, right?
Re:Malicious attack on Wikipedia – what we know and what we’... by cramforce on Saturday September 14, 2019 @11:29PM (#20975401)
No, they can be created on the fly. That basically makes it a TLS signing Oracle.
Re:Malicious attack on Wikipedia – what we know and what we’... by snazz on Sunday September 08, 2019 @09:33AM (#20910474)
Cloudflare’s business also depends on not messing with your traffic, right? It would certainly be easier for them to get your users’ content than for Amazon to do the same, but I think you still have to accept that risk with either. “Hypothetically being able to but not doing it” isn’t a whole lot of confidence if I were hosting some kind of shady website.
Re:Malicious attack on Wikipedia – what we know and what we’... by SahAssar on Sunday September 08, 2019 @02:11PM (#20912235)
Sure, but since Cloudflare’s business is actively "messing" with all your traffic, all the time it's a smaller technical step to do it some more, and can also lead to accidents like cloudbleed. Every step that has access to unencrypted data is a potential attack vector or might be logging/leaking data.
Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Saturday September 07, 2019 @09:40PM (#20908010)
You upload your private SSL key to Cloudflare for example. And I was talking about hosting on your own hardware/colos like most large sites do (7x cheaper than AWS list prices on avg)
Re:Malicious attack on Wikipedia – what we know and what we’... by acdha on Saturday September 07, 2019 @09:42PM (#20908025)
Please specify in detail how you believe that’s an MITM using the standard industry definition. In particular, consider whether “attack” and “voluntary business agreement” are synonyms.
Re:Malicious attack on Wikipedia – what we know and what we’... by lazyguy2 on Sunday September 08, 2019 @01:33AM (#20908785)
MITM is not a uncommon term to use when you do things like install corporate SSL certs on laptops so you can monitor people's activities.
Re:Malicious attack on Wikipedia – what we know and what we’... by detaro on Sunday September 08, 2019 @05:57AM (#20909544)
Breaking open encryption to monitor activity between users and other sites is a completely different thing than having a provider handle hosting for your site.
Re:Malicious attack on Wikipedia – what we know and what we’... by judge2020 on Saturday September 07, 2019 @08:57PM (#20907815)
A better comparison would be Cloudfront and Application Load Balancers since you can expose your own ec2 server or load balancer and be e2e encrypted (unless AWS wanted to run commands on your instance, which they could do, but that's a different threat vector entirely).
Re:Malicious attack on Wikipedia – what we know and what we’... by acdha on Saturday September 07, 2019 @09:40PM (#20908018)
That was the model I had in mind but it’s not really a meaningful distinction since the host could almost certainly compromise those servers as well. In any case, you’re trusting a third party rather than having their involvement maliciously imposed.
Re:Malicious attack on Wikipedia – what we know and what we’... by awirth on Saturday September 07, 2019 @08:19PM (#20907642)
Akamai has a BGP based DDoS mitigation service via their prolexic acquisition.
[dead]
Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Saturday September 07, 2019 @05:52PM (#20906790)
The originalcontent was posted on IG. 8ch took the reposts down when it became known that it was connected to the real shooting. Watch the video with the 8ch founder explaining (unless YouTube took it down too). Matt was preparing for the IPO.
Re:Malicious attack on Wikipedia – what we know and what we’... by fennecfoxen on Saturday September 07, 2019 @11:13PM (#20908382)
You appear to be extremely mad that anyone questions the power of political pressure and an angry mob.

Look, you can feel however you like about whether the high-profile takedowns are right or wrong, whether the CEO's promises after the Daily Stormer are hypocritical — but let's be clear-eyed about placing a site in a position where one outside person can do it real harm. The question you should look at is whether the risk is actually acceptable for your organization.

Re:Malicious attack on Wikipedia – what we know and what we’... by aceofspades19 on Saturday September 07, 2019 @04:59PM (#20906473)
How did 8chan "encourage" large gun massacres exactly? By allowing users to post content?
Re:Malicious attack on Wikipedia – what we know and what we’... by Operyl on Saturday September 07, 2019 @05:22PM (#20906600)
By not moderating content largely, it was no secret what the site was letting go.
Re:Malicious attack on Wikipedia – what we know and what we’... by o-__-o on Saturday September 07, 2019 @08:49PM (#20907781)
By your statement then reddit was complicit with the Russian trolls during election season because the bitcoin trolls who evolved into trump trolls were not punished in the slightest (I have a list of 300+ usernames that are still active today)
Re:Malicious attack on Wikipedia – what we know and what we’... by Operyl on Saturday September 07, 2019 @10:25PM (#20908198)
Reddit is actively moderated by both paid Admins (site wide rules) and volunteer Mods (per subreddit rules). So no, I disagree.
Re:Malicious attack on Wikipedia – what we know and what we’... by lucifirius on Sunday September 08, 2019 @09:09AM (#20910354)
the chans are also actively moderated, and the chans remove CP and did remove other content after events happen
Re:Malicious attack on Wikipedia – what we know and what we’... by judge2020 on Saturday September 07, 2019 @09:04PM (#20907847)
The point is that Reddit tries to moderate, which is good enough for their providers (AWS/Fastly).

The 8ch takedown wasn't actually due to issues with moderation, since (at least based on the owner's video) 8ch removed the post, actively responds to real law enforcement requests, and the original post was actually posted to IG. The issue was that CF was getting enough bad press, and more importantly enough calls/concerns from real Enterprise clients (this is speculation on my part), to take down the website.

Re:Malicious attack on Wikipedia – what we know and what we’... by kevingadd on Saturday September 07, 2019 @05:13PM (#20906551)
Alternately: The fact that Prince was super okay with hosting those websites until the moment it made him look bad
Re:Malicious attack on Wikipedia – what we know and what we’... by judge2020 on Saturday September 07, 2019 @08:59PM (#20907826)
That's a valid stance but they didn't host the website; they only provided DDOS protection for the actual host (which proceeded to drop 8ch once CF stopped providing the protection).
Re:Malicious attack on Wikipedia – what we know and what we’... by nullc on Saturday September 07, 2019 @03:29PM (#20905949)
> It looks like a volumetric attack from this tweet. Wikipedia needs to use Verisign BGP mitigation. They create GRE tunnels to your routers and are capable of handling 2Tbps.

Great way for a state actor to intercept your traffic. little bit of volumetric dos and the target themselves responds by tunning through your partner(s).

Re:Malicious attack on Wikipedia – what we know and what we’... by gruez on Saturday September 07, 2019 @01:32PM (#20905238)
>no Matthew Prince selectively and benevolently enforcing CF neutrality.

What's the logic behind this? It's still a single point of failure and relying on a corporation. If the daily stormer or 8chan tried to use them, they would probably kicked off as well.

Re:Malicious attack on Wikipedia – what we know and what we’... by nine_k on Saturday September 07, 2019 @01:44PM (#20905317)
If you are not a political undesirable, it does help, though. I think Wikipedia is fine in this regard, not something to shun of for a big corp.
Re:Malicious attack on Wikipedia – what we know and what we’... by sannee on Saturday September 07, 2019 @02:57PM (#20905780)
Wikipedia is blocked in China. It's politically undesirable for 1/8 of the human population...
Re:Malicious attack on Wikipedia – what we know and what we’... by NotSammyHagar on Saturday September 07, 2019 @03:39PM (#20906011)
I think undesirable here describes something like white nationalists. They have a problem getting web hosting.
Re:Malicious attack on Wikipedia – what we know and what we’... by sannee on Saturday September 07, 2019 @05:37PM (#20906700)
CloudFlare has strategic business partnership with Baidu [1]. They are very likely to cooperate with the chinese government to implement the great chinese firewall.

Additionally, helping to block Wikipedia because China says so is much easier to excuse than blocking 4chan - they would just be complying with local regulations after all.

[1] https://www.cloudflare.com/press-releases/2015/cloudflare-an...

Re:Malicious attack on Wikipedia – what we know and what we’... by allard on Saturday September 07, 2019 @04:43PM (#20906401)
Because all of them don't want it?
Re:Malicious attack on Wikipedia – what we know and what we’... by nine_k on Saturday September 07, 2019 @03:02PM (#20905804)
Unlike a DDoS attack, this is not a technological problem.
Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Saturday September 07, 2019 @01:45PM (#20905329)
There's always something "undesirable" for someone in a big crowdsourced website.
Re:Malicious attack on Wikipedia – what we know and what we’... by rocqua on Saturday September 07, 2019 @04:48PM (#20906421)
The cloudfare 8chan action was based on a direct link with multiple actual mass-shootings. Moreover, as they took the decision they went to great pains to explain this was an exceptional case.

Going from that to 'undesired political speech will be censored' requires more of a slippery cliff than a slippery slope.

Re:Malicious attack on Wikipedia – what we know and what we’... by gruez on Saturday September 07, 2019 @07:20PM (#20907347)
>The cloudfare 8chan action was based on a direct link with multiple actual mass-shootings

What is this "direct link" you speak of? Did the shooters plan/recruit/organize their attacks on 8chan?

Re:Malicious attack on Wikipedia – what we know and what we’... by speedplane on Sunday September 08, 2019 @05:14AM (#20909429)
> What is this "direct link" you speak of? Did the shooters plan/recruit/organize their attacks on 8chan?

Legally, a "direct link" is irrelevant, you can rarely find a "direct link" between two of anything. What matters legally is whether 8chan was a "proximate cause" in creating the mass shootings. Whether one thing is the "proximate cause" of another is often pretty difficult to discern.

However, as a helpful guide towards determining proximate cause, lawyers ask whether one thing was the "but for" cause of another, i.e., would the mass shootings occur "but for" 8Chan? Put another way, if 8Chan did not exist, would these shootings occur?

Unfortunately, we do not have an alternative reality to play out events without 8Chan, so we cannot know for certain, but we can use evidence (e.g., 8Chan chats, how the shooter interacted with 8Chan and others on the service, etc) to try to simulate that alternative reality. All of this analysis also needs to consider related issues like freedom of speech on public forums and any commercial interests.

I'm not saying 8Chan is guilty or innocent, just that the existence (or lack thereof) of a "direct link" is pretty meaningless.

Re:Malicious attack on Wikipedia – what we know and what we’... by nl on Sunday September 08, 2019 @04:40AM (#20909302)
There are multiple instances of them announcing them and implying they are follow-ups of previous discussions on 8chan.

These include the Christchurch shootings, the Poway synagogue shooting and the El Paso Walmart shootin.

The Christchurch shooter shared his Facebook stream to 8chan before the shooting started, and it was spread from there.

The Poway shooter blamed/thanked 8chan for his views.

Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Sunday September 08, 2019 @11:09AM (#20910986)
So FB's internet peers should depeer Facebook then in their routers, since the original material (the stream) was on FB? Or you prefer your justice selective?
Re:Malicious attack on Wikipedia – what we know and what we’... by nl on Sunday September 08, 2019 @10:49PM (#20914829)
I'm sure you already realize this, but to make it clear: FB has enormous utility for billions of people outside that and that is worth defending.

You are expanding a lot of effort defending 8chan here. Perhaps consider that it might not be worth defending.

Re:Malicious attack on Wikipedia – what we know and what we’... by dangxiaopin on Monday September 09, 2019 @01:24AM (#20915400)
8ch had a lot of very interesting and non-violent stuff. Have you been reading it regularly? I did.

I lived in a socialist country and you did not. Perhaps consider that you might not know where these current trends are pointing to.

[dead]
Re:Malicious attack on Wikipedia – what we know and what we’... by marvin-83 on Monday September 09, 2019 @09:36AM (#20917994)
you're not really engaging with his point. Effectively banning 8chan by removing network protection does not just restrict extremists; it restricts anyone who used that forum.

Ultimately, such matters should be prosecuted by courts. It is inappropriate for organisations like cloudflare to leverage their position within essential network infrastructure to start editorialising what passes through their network.

Re:Malicious attack on Wikipedia – what we know and what we’... by nl on Monday September 09, 2019 @09:19PM (#20924267)
It is inappropriate for organisations like cloudflare to leverage their position within essential network infrastructure to start editorialising what passes through their network.

No, I think it's entirely appropriate.

"Don't troll" and methods for dealing with trolls has been a thing all sites have done since the internet was invented. I don't see any difference here at all.

Re:Malicious attack on Wikipedia – what we know and what we’... by marvin-83 on Tuesday September 10, 2019 @11:07AM (#20929018)
the difference is their position in the stack.

Cloudflare blocking people that abuse the network is legitimate (e.g. spam, denial-of-service), just like it is legitimate for forum admins to block people that abuse the forum (trolling, explicit posts).

But cloudflare, or any other network infrastructure provider, shouldn't be determining permissible content for websites because they are not hosts/administrators for that content.

It is like a postal service reading your letters and then saying "we don't like what is being said, so you can't send letters anymore." They can and should stop people sending dangerous materials by post, but they should not be determining permissible content of letters.

Re:Malicious attack on Wikipedia – what we know and what we’... by nl on Tuesday September 10, 2019 @08:11PM (#20935272)
See, I think 8-chan itself is a troll, and it is entirely reasonable to deal with it by refusing to provide service.

It is like a postal service reading your letters and then saying "we don't like what is being said, so you can't send letters anymore." They can and should stop people sending dangerous materials by post, but they should not be determining permissible content of letters.

No it's not. It's like FedEx declining to deliver for a company which continues to cause it problems, or refusing to service Amazon[1]. Or like Visa refusing to service businesses which have lots of charge-backs.

[1] https://www.nytimes.com/2019/06/07/business/fedex-amazon-exp...

Re:Malicious attack on Wikipedia – what we know and what we’... by ryacko on Wednesday September 11, 2019 @04:15AM (#20937677)
Actually, it is illegal to mail obscene materials or crime inciting matter through the postal service.

https://www.law.cornell.edu/uscode/text/18/1461

Re:Malicious attack on Wikipedia – what we know and what we’... by marvin-83 on Wednesday September 11, 2019 @11:31AM (#20941206)
yes, but these are investigated and prosecuted by police, public prosecution services, and courts; not by couriers discontinuing their services.
Re:Malicious attack on Wikipedia – what we know and what we’... by marvin-83 on Wednesday September 11, 2019 @11:52AM (#20941478)
if 8chan was cut off because they were subject to extensive network attacks and cloudflare did not see any profit or value in serving them then I am ok with that. I just don't think that's the reason.

I expect that a different site with the same contract and payment terms, subject to the same attacks would have continued to be protected. maybe I'm wrong but it looked like a political decision, not a business decision.

Re:Malicious attack on Wikipedia – what we know and what we’... by rocqua on Sunday September 08, 2019 @05:01AM (#20909371)
The direct link is that they announced these attacks there.

Beyond that, given the announcement there, it stands to reason they were convinced to do it there.

Re:Malicious attack on Wikipedia – what we know and what we’... by wwright on Saturday September 07, 2019 @02:50PM (#20905733)
I think it’s somewhat misleading to refer to those who support genocide and child abuse as simply “political undesirables.”
Re:Malicious attack on Wikipedia – what we know and what we’... by bitwize on Saturday September 07, 2019 @03:27PM (#20905938)
It's not just supporting. Taking a neutral stance on censoring these things, or not being adequately proactive on hate speech, is now seen as condoning. You either censor your user base, or upstream will censor you. Gone are the days of "The net interprets censorship as damage and routes around it." The new policy is "The net interprets wrongthink as noise and filters it out."
Re:Malicious attack on Wikipedia – what we know and what we’... by wwright on Saturday September 07, 2019 @08:01PM (#20907553)
It’s not censorship: they are not suppressing information, they just aren’t allowing their resources to be used to spread it.

It would be “censorship” if they actively antagonized any attempt to spread the information, such as by lawsuit or DMCA notice. They are just refusing to participate.

And given that the “information” is definitively known to be child pornography and violent white supremacy propaganda presented as news, I would personally say refusing to participate is the only responsible action.

Re:Malicious attack on Wikipedia – what we know and what we’... by claudiawerner on Sunday September 08, 2019 @04:35PM (#20913252)
> Gone are the days of "The net interprets censorship as damage and routes around it."

But it's clear that it matters just what's being censored. Surely you wouldn't say the same trite clever-sounding hackerspeak if we're talking about censorship of threats, assault and child pornography, would you?

Re:Malicious attack on Wikipedia – what we know and what we’... by nine_k on Saturday September 07, 2019 @03:00PM (#20905793)
They are beyond a certain line; some very-very far past it, some just crossed it. It makes them unsupportable by any corporation that aims to look decent.
Re:Malicious attack on Wikipedia – what we know and what we’... by the8472 on Saturday September 07, 2019 @03:49PM (#20906070)
Genocide has been and still is a political tool. It is extreme, but ultimately something that people consider and carry out as part of political processes, not a special category of its own. And realpolitik is to continue dealing with countries that practice genocide. Consider Burma or China.

Cloudflare simply has the luxury of choosing which politically disagreeable parties they do not want to associate with because they are insignificant customers.

Pretending that this is not due to differences in politics and moral judgment is semantic smoke and mirrors.

Anyway, the point is that they are not a neutral carrier/providers. Unlike banks or telecoms which are required by regulation to accept any legal business. CF styles itself as neutral infrastructure, until they decide they are not.

The risk of getting deplatformed due to someone's moral judgment is quite real, even for an entity such as Wikipedia. For example they were blocked in the UK because the Virgin Killer album cover landed it on a block list used by major ISP.

Re:Malicious attack on Wikipedia – what we know and what we’... by wwright on Saturday September 07, 2019 @08:04PM (#20907570)
I didn’t say it wasn’t political, but it’s not just undesirable for immediate political reasons — it’s undesirable for nearly universally-agreed moral and ethical reasons. So implying it’s only inconvenient for politics is, in my opinion, misleading.
Re:Malicious attack on Wikipedia – what we know and what we’... by the8472 on Sunday September 08, 2019 @06:49AM (#20909716)
The political tends to encompass or at least subsume the moral and ethical aspects, as I tried to allude to with the realpolitik aspect.

But again, this is just a tangent. The core argument is that it is best not to rely on providers that have the freedom to make political/moral decisions who they deal with because that freedom makes them susceptible to moral denial of service attacks. You are one moral outrage away from being deplatformed.

Re:Malicious attack on Wikipedia – what we know and what we’... by wwright on Sunday September 08, 2019 @08:47AM (#20910234)
I can see that mentality, but what I’m saying is that, personally, if I become a Nazi, I think I should be deplatformed.
Re:Malicious attack on Wikipedia – what we know and what we’... by whenchamenia on Sunday September 08, 2019 @10:37AM (#20910816)
Then who decides what is a Nazi? Deplatforming someone for their speech makes them one in my book. How far down do we go?
Re:Malicious attack on Wikipedia – what we know and what we’... by judge2020 on Saturday September 07, 2019 @02:38PM (#20905662)
This recent CF product announcement might be the same thing (not sure, sounds similar): https://blog.cloudflare.com/magic-transit/
Re:Malicious attack on Wikipedia – what we know and what we’... by jopsen on Sunday September 08, 2019 @05:51AM (#20909530)
> no Matthew Prince selectively and benevolently enforcing CF neutrality.

Is this a slippery slope argument.

Because there is a world in difference from discontinuing a few extremists customers, to discontinuing service for something akin to Wikipedia.

I'm not sure every slight compromise of principals is a slippery slope. It seems to me that CF generally aims at being neutral.

Re:Malicious attack on Wikipedia – what we know and what we’... by palerdot on Sunday September 08, 2019 @10:25AM (#20910726)
The argument made here is there is a chance (however minute) that the same can happen to something like Wikipedia because of some misplaced sense of morality, like say - we don't agree with wikipedia edits and editing process which we see if offending certain sections of X population. It does not matter how right their reason is. The fact that providers like cloud flare are in such position to take a moral high stance is not right ...
Re:Malicious attack on Wikipedia – what we know and what we’... by jopsen on Tuesday September 10, 2019 @12:38AM (#20925074)
I don't disagree, but has it ever been any different?
Re:Malicious attack on Wikipedia – what we know and what we’... by joatmon-snoo on Sunday September 08, 2019 @03:24AM (#20909091)
Anyone that suggests that there is One True Solution TM is either biased or ignorant.

You also don't get to claim it supports 2Tbps if you've only weathered 44Gbps.

Re:Malicious attack on Wikipedia – what we know and what we’... by lima on Saturday September 07, 2019 @06:53PM (#20907200)
There's plenty of specialized providers which provide this service, Verisign is one of many.

The issue with on-demand BGP mitigation is that an attacker can do short attacks on and off over a long period of time. Each time the mitigation kicks in, BGP propagation takes at least ~1 minute and will cause some downtime. Proper protection is always-on without requiring redirection.

Re:Malicious attack on Wikipedia – what we know and what we’... by amaccuish on Saturday September 07, 2019 @01:32PM (#20905241)
What's with the username? Are you trying to equate dang to Deng Xiaopin?
Re:Malicious attack on Wikipedia – what we know and what we’... by kyrra on Saturday September 07, 2019 @09:34PM (#20907986)
The attacker also attack Blizzard's game servers. Is actively taking down WoW classic and Overwatch.

https://www.reddit.com/r/classicwow/comments/d10x4f/servers_...

The attacker was posting updates to Twitter, but their account has since been suspended.

Re:Malicious attack on Wikipedia – what we know and what we’... by jrochkind1 on Saturday September 07, 2019 @11:06AM (#20904178)
Did they say anywhere what their motive was?
Re:Malicious attack on Wikipedia – what we know and what we’... by diveanon on Saturday September 07, 2019 @12:38PM (#20904848)
They are advertising their services.
Re:Malicious attack on Wikipedia – what we know and what we’... by impalallama on Saturday September 07, 2019 @11:13AM (#20904240)
Power tripping most likely.
Re:Malicious attack on Wikipedia – what we know and what we’... by comboy on Saturday September 07, 2019 @12:26PM (#20904762)
It's not cheap, advertising their services seem more likely to me.
Re:Malicious attack on Wikipedia – what we know and what we’... by bollockitis on Saturday September 07, 2019 @11:15AM (#20904248)
Do these kinds of attacks usually have a motive?
Re:Malicious attack on Wikipedia – what we know and what we’... by Iv on Saturday September 07, 2019 @11:39AM (#20904428)
I am pretty certain that when China used the Great Firewall to attack github, this was a test of their capabilities.
Re:Malicious attack on Wikipedia – what we know and what we’... by eloff on Saturday September 07, 2019 @01:30PM (#20905225)
Source?
Re:Malicious attack on Wikipedia – what we know and what we’... by yorwba on Saturday September 07, 2019 @03:28PM (#20905944)
Re:Malicious attack on Wikipedia – what we know and what we’... by eloff on Saturday September 07, 2019 @03:33PM (#20905971)
What a world we live in... Government sponsored DDoS.
Re:Malicious attack on Wikipedia – what we know and what we’... by ngcc_hk on Saturday September 07, 2019 @07:06PM (#20907268)
What a world live in if you are the 1.x million in som northern part of china. The 1.x billion if live inside Great Wall. The 7m if you are in Hong Kong or 2x million if you are in Taiwan.

You live in a world where a totalitarian communist state is welcomed and controlled a significant portion of the world economy. Even speak in internet summit.

Welcome to the brave new internet and international world of china.

Re:Malicious attack on Wikipedia – what we know and what we’... by ethelward on Saturday September 07, 2019 @11:24AM (#20904327)
They can be used by blackhats selling e.g. DDoD-netbots to prove the “quality of the merchandise”.
Re:Malicious attack on Wikipedia – what we know and what we’... by aldoushuxley001 on Saturday September 07, 2019 @11:38AM (#20904422)
I definitely get the feeling that’s what they’re going for. They mentioned they’re just testing out a new botnet made from IoT devices.
Re:Malicious attack on Wikipedia – what we know and what we’... by mirimir on Saturday September 07, 2019 @08:40PM (#20907738)
Ah, Mirai Mark N. So what, light bulbs? Cameras?
Re:Malicious attack on Wikipedia – what we know and what we’... by mpfundstein on Saturday September 07, 2019 @01:01PM (#20905014)
Where did you read this? I am curious...
Re:Malicious attack on Wikipedia – what we know and what we’... by aldoushuxley001 on Saturday September 07, 2019 @01:24PM (#20905187)
From the attacker's twitter account, just read through his/her twitter replies (though it sounds like it's actually a group of them).
Re:Malicious attack on Wikipedia – what we know and what we’... by Havoc on Saturday September 07, 2019 @11:48AM (#20904505)
And so the IoT wars begin...
Re:Malicious attack on Wikipedia – what we know and what we’... by canjobear on Saturday September 07, 2019 @11:50AM (#20904520)
Who are they?
Re:Malicious attack on Wikipedia – what we know and what we’... by mises on Saturday September 07, 2019 @12:32PM (#20904806)
Some clown named ukdrillas. That's about all any one knows.