Cloudflare is no better, maybe worse. They forward your complaint & PI on to the offending site's registered owner and to whichever (gray or black hat) host it's served from. In my experience, there is nothing you can do to convince Cloudflare to do anything other than be a middleman for the complaint, yet they offer a layer of protection for the nefarious activities.
Even when I've been able to track down hosts, registrars, etc for scraped duplicates of sites, and report to all and Google, Microsoft Safety Scanner, etc -- nobody acts (or certainly not in any reasonable enough time to be useful).
In one case the scammer was using our own logo served directly from a source we could replace with Cloudflare rewrites. So the hijacked logo became "THIS IS A SCAM SITE" while we replaced the one on production.
Are you getting takedown requests from people who don’t understand how DNS works, or… are they actually suggesting that your particular DNS server filter particular results?
> Are you getting takedown requests from people who don’t understand how DNS works, or… are they actually suggesting that your particular DNS server filter particular results?
They're asking me to block servers (filter particular results). Here's a takedown request I received yesterday from PhishLabs:
During an investigation of fraud, we discovered a domain(s) registered for the sole intent of malicious activity. Please address this issue as per your terms of service.
> We take abuse reports very seriously. To report a site, email the offending URL to [email protected]. We respond to all abuse reports within 24 hours
> Cloudflare is no better, maybe worse. They forward your complaint & PI on to the offending site's registered owner and to whichever (gray or black hat) host it's served from.
This is literally false. They are one of the few hosts I have dealt with that actually does NOT do this. Their abuse reporting form even has check boxes that are optional to forward it to the underlying host and the owner. If you leave them unchecked they don't forward anything.
I don't know where you got your information from but it's quite literally the opposite of reality.
Now, whether or not they actually act on it depends on whether they are proxying the site or merely providing authoritative DNS. If they are just providing DNS they will continue to provide it and deny your report and I think that's stupid and frustrating. If they are proxying it they will put up a block page in front of it which is meh.
A large company's report system is designed to distract you from complaint paths that work and are expensive for the company to deal with (lawsuits) and make you complain to /dev/null instead.
Similar results for my workflow. And the Round art comes out significantly less round without prompt changes (more input tokens)
Setting (1024x1024) Tokens Cost/image Time
2.5 medium 439 $0.014 12.0 s
2.6 low 824 $0.025 6.7 s
2.6 medium 1,449 $0.044 7.9 s
2.6 high 1,758 $0.053 8.9 s
I have to believe that if hackers hit the treasure trove of Lastpass customer passwords, Instagram is not going to be their first target. We'd be seeing financial fraud first and foremost, likely sparingly at first, to not alert everyone to the fact that all of our passwords are compromised.
Your probably right, but I'd assume financial attacks would be highly targeted after verifying they have the proper passwords via using places like FB that will just ignore you endlessly if your account is hacked.
> We have determined that an unauthorized party, using information obtained in the August 2022 incident, was able to gain access to certain elements of our customers’ information. Our customers’ passwords remain safely encrypted due to LastPass’s Zero Knowledge architecture.
Sure sounds like they found passwords or keys in the development environment breach back in August, and nobody bothered to change those after knowing they were hacked.
I'm not sure how they expect to save users' credit card details in a way that can be transferred to the airlines. Can't store the CVV code at all, and everything else is supposed to be encrypted.
They can perform a initial auth against the device with the CVV for zero dollars (depending on the interchange network), then from then on perform recurring charges without the CVV at a higher interchange fee. That shouldn't be a problem since airline tickets are higher margin, low volume, purchases.
It mostly comes down to Kayak's business agreements with Visa/Mastercard etc and the airlines involved.
Edit: additionally the article doesn't say it's built yet, so they probably have several road blocks to hit yet. On top of that, they could always ask for CVV when actually making the purchase. Not like you wouldn't have your wallet on you if you have your iPhone
Oh, so you think that Kayak will actually be charging me for the ticket -- that would be easy. I got the impression that Kayak would be storing my credit card details and automatically fill out the appropriate airline's website forms in the background... which would require storing all of my credit card details with reversible encryption.
Also, according to my processor there is no interchange fee difference for using CVV or not. There is a financial incentive for address verification, but not CVV. Maybe this varies by processor.
reply