#ipranges — Public Fediverse posts

Finally finished my #authelia setup yesterday. #SSO is amazing. Strong #password + #2FA everywhere just feels right.

Not only that, but you can also configure #AccessControls and trusted #IPRanges.

Since i'm not the only user on my #server, having fine-grained control is very welcome.

#security #linux #homelab #selfhosting

summarized here: https://www.eke.li/2023/02/domains-in-docs/

when writing #technicalDocumentation - don't use real #urls or #ipAddresses. you never know what will grab those and use them.

there are reserved #domains and #ipRanges for just this!

for #url: the top-level-domains
.test, .example, .invalid and .localhost and the domain example.com are reserved

for ip-adresses the blocks 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24 are reserved

they are always safe to use in #documentation

SINCE THE START of coronavirus, the filesize of #IPAddresses owned by #Amazon saw a more than four fold increase!

Going from 280kb to 1.2Mb!

https://web.archive.org/web/20200403022547/https://ip-ranges.amazonaws.com/ip-ranges.json

We realise filesize is a fairly loose metric for #IPRanges but its alarming nonetheless.

#CAGEFAM #internetAttack #monopoly #plutocracy #blockAmazon #scamazon #ethScamTokens #ethereumScam #CBDC #AWS

@arh
It's something you need to see for yourself, instructions to run a #packetSniffer are fairly direct. There's tcpdump or Wireshark.

#Amazon #IPRanges are available at:
https://ip-ranges.amazonaws.com/ip-ranges.json

---

Meanwhile Firefox calls up Amazon, #Google and #Cloudflare frequently…

Google ranges:
https://www.gstatic.com/ipranges/goog.json

Cloudflare (IPv4, change for IPv6)
https://www.cloudflare.com/ips-v4

Stay safe, friend.