I’ve told qbit to exclude those files and many other extensions from someone’s helpful comment on here previously, but the stack keeps on grabbing and seeding them, which the latter I’m a little unhappy about sharing malware.

While all the boxes on my network have no sign of Windows to get exploited it does worry me about another family members arrr stack because there is a Windows laptop down there, but thankfully not used for media consumption.

Help?

edit: big thanks to kiszkot@feddit.nu for pointing me in line separators instead of comma separated exclusions!

  • kiszkot@feddit.nuEnglish
    0·
    14 days ago

    According to some posts online you should use pattern matching to exclude filetypes. “*.ink” should match any file ending in “ink”. Exclusions should be separated by a newline.

    • ladfrombrad 🇬🇧@lemdro.idOPEnglish
      1·
      4 hours ago

      Separated by a newline

      You brilliant person got it in one! Love you 😘

      https://files.catbox.moe/tda0my.jpg

      Now I haven’t tested which of the line separated ones blocked it, but the wildcard *.lnk didn’t work when they were comma separated but do when line separated. have tested, and these are the most common so far I’ve seen

      *.lnk

      *.scr

      *.arj

      *.zipx

      *.exe

      *.cmd

      *.bat

      *.scf

      Again, 👌