Hacker Newsnew | past | comments | ask | show | jobs | submit | erros's commentslogin

Don't stress it. It's clear someone in the know did not respect or communicate the embargo and were sharing information with people who weren't in the need to know. The problem is less with you and more with the entire process. Case in point, we saw ZDI drop some zerodays on the kernel mailing list this week.

It is clear as day that this industry is fucked, and has no clue on how to deal with operational security for sensitive information. It is what it is at this point. The days of full disclosure are back.


Money. They make so much money from malvertisement that it doesn't make sense to remediate them. It's corporate greed and they've known about this since the 2010s, various campaigns have sprung up and have caused untold X amount of dollars in damages in breaches, and nothing changes. I've heard at least one FBI agent who had investigated cases related to malvertisement put Google up there with some of the worst ad networks.


This is it. The truth is Google's largest revenue sources are scams, fraud, and malware, and they wouldn't be in business without them. They're not going to remove all of their highest pay per click customers because it might harm society or something.

Just try to convince Google to remove "MapsQuest Driving Directions", a browser hijacking extension advertiser who clearly impersonates one of Google's competitors: It's an extremely high value scam targeting seniors (the folks who mostly look for MapQuest on... Google) and it makes them way too much money for them to stop it.


So true!


Ladies and gentlemen, this person solves problems. Let it be known.


he gave himself a pat on the back


You may want to update this post to disable password authentication, and thus you'll no longer need to install fail2ban. An important goal is to tighten your attack surface, not expand it. At this point you will still have an exposed SSHd server, so I'd recommend throwing the server under tailscale. You can setup the SSHd listener to use your tailscale IP or setup tailscale for SSH via ACLs (https://tailscale.com/tailscale-ssh).

Additionally you can further tighten controls of incoming logins with the use of AllowGroups to tighten your controls on which groups can log into the system. This would mitigate a scenario where an adversary is able to escalate enough privileges to write an .authorized_keys file to a non-privileged user which may have a shell still configured.

Finally, unless you're treating this server as a bastion host of sorts, you probably should disable forwarding for agents or X11 etc. We've seen a lot of adversaries move laterally due to this agent forwarding.


> You may want to update this post to disable password authentication

Probably not, as that’s one of the first things they do.

That said, I feel like all this fail2ban stuff is very much cargo culting in the selfhosting community. I’ve had my VPS SSH server on port 22 with no fail2ban for slightly over a decade, exposed to the public internet (home server is behind tailscale, VPS hosts the stuff I always want accessible from everywhere). Bots try it, they fail, the end. Maybe I’m missing something, but I have yet to find a good reason for the added complexity.


This and possibly unknown similar flaws is a good reason for not advertising ssh:

https://arstechnica.com/security/2024/07/regresshion-vulnera...


fail2ban is great for reducing clutter in logs. When I'm trying to debug something using auth.log I don't want to sift through 800 attempts by some IP to SSH in as root.

It gives just enough info about the origin and nature of attempted intruders without overwhelming detail.


I'm sure we all could appreciate Mega for what it was, and we could also debate the charges and go back and forth on extradition laws. The reality is that according to the DoJ, US citizens were victimized by a service that used US assets (servers) within its territory. That opens the doors for litigation. This happens literally in every country that can enforce it.

Like Reddit, HN has a crowd of anti-US folks with terrible sentiment until, you know, when they need the US or need a job in the U.S. The hypocrisy is astounding.


Just out of curiosity I booted up a box with 10x RTX A6000 @ 451.6 TFLOPS

    Speed.#1.........:    38789 H/s (11.17ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#2.........:    39017 H/s (11.17ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#3.........:    38894 H/s (11.16ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#4.........:    39254 H/s (11.02ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#5.........:    38626 H/s (11.17ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#6.........:    39448 H/s (10.94ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#7.........:    39256 H/s (11.06ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#8.........:    38966 H/s (11.14ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#9.........:    38870 H/s (11.17ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#10.........:    39259 H/s (11.01ms) @ Accel:128 Loops:64 Thr:64 Vec:1
    Speed.#\*.........:   390.0 kH/s
Used the same example as the author with 100500 iterations. I think with some good wordlists, I'd wager a ton of low hanging fruits will be wiped within a reasonable time. If we're talking a threat actor with $$, they'd do some serious damage on this dump.

*edit: just wanted to clarify that I think bruteforcing this dump wouldn't be as useful. It would still take a crapload of resources to be effective or useful in that scenario.


So you're doing 4e10 hashes per second or 390k password guesses per second. At what price per hour?


Used vast.ai for this setup: $5.875/hr. Using their API you can likely find better deals and launch a series of different setups and optimize your spending. Hope that helps.


To be fair I don’t think nation state actors care about the bill. Be it US, China, Russia, Saudi, etc.


Do you get extra credit if one of the first accounts you hack has a cloud provider account credentials that you can then spin up more machines to further the attack on someone else's dime?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: