full-disclosure - OT microsoft "feature"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <59E872461F38D511BA3100508BB818870664502C@exnarocmbx3.ams.gblxint.com>
From: Jason.Ross at GlobalCrossing.com (Ross, Jason)
Subject: OT microsoft "feature"

-----Original Message-----
> From: Sacha J. Bernstein [mailto:sacha-fulldisclosure@...com.com] 
> Sent: Friday, April 16, 2004 9:59 AM
> To: Davide Del Vecchio; full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] OT microsoft "feature"
>
>
> The leading zero specifies that the number following is octal.  This is 
> expected behavior, and you will find that Solaris, FreeBSD, and Solaris
> all act exactly the same.
-------------------------------------------------------------------------

It is true that the command line is interpreting it as octal (as so many
others have pointed out also), however, what interested me is that it
doesn't appear to do so consistently:

F:\>ping 10.60.92.144
Pinging 10.60.92.144 with 32 bytes of data:

F:\>ping 010.60.92.144
Pinging 8.60.92.144 with 32 bytes of data:

F:\>ping 010.060.92.144
Pinging 8.48.92.144 with 32 bytes of data:

F:\>ping 010.060.092.144
Pinging 010.060.092.144 [10.60.92.144] with 32 bytes of data:



Also, Solaris 9 doesn't interpret it as octal in the same way, but does have
the same apparent quirkiness as DOS at the third octet:

bash-2.05$ uname -an
SunOS snusroc41 5.9 Generic_112233-04 sun4u sparc
SUNW,UltraSPARC-IIi-cEngine

bash-2.05$ ping -s 10.60.92.144 1 1
PING 10.60.92.144: 1 data bytes

bash-2.05$ ping -s 010.60.92.144 1 1
PING 010.60.92.144: 1 data bytes

bash-2.05$ ping -s 010.060.92.144 1 1
PING 010.060.92.144: 1 data bytes

bash-2.05$ ping -s 010.060.092.144 1 1
PING 010.060.092.144: 1 data bytes
9 bytes from irreantum.ams.gblxint.com (10.60.92.144): icmp_seq=0.


Not being overly familiar with octal, there may be a reason for this
behavior, but it struck me as kinda odd ...