The Poor Man's (or Woman's) Intrusion Detection System
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.md 3.0 KiB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. ChipMaster's Black Lists
  2. ========================
  3. These are provided simply for the curious. I'm actively using these
  4. lists to block traffic I don't want happening. I'm very militant
  5. about traffic on my network. I don't want my computers doing anything
  6. I didn't ask it to do. So I block for the following reasons:
  7. 1. I find a program reaching out across the net when there is no visual
  8. reason for them to do so. This could be any number of things
  9. like: update servers, feature use tracking, DRM tracking, ...
  10. 2. Website advertisers: IMO these are particularly nasty. Its not
  11. that I necessarily have anything against a site funding itself
  12. with ads. Although some sites are rude in how they place them or
  13. they perform rude, malware like actions. But the **REAL** risk,
  14. as far as I'm concerned, is that many cyber-thugs use ad services
  15. to distribute malware. Unfortunately the ad services don't seem
  16. to have any interest in vetting their scuzz.
  17. 3. Some host names are specifically used for tracking, like "g00gle
  18. analytics". I have nothing against a site owner wanting to know
  19. how their site is being used. All of us, with websites, want to
  20. know how popular the site is and specifically which pages are the
  21. most viewed and common occurring browse patterns, to tell us how
  22. we may be able to better our sites. But off-site trackers slow
  23. down my browsing experience and someone as massive as g00gle can
  24. aggregate this with a lot of other data sources to learn and sell
  25. waaay too much about me.
  26. 4. I want to deliberately block updates. Although as a Linux user
  27. that's not usually my concern. But I do it for clients to prevent
  28. M$ and others from breaking stuff. I also do it so I won't be
  29. constantly hounded by "I can't update" or "there is a new
  30. version" messages.
  31. 5. Unknown traffic being generated by device X, like Android
  32. devices. What on earth are they busy chattering about? That's
  33. malware like activity. Or maybe its **real** malware activity?
  34. =-O
  35. 6. Some location was causing me to _wait_. Common examples are the
  36. "like" buttons for major social networks. The off-site hosted
  37. code is either large, on a slow server or behaving in suspicious
  38. manner like taking too much CPU power. I've had some of those
  39. literally lock a machine up until I kill them. If nothing else
  40. this is extremely poor coding but it could be worse.
  41. 7. I just don't know what its for and I notice nothing wrong when I
  42. block it. :-D
  43. 8. Something in its behavior alerts me to potential danger.
  44. And there are other reasons something might tweak me funny and I say,
  45. "That's enough of that."
  46. All of that to say that the things I'm blocking might not actually be
  47. _bad_ but they annoy me for one reason or another and it may just be
  48. a philosophical disagreement on my part. But think about the enormous
  49. amount of browsing information that can be accumulated by g00gle
  50. simply hosting popular JavaScript libraries and then linking that to
  51. your g00gle login...
  52. Use any of this at your own peril.
  53. - ChipMaster