Bug#335897: similar problem workaround/solved

[Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de>]

Rene Engelhard wrote:
>>> So a problem on your side. qed.
>> What do you mean by that?
>> Why is it your point to set out to prove that this problem is on my side?
>> What proofs do you have that it is a problem on my side?
> 
> That restarting your firewall/portmapper fixed it. You sourself said that.
> That means somthing on that side didn't work correctly.

"That side" is not neccessarily "my side". I'm actually quite sure it is
not my side. I have no clue, what could have triggered portmap or the
firewall to reject to work with OOo, while all other apps continued to
work.

>> Unfortunately, I don't have the means of locating and fixing it further,
>> but I guess someone who could do that could also turn it into an
>> outright security exploit.
> 
> Proof? 

I didn't say Proof.

> I doubt that. It's not even a crash, just a hang, so maybe a DOS. And even then,
> if someone broke your nfs/firwall/portmapper per purpose (and he'd need root for that) you
> already have a problem....

I have no hints that someone gained root access to that machine - let
alone break anything.

Johannes