[omniORB] Naming Server Crash
Duncan Grisby
dgrisby@uk.research.att.com
Tue, 14 Dec 1999 15:27:23 +0000
On Tuesday 14 December, Brecht Vermeulen wrote:
> It's with the 2.8.0 version (Linux debian 2.1). If you take the eg3
> example and you change in the client
> orb->resolve_initial_references("NameService")
> by (thus a typo :-) )
> orb->resolve_initial_references("NamyService")
> then the naming service blocks on next calls. Ideal for denial of service
> attacks !
This is sort of a bug. It only arises if omniNames has been started
with -ORBInitialHost and -ORBInitialPort. In that case, it deadlocks
trying to resolve initial references with itself. The workaround for
now is to start omniNames without the ORBInitialHost/Port.
Cheers,
Duncan.
--
-- Duncan Grisby \ Research Engineer --
-- AT&T Laboratories Cambridge --
-- http://www.uk.research.att.com/~dpg1 --