Andrew Pam wrote:
On Fri, Apr 15, 2005 at 07:32:52AM -0400, Bob wrote:
I want a host, so the last n ought not to be zero(most likely
a network),
That's your mistake. There is no rule that hosts can't have an IP address ending in zero. In any network larger than /24 it is perfectly legal and likely that there will be hosts where the last octet of the address is zero.
Hope that helps,
Andrew
Falling through bad input to giving away the store is not my default(that would be "my mistake") for cleartext exchanges. The law of averages carries a lot of weight, and I would be a fool to be a scofflaw there. The left lane is available.
What is astronomically more likely than an imaginary ldap server host's ip ending in 0 is that a realworld bad config was munged to "", became 0 as we in perl so often use "" and 0 interchangeably, and bad code fall though to 0.0.0.0. Then I don't DENY, I decline to presume to sink my hook in my people's business whilst they are probably just unawares(of THEIR little mistake), as the law of averages would have it.
There is also the law of distinct possibilities. I'm already bending over pretty far not to enforce 127.0.0.0/8 ip's for cleartext password exchanges. I don't want to ruin somebody or get blamed.
Have you ever noticed that a lot of applications default install on localhost? Ever noticed that reiserfs won't boot without a human typing "Yes", case sensitive, before doing anything(I can hack the code if I don't like it)?
If you have a real world application which needs ssl ldap server, Net::LDAP has those calls.
-Bob Dodds
