Re: [users@httpd] Re: off topic - how to secure httpd

2024-12-04 Thread gene heskett
On 12/4/24 20:46, Jonesy wrote: On Wed, 4 Dec 2024 18:09:06 -0500, gene heskett wrote: On 12/4/24 09:20, Marc wrote: Having these ipv6 so abundantly available made me also think about how I have currently arranged my abuse mitigation. Currently I am having ipsets for different subments and use

[users@httpd] Re: off topic - how to secure httpd

2024-12-04 Thread Jonesy
On Wed, 4 Dec 2024 18:09:06 -0500, gene heskett wrote: > On 12/4/24 09:20, Marc wrote: >> >> Having these ipv6 so abundantly available made me also think about >> how I have currently arranged my abuse mitigation. Currently I am >> having ipsets for different subments and use a sort of honeypot

Re: [users@httpd] off topic - how to secure httpd

2024-12-04 Thread gene heskett
On 12/4/24 09:20, Marc wrote: I hope nobody minds me addressing this off topic question. I was thinking about adding ipv6, and when I got a range to try with, I was actually surprised how many I got. This made me wonder how many ipv6 are being used and how many ipv4. Having these ipv6 so abun

Re: [users@httpd] off topic - how to secure httpd

2024-12-04 Thread E.S. Rosenberg
If you are storing blocks per single IP that won't scale (storage wise, searching the list/table, just a bitmap of the whole IPv6 space is 10^19 Exabytes! [2^128 bits in EiB]), if you aggressively block whole ranges you will most likely end up blocking a lot of legitimate potential users. I also t

[users@httpd] off topic - how to secure httpd

2024-12-04 Thread Marc
I hope nobody minds me addressing this off topic question. I was thinking about adding ipv6, and when I got a range to try with, I was actually surprised how many I got. This made me wonder how many ipv6 are being used and how many ipv4. Having these ipv6 so abundantly available made me also t