Google DNS at 010.010.010.010

Post by Aardwolf » Mon, Nov 01, 2021, 11:47 PM UTC

floatingatoll wrote: post #88

lucb1e wrote: post #14

It's also at 010.010.2056 or 0x8080808 or 01002004010. I made a little tool a while ago that iterates over all the options that I know of: https://lucb1e.com/randomprojects/php/funnip.php?ip=8.8.8.8 The variant found by OP is apparently the very last option that my tool generates. These days, Firefox is a bit boring (okay, okay, I'll admit it's a good choice for security) and translates these at the first opportunity…

Octal is a great way to mislead both human beings and software, and I kind of hope it gets removed by browsers as a result of this new attention. It’s one of those things that isn’t productive or useful in any way in our modern era and serves only to complicate with no benefit in return.

Octal as a base is fine, but that misleading notation where starting with a 0 means octal is not.

Post by broodbucket » Tue, Nov 02, 2021, 12:05 AM UTC

floatingatoll wrote: post #128

broodbucket wrote: post #124

Earlier quoted context omitted.

This is funny for me to read because I converted a bunch of constants for file permissions to octal values in the Linux kernel because they're harder to read and there's multiple ways of arriving at the same value. You wanna look up what a constant is and you find #define S_IRUGO (S_IRUSR|S_IRGRP|S_IROTH) or you could see 0444 and immediately know what it means. I agree in cases where you're modifying existing permis…

How do you represent a=rX in octal?

Oh, I didn't know what X did and made assumptions.

If you split file permissions into two halves - defining the initial permissions / modifying something that already exists - I can see how it makes sense to do both with the same syntax since modifying existing permissions is worse with octal.

Re: Google DNS at 010.010.010.010

Re: Google DNS at 010.010.010.010