On Thu, 2010-11-25 at 18:08 +0000, Chris Young wrote: > Actually it's just down to the differences between C-style libraries > and .libraries. A .library exists once in memory (code+data), so any > callers will share the same global variables. (the security flaw > isn't with libwapcaplet per se, only this .library version)
Aha. In which case, yes, that makes much more sense. > The other solution is to change back to using .so, but I was trying to > move away from them as they cause problems, have a slight overhead and > don't work properly on OS4.0. If you're willing to wait a week or so, it's possible that we'll have time to change the way the libraries work so that they do operate in a context. This change needs to happen so that they can be used from other shared libraries, anyway. Additionally (and with precisely zero knowledge of the issues involved) it seems to me that the stubs could be auto-generated. Is this correct? If so, it's probably possible to include the appropriate support in the core buildsystem. J.
