[omniORB] Naming Server Crash
Brent Fulgham
brent.fulgham@xpsystems.com
Tue, 14 Dec 1999 14:27:11 -0800
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BF4682.5D3507B4
Content-Type: text/plain;
charset="iso-8859-1"
> > 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.
>
Would this also occur with an /etc/omniorb.cfg such as:
host blah
port 8088
Or is it only if these are passed on the command line?
-Brent
------_=_NextPart_001_01BF4682.5D3507B4
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: [omniORB] Naming Server Crash </TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>> > It's with the 2.8.0 version (Linux debian 2.1). If you take the eg3</FONT>
<BR><FONT SIZE=2>> > example and you change in the client </FONT>
<BR><FONT SIZE=2>> > orb->resolve_initial_references("NameService")</FONT>
<BR><FONT SIZE=2>> > by (thus a typo :-) )</FONT>
<BR><FONT SIZE=2>> > orb->resolve_initial_references("NamyService")</FONT>
<BR><FONT SIZE=2>> > then the naming service blocks on next calls. Ideal for </FONT>
<BR><FONT SIZE=2>> denial of service</FONT>
<BR><FONT SIZE=2>> > attacks !</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> This is sort of a bug. It only arises if omniNames has been started</FONT>
<BR><FONT SIZE=2>> with -ORBInitialHost and -ORBInitialPort. In that case, it deadlocks</FONT>
<BR><FONT SIZE=2>> trying to resolve initial references with itself. The workaround for</FONT>
<BR><FONT SIZE=2>> now is to start omniNames without the ORBInitialHost/Port.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>Would this also occur with an /etc/omniorb.cfg such as:</FONT>
</P>
<P><FONT SIZE=2>host blah</FONT>
<BR><FONT SIZE=2>port 8088</FONT>
</P>
<P><FONT SIZE=2>Or is it only if these are passed on the command line?</FONT>
</P>
<P><FONT SIZE=2>-Brent</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BF4682.5D3507B4--