Skip to main content

Problem:

  • Product Name:VisiBroker
  • Product Version:6.x, 7.0
  • Product Component:ORB
  • Platform/OS Version:Linux, HP-UX

Is there any pattern in the shared memory key which VisiBroker generates?
Is there any way to restrict a range of keys to avoid collision with other keys?

Resolution:

VisiBroker uses the system function

key_t ftok(const char *pathname, int proj_id)

to generate shared memory key using "/tmp/orb_${pid}_${uid}_shm" as pathname, 1 as proj_id.
In the pathname, the first parameter, ${pid}, is the server's process id. The second parameter, ${uid},
is an unique id internally generated by the server.

Thus there is no way to restrict keys in specific number range.


#VisiBroker
#Security