Hacker News
Someone on Torrent Sites Kept Fucking with My Sonarr
aftbit
|next
[-]
Now you need 9 different pieces of software that end in *arr, all of which implement parts of the solution that you want and parts that you don't, and none of them is even a torrent client!
And they don't even work with torrent sites reliably, so people then spend money on a Usenet subscription like it's 1990 again.
bhaney
|next
|previous
[-]
Alternatively, if there's a way to have qbit itself mark the download as "Failed" when it detects and refuses to download an executable, that would work too. I don't use qbit personally so I don't know if that's a thing it can be configured to do.
shmoil
|next
|previous
[-]
gradstudent
|root
|parent
|next
[-]
shmoil
|root
|parent
|next
[-]
If you are too old for trackers, then just sign up for usenet. You will have to pay for it though.
lelandfe
|root
|parent
|next
|previous
[-]
TBF this isn’t a revival of some 90s thing, this is just how private trackers have been. What was the same in the aughts, for instance.
torben-friis
|root
|parent
|next
|previous
[-]
In practice, it's just adding an API key, setting a rule in the app to remove after x and then you can go back to ignoring it.
Havoc
|next
|previous
[-]
The whole sticky notes next to monitor is not a joke. I bet you could grab some crypto recovery keys this way
josu
|next
|previous
[-]
dd_xplore
|next
|previous
[-]
para_parolu
|next
|previous
[-]
stronglikedan
|root
|parent
[-]
joloooo
|next
|previous
[-]
bastard_op
|next
|previous
[-]
Scammers always have a new trick up their sleeve.
comrade1234
|next
|previous
[-]
c-hendricks
|root
|parent
|next
[-]
Using settings on the indexer isn't great since with Prowlarr the user doesn't actually interact with the indexer portion of Sonarr.
Doing it in release profiles by bumping down their score is a cute workaround but then the torrents will just stop saying ".exe" in their title.
Really it's a thing Sonarr have to do, as evidenced by the multiple PRs they have to try and finally do it.
yborg
|root
|parent
|next
|previous
[-]
queenkjuul
|root
|parent
|previous
[-]
serf
|root
|parent
[-]
let's all join a private tracker!
that'll fix the problem, the bad actors won't chase the crowd, and it definitely wont end in a burning of the library of alexandria loss-of-history what.cd style event again and again if the public can't archive it.
/s
how about we just create an exe/bat/com exclusion on our dumb-as-dick media downloaders like sensible people have been doing for 30+ years?
LoganDark
|next
|previous
[-]
The ability to change it, dude. Have you never written a malware before?
Often a primary concern is the security response, so you want redundancy for the ability to work around enforcement action, such as website takedowns.
Hardcoding a scapegoat into the malware itself also buys you time, so that the first enforcement action is less likely to spend your backups right away.
> And to whoever made this: you probably spent weeks or shit ton of tokens on ChaCha20, AES-CTR, runtime API hashing, anti sandbox scoring, Chrome app bound encryption bypasses, just to make a shitty skid malware.
People have been making infostealers that support hundreds or thousands of different apps and corners of your computer for decades. Plenty of vendors pride themselves on it.
Meanwhile you used LLM to write a bunch of your article, and seemingly to do the RE too...