So your threat model assumes an actor with a quantum computer capable of breaking RSA, but not a regular computer capable of filtering by IP address?
See also https://lemmy.world/u/p1mrx
So your threat model assumes an actor with a quantum computer capable of breaking RSA, but not a regular computer capable of filtering by IP address?
“We are in the late stages of having a user base”
.gov is allowed for use by any governments that invented the internet.
.us is sketchy AF. They should use something.gov.
Here is the building on Street View:
It’s been knocked down and replaced since 2015.
It’s generally a bad idea to create fake Google accounts, if you have a primary account you don’t want banned.
I listed the 5 possible digits. What’s missing?
IPv6 subnet masks are long, but super easy because of hexadecimal. A bunch of F
s, then [
then a bunch of ]?0
s.
fd00::x is shorter than 192.168.x.x
Technically you’re supposed to use fdxx:xxxx:xxxx::x, but on your home network nobody cares.
Did you mean caveat emptor (buyer beware), or do you refer to Amazon as caveat emporium (the beware market)?
I’ll go with… Hieronymus Bosch.
You can tell it’s the '90s because of the TV on the couch.
Roughly speaking, fd00::123 is the IPv6 equivalent of 192.168.0.123
A device on your private IPv4 network can send packets directly to 104.21.36.127
via NAT. How will it send packets to 2606:4700:3033::6815:247f
? There’s not enough space in the IPv4 header.
You can statically number a LAN with fd00::/8 and NAT66 to the internet, if you really want to.
Here’s a presentation: https://www.youtube.com/watch?v=OAB6Xh8L1kk
They’re basically generating weird patterns that manipulate light to project a very precise shadow.
Solar PV tortillas taste awful and hurt my teeth.
A VPN encrypts traffic between your device and the VPN server, and any packet on that path includes your IP address. So anyone attempting to decrypt your VPN traffic can trivially distinguish your packets from other users of the VPN server.