Re: Bug in ORBit 0.5.1 with floats/doubles ?

["Povl H. Pedersen" <pope netguide dk>]

> > 
> > Using http://www.parc.xerox.com/istl/projects/ILU/parseIOR/
> > to parse the resulting IOR I get:
> > _IIOP_ParseCDR:  byte order LittleEndian, repository id <IDL:Cashcow/CashcowCORBA:1.0>, 1 profile
> > _IIOP_ParseCDR:  profile 1 is 80 bytes, tag 3135221450, LittleEndian byte order
> > _IIOP_ParseCDR:  error:  No object for IOR.
> > Error parsing IOR:  inv_objref
> 
> It wants TCP/IP turned on, which I turned off in 0.5.3 because of much
> whining from the 'ignorant' GNOMEs. :)
> 
> 	echo ORBIIOPIPv4=1 > ~/.orbitrc
> 
> should do the trick.

OK. It also said something in the docs or a readme about security, and
how you would have to hack in the source yourself to get it working. I
assumed it was 'fixed' for good as it worked in my 0.5.1.

Now, the next thing we need is some sort of security. I can implement
something myself, but I am not sure it is good enough. Is the IOR
good enough, assuming I run a VPN between my 2 machines thus resulting
in nobody being able to see my traffic ? Or can I limit it to localhost ?

PS: I thought GNOMEs would like TCP/IP. Have one program script another one
on another machine.