[omniORB] OmniORB GIOP Message padding

[MICHEL Franck (SAGEM DEFENSE SECURITE)]

Hi all,

I saw in the OmniORB mailing list that there was some discussions (back in 2005) related to uninitialized padding in GIOP messages.

We are encountering some issue at this moment linked to this problem since we are trying to compare GIOP message replies.
Due to the uinitialized padding, two replies for the same request are not binary identical.

Have there been some progress :
- compilation option defined or
- patch built (since 2005) or
- solution

regarding the possible initialization of padding ?

Thanks for your help,
Frank MICHEL

#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caract?re priv?. S'ils ne vous sont pas destin?s, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque mani?re que ce soit le contenu. Si ce message vous a ?t? transmis par erreur, merci d'en informer l'exp?diteur et de supprimer imm?diatement de votre syst?me informatique ce courriel ainsi que tous les documents qui y sont attach?s."
******
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20111213/62956583/attachment-0001.htm

[Duncan Grisby]

On Tue, 2011-12-13 at 10:42 +0100, MICHEL Franck (SAGEM DEFENSE
SECURITE) wrote:

[...]

Post by MICHEL Franck (SAGEM DEFENSE SECURITE)
Due to the uinitialized padding, two replies for the same request are not binary identical.
- compilation option defined or
- patch built (since 2005) or
- solution

I'm not aware of anyone having done that. It's certainly not in the
mainstream omniORB release.

There are quite a few places that buffers are allocated, so clearing
buffers to ensure padding has known values is not a totally trivial
thing. It shouldn't be that hard to track all the places down, though.

Cheers,

Duncan.

[MICHEL Franck (SAGEM DEFENSE SECURITE)]

Hi Duncan,

Thank you for your reply.

After checking in the omniORB sources, we came up with a patch in "orbcore/giopStream.cc" which reset the content of the buffer that was just sent to the socket.

As the "giopStream_Buffer" structure is constantly reused, padding shows content from previous requests which is not overwritten.

This is simple but it works. I known it is a borderline usage but some people from the mailing list stated it could help in some cases.
It does for us.

We can provide with the patch if you're interested.

Thanks,
Frank MICHEL

-----Original Message-----
From: Duncan Grisby [mailto:***@grisby.org]
Sent: Wednesday, December 14, 2011 6:16 PM
To: MICHEL Franck (SAGEM DEFENSE SECURITE)
Cc: omniorb-***@omniorb-support.com
Subject: Re: [omniORB] OmniORB GIOP Message padding

On Tue, 2011-12-13 at 10:42 +0100, MICHEL Franck (SAGEM DEFENSE
SECURITE) wrote:

[...]

Post by MICHEL Franck (SAGEM DEFENSE SECURITE)
Due to the uinitialized padding, two replies for the same request are not binary identical.
- compilation option defined or
- patch built (since 2005) or
- solution

I'm not aware of anyone having done that. It's certainly not in the
mainstream omniORB release.

There are quite a few places that buffers are allocated, so clearing
buffers to ensure padding has known values is not a totally trivial
thing. It shouldn't be that hard to track all the places down, though.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --


#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caract?re priv?. S'ils ne vous sont pas destin?s, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque mani?re que ce soit le contenu. Si ce message vous a ?t? transmis par erreur, merci d'en informer l'exp?diteur et de supprimer imm?diatement de votre syst?me informatique ce courriel ainsi que tous les documents qui y sont attach?s."
******
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#