h4kunamata

17 ms·

1. 301.▲
   by h4kunamata 1y ago

   With Git Actions at full speed..... it is dying.
2. 302.▲
   by h4kunamata 1y ago

   I have mixed feeling about this. It has helped me in the past but yet, I could not reply nor post anything back to help others when I knew the solution because of the way how it works. To make matters worse while working in IT, I worked wit
3. 303.▲
   by h4kunamata 1y ago

   That is cool, but the list looks too small, the list https://public-dns.info/nameservers-all.txt is a lot bigger.
4. 304.▲
   by h4kunamata 1y ago

   I shared the link before, we do need to have firewall rules in place to enforce that. I had done it before but was wrong, I could still bypass PiHole. I had to recreate all my firewall rules because of a system crash, the order and place I
5. 305.▲
   by h4kunamata 1y ago

   I see your point, I have no need to block 99% of everything. For instance, many apps like bank apps use Google to delivery notification (there is a name for it), so if you start blocking everything, you won't use anything. To your cred
6. 306.▲
   by h4kunamata 1y ago

   I followed this blog to get the firewall dynamic firewall in place: https://labzilla.io/blog/force-dns-pihole Like you said, you cannot just block 443, the dynamic firewall uses a public list, which contains all the pu
7. 307.▲
   by h4kunamata 1y ago

   I run PiHole for years in my home network, I cannot live without it. With the years, I have made small changes to increase my control over it. I have a recursive DNS setup, PiHole filters everything, and what is left is processed locally vi
8. 308.▲
   by h4kunamata 2y ago

   This is a hot topic. I always refused to use company devices for so many reasons, it's a device not managed by me exposing my home network to risks I wouldn't otherwise have. I use Linux and will always use Linux. It's a gam
9. 309.▲
   by h4kunamata 2y ago

   Do this at your own risk!! Apparently there are two NON-OFFICIAL solutions: 1. Rename csagent.sys ( the file causing the BSOD ) 2. Rename c:\windows\System32\Drivers\Crowdstrike Again, do this at your own risk. Both workaround have been rep