Latest OS X Security Patch Problems?

[Sean Chou]

I just installed the latest OS X 10.3.5 patch and I'm thinking it may
have messed up webrick. I've created trivially simple webrick scripts
to try it out and get the following error:

[2004-10-10 15:51:48] ERROR SocketError: getnameinfo: System error
/usr/local/lib/ruby/1.8/webrick/server.rb:147:in `peeraddr'
/usr/local/lib/ruby/1.8/webrick/server.rb:147:in `start_thread'
/usr/local/lib/ruby/1.8/webrick/server.rb:144:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:144:in `start_thread'
/usr/local/lib/ruby/1.8/webrick/server.rb:94:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:89:in `each'
/usr/local/lib/ruby/1.8/webrick/server.rb:89:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:79:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:79:in `start'

Has anyone else installed the patch and tried webrick subsequently? It
could also be something in my configuration since I have been messing
around with it, but thought I'd check with others before digging
through hundreds of conf files.

 

[Paul Battley]

I just installed the latest OS X 10.3.5 patch and I'm thinking it may
have messed up webrick. I've created trivially simple webrick scripts
to try it out and get the following error:

I have seen the same problem many times on OS X even before the 10.3.5
update. It relates to the reverse DNS lookup that the socket performs
on each connecting client by default. This is somehow broken on OS X,
apparently in gethostbyname(). If, like me, you don't care about
reverse dns lookups on each client, you can fix the problem and save
some processor time by adding this line near the top of your program:
Socket.do_not_reverse_lookup = true

That ought to do it, though I can't test anything until my iBook gets
back from repair (the infamous logic board problem).

Paul.