Re: How is "0x43.0x9e.0x87.0xa9" a valid domain?
- From: Barry Margolin <barmar@xxxxxxxxxxxx>
- Date: Sat, 20 May 2006 18:36:56 -0400
In article <v1Hbg.27079$4H.25957@dukeread03>,
"M. Trimble" <user@xxxxxxxxx> wrote:
Unruh wrote:
"Joe" <jtester8424@xxxxxxxxx> writes:
...
Because it is just a number. In hex ( which is what the 0x means).
Took one look at that and, 'Oh. Hex. OK, translate to decimal and see what
comes up'. But, why encode it that way? someone trying to obscure the IP
address [like a kitten covering up on the linoleum]?
Someone puzzle me that one???
It probably gets around some security programs, which know how to
recognize dotted-decimal addresses and block them, but don't recognize
the hex.
--
Barry Margolin, barmar@xxxxxxxxxxxx
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
.
- References:
- How is "0x43.0x9e.0x87.0xa9" a valid domain?
- From: Joe
- Re: How is "0x43.0x9e.0x87.0xa9" a valid domain?
- From: Unruh
- Re: How is "0x43.0x9e.0x87.0xa9" a valid domain?
- From: M. Trimble
- How is "0x43.0x9e.0x87.0xa9" a valid domain?
- Prev by Date: Re: The origin of breakin attempts
- Next by Date: Re: The origin of breakin attempts
- Previous by thread: Re: How is "0x43.0x9e.0x87.0xa9" a valid domain?
- Next by thread: The origin of breakin attempts
- Index(es):
Relevant Pages
|