Live data from Hacker News

Ban me at the IP level if you don't like me

boston.conman.org

221–230 of 516 posts

Re: Ban me at the IP level if you don't like me

#221
post #141

Earlier quoted context omitted.

Yes and it makes reading your logs needlessly harder. Sometimes I find an odd password being probed, search for it on the web and find an interesting story, that a new backdoor was discovered in a commercial appliance. In that regard reading my logs led me sometimes to interesting articles about cyber security. Also log flooding may result in your journaling service truncating the log and you miss something important…

> Sometimes I find an odd password being probed, search for it on the web and find an interesting story [...]. Yeah, this is beyond irresponsible. You know the moment you're pwned, __you__ become the new interesting story? For everyone else, use a password manager to pick a random password for everything.

What is beyond irresponsible? Monitoring logs and researching odd things found there?

Re: Ban me at the IP level if you don't like me

#222
post #168

Earlier quoted context omitted.

> All of the "blockchain is only for drug dealing and scams" people will sooner or later realize that it is the exact type of scenarios that makes it imperative to keep developing trustless systems. This is like saying “All the “sugar-sweetened beverages are bad for you” people will sooner or later realize it is imperative to drink liquids”. It is perfectly congruent to believe trustless systems are important and tha…

Tell that to the "web3 is doing great" crowd. I've met and worked with many people who never shilled a coin in their whole life and were treated as criminals for merely proposing any type of application on Ethereum. I got tired of having people yelling online about how "we are burning the planet" and who refused to understand that proof of stake made energy consumption negligible. To this day, I have my Mastodon inst…

[flagged]

Re: Ban me at the IP level if you don't like me

#224
post #153

Earlier quoted context omitted.

Only if your bank isn't competent in using them. Visa/Mastercard chargeback rules largely apply worldwide (with some regional exceptions, but much less than many banks would make you believe).

No, outside the US, both Visa and Mastercard regularly side with the retailer/supplier. If you process a chargeback simply because a UK company blocks your IP, you will be denied.

Visa and Mastercard aren't even involved in most disputes. Almost all disputes are settled between issuing and acquiring bank, and the networks only step in after some back and forth if the two really can't figure out liability.

I've seen some European issuing banks completely misinterpret the dispute rules and as a result deny cardholder claims that other issuers won without any discussion.

Re: Ban me at the IP level if you don't like me

#225
post #175

Externally I use Cloudflare proxy and internally I put Crowdsec and Modsecurity CRS middlewares in front of Traefik. After some fine-tuning and eliminating false positives, it is running smoothly. It logs all the temporarily banned and reported IPs (to Crowdsec) and logging them to a Discord channel. On average it blocks a few dozen different IPs each day. From what I see, there are far more American IPs trying to ac…

Crowdsec: the idea is tempting, but giving away all of the server's traffic to a for-profit is a huge liability.

You pass all traffic through Cloudflare. You do not pass any traffic to Crowdsec, you detect locally and only report blocked IPs. And with Modsecurity CRS you don't report anything to anyone but configuring and fine tuning is a bit harder.

Re: Ban me at the IP level if you don't like me

#226
post #175

Externally I use Cloudflare proxy and internally I put Crowdsec and Modsecurity CRS middlewares in front of Traefik. After some fine-tuning and eliminating false positives, it is running smoothly. It logs all the temporarily banned and reported IPs (to Crowdsec) and logging them to a Discord channel. On average it blocks a few dozen different IPs each day. From what I see, there are far more American IPs trying to ac…

The more egregious attempts are likely being blocked by Cloudflare WAF / similar.

Re: Ban me at the IP level if you don't like me

#227

I think a lot of really smart people are letting themselves get taken for a ride by the web scraping thing. Unless the bot activity is legitimately hammering your site and causing issues (not saying this isn't happening in some cases), then this mostly amounts to an ideological game of capture the flag. The difference being that you'll never find their flag. The only thing you win by playing is lost time. The best wa…

> The best way to mitigate the load from diffuse, unidentifiable, grey area participants is to have a fast and well engineered web product. I wonder what all those people are doing that their server can't handle the traffic. Wouldn't a simple IP-based rate limit be sufficient? I only pay $1 per month for my VPS, and even that piece of trash can handle 1000s of requests per second.

> I only pay $1 per month for my VPS, and even that piece of trash can handle 1000s of requests per second.

Depends on the computational cost per request. If you're serving static content from memory, 10k/s sounds easy. If you constantly have to calculate diffs across ranges of commits, I imagine a couple dozen can bring your box down.

Also: who's your webhost? $1/m sounds like a steal.

Re: Ban me at the IP level if you don't like me

#228
post #200

Earlier quoted context omitted.

Uh, no, it's definitely not. Hero begins with a consonant, so it should be preceded by "a", not "an".

Welcome to British English. The h in hero isn’t pronounced, same as hospital, so you use an before it.

That's not right. It's:

a hospital

an hour

a horse

It all comes down to how the word is pronounced but it's not consistent. 'H' can sound like it's missing on not. Same with other leading consonants that need an 'an'. Some words can go both ways.

Re: Ban me at the IP level if you don't like me

#229
I know opinions are divided on what I am about to mention, but what about CAPTCHA to filter bots? Yes, I am well aware we're a decade past a lot of CAPTCHA being broken by _algorithms_, but I believe it is still a relatively useful general solution, technically -- question is, would we want to filter non-humans, effectively? I am myself on the fence about this, big fan of what HTTP allows us to do, and I mean specifically computer-to-computer (automation/bots/etc) HTTP clients. But with the geopolitical landscape of today, where Internet has become a tug of war (sometimes literally), maybe Butlerian Jihad was onto something? China and Russia are blatantly and near-openly shoving their fingers in every hole they can find, and if this is normalized so will Europe and U.S., for countermeasure (at least one could imagine it being the case). One could also allow bots -- clients unable to solve CAPTCHA -- access to very simplified, distilled and _reduced_ content, to give them the minimal goodwill to "index" and "crawl" for ostensibly "good" purposes.

Re: Ban me at the IP level if you don't like me

#230

We solved a lot of our problems by blocking all Chinese ASNs. Admittedly, not the friendliest solution, but there were so many issues originating from Chinese clients that it was easier to just ban the entire country. It's not like we can capitalize on commerce in China anyway, so I think it's a fairly pragmatic approach.

Lmao I came here to post this. My personal server was making constant hdd grinding noises before I banned the entire nation of China. I only use this server for jellyfin and datahoarding so this was all just logs constantly rolling over from failed ssh auth attempts (PSA: always use public-key, don't allow root, and don't use really obvious usernames like "webadmin" or ).

I have my jellyfin and obsidian couchdb sync on my Tailscale and they don’t see any public traffic.
Post reply on HN