Inconsistent octal madness
$ ping 010
PING 010 (0.0.0.8) 56(84) bytes of data.
$ ping 010.1.1.1
PING 010.1.1.1 (8.1.1.1) 56(84) bytes of data.
$ ping 018
ping: 018: Name or service not known
$ ping 18
PING 18 (0.0.0.18) 56(84) bytes of data.
$ ping 018.1.1.1
PING 018.1.1.1 (18.1.1.1) 56(84) bytes of data.
$ ping 18.1.1.1
PING 18.1.1.1 (18.1.1.1) 56(84) bytes of data.
Daniel T 🌻
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
Unknown parent • • •daniel:// stenberg://
in reply to daniel:// stenberg:// • • •Dan Sugalski
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to daniel:// stenberg:// • • •urlapi: treat 0 alone as decimal number in IPv4 address by bagder · Pull Request #16652 · curl/curl
GitHubLudwig Behm
in reply to daniel:// stenberg:// • • •you have indeed a strange debian. I can't reproduce decimal conversion with leading 0 on debian testing, either.
Does nsswitch.conf play a role in parsing ip address notation? Or is this only depended on ping version?
I would vote for not accepting any non-decimal notations. Neither octal, nor hex, nor anything else.
daniel:// stenberg://
in reply to Ludwig Behm • • •Romain Tartière
in reply to daniel:// stenberg:// • • •@inguin Similar result on FreeBSD:
ping: cannot resolve 018.1.1.1: Name does not resolve
daniel:// stenberg://
in reply to daniel:// stenberg:// • • •David Wheeler
in reply to daniel:// stenberg:// • • •Brian
in reply to daniel:// stenberg:// • • •Harry Sintonen
in reply to daniel:// stenberg:// • • •UpCloud
in reply to daniel:// stenberg:// • • •Author Hester Velmans
in reply to daniel:// stenberg:// • • •Paul_IPv6
in reply to daniel:// stenberg:// • • •many DNS server implementations have taken the IETF "be liberal in what you accept" to dizzying heights. what is "conservately sent" can be quite a puzzle to work out.
some DNS flag days and serious efforts by the big FOSS implementations has reined in a lot of that chaos but it can still be fun.
sadly, various system/OS stub resolvers deciding they are more clever than you have taken up much of the chaos slack and introduced new, very inexplicable behaviors.
suspect you have similar war stories about http/https/tls...
daniel:// stenberg://
in reply to Paul_IPv6 • • •Christian Huitema
in reply to daniel:// stenberg:// • • •Paul_IPv6
in reply to Christian Huitema • • •@huitema
"I felt a great disturbance in the internet, as if millions of badly written, loadbearing scripts suddenly cried out in terror and were suddenly broken."
sadly, the above is why we wind up with so many horrible hacks in code and protocols.
when working in support for a FOSS project, i regularly got complaints about improvements and bug fixes breaking some script that depended on the broken/buggy behavior.
daniel:// stenberg://
in reply to Paul_IPv6 • • •Koos van den Hout
in reply to daniel:// stenberg:// • • •I'm not sure it's DNS, it could be earlier in the local functions to handle IP addresses in different notations (I am not going to embarrass myself by naming these functions to you).
That will make things like
$ ping 0x7f000001
PING 0x7f000001 (127.0.0.1) 56(84) bytes of data.
$ ping 0177.0.0.1
PING 0177.0.0.1 (127.0.0.1) 56(84) bytes of data.
work without ever hitting the resolver.
daniel:// stenberg://
in reply to Koos van den Hout • • •@KHoos I am sure it is the DNS. Using ltrace I could see how 018.1.1.1 gets a 0 back from the getaddrinfo() call. I can also reproduce it with dig directly.
The precise point was to use 018 as the first number, as that is 0-prefixed but not a valid octal.
Robert Edmonds
in reply to daniel:// stenberg:// • • •All of those except 018.1.1.1 get resolved directly by the OS for me.
root@592cda340524:/# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="debian.org/"
SUPPORT_URL="debian.org/support"
BUG_REPORT_URL="bugs.debian.org/"
root@592cda340524:/# grep hosts: /etc/nsswitch.conf
hosts: files
root@592cda340524:/# getent ahosts 010
0.0.0.8 STREAM 010
0.0.0.8 DGRAM
0.0.0.8 RAW
root@592cda340524:/# getent ahosts 010.1.1.1
8.1.1.1 STREAM 010.1.1.1
8.1.1.1 DGRAM
8.1.1.1 RAW
root@592cda340524:/# getent ahosts 018
root@592cda340524:/# echo $?
2
root@592cda340524:/# getent ahosts 18
0.0.0.18 STREAM 18
0.0.0.18 DGRAM
0.0.0.18 RAW
root@592cda340524:/# getent ahosts 018.1.1.1
root@592cda340524:/# echo $?
2
root@592cda340524:/# getent ahosts 18.1.1.1
18.1.1.1 STREAM 18.1.1.1
18.1.1.1 DGRAM
18.1.1.1 RAW
root@592cda340524:/#
Debian -- The Universal Operating System
www.debian.orgPetr Menšík
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Petr Menšík • • •Petr Menšík
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Petr Menšík • • •Jim Fuller
in reply to daniel:// stenberg:// • • •j5v
in reply to daniel:// stenberg:// • • •Cassandrich
in reply to daniel:// stenberg:// • • •Cassandrich
in reply to Cassandrich • • •the vessel of morganna
in reply to Cassandrich • • •Cassandrich
in reply to the vessel of morganna • • •daniel:// stenberg://
in reply to Cassandrich • • •Cassandrich
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Cassandrich • • •Cassandrich
in reply to Cassandrich • • •the vessel of morganna
in reply to Cassandrich • • •the vessel of morganna
in reply to the vessel of morganna • • •@dalias sdmzsapnsp01:/etc/bind root$ host 018.0.0.0
018.0.0.0 has address 18.0.0.0
Host 018.0.0.0 not found: 3(NXDOMAIN)
Help, I'm nauseous.
the vessel of morganna
in reply to the vessel of morganna • • •@dalias Even more batshit:
sdmzsapnsp01:/etc/bind root$ host 019.005.005.006 019.005.005.006 has address 19.5.5.6
daniel:// stenberg://
in reply to the vessel of morganna • • •