> Le 18 juin 2018 à 15:54, Thierry Fournier <thierry.fourn...@arpalert.org> a > écrit : > > I don’t known. In fact it works, so it is not a bug. But, when I use the > reservation for an ex_data slot, it returns the slot 0, and this slot is > used for the compatibility layer and can be crush some data. I conclude > that is a bug in Openssl. The reservation function must give a slot > starting to 1. >
Indeed, it’s unexpected. > Maybe, the recommendation is to not mix the compatibility functions > like set_app_data() with *ex_data*() functions. But, I don’t see > anything about this. > Neither do I... In any case it's cleaner with *_get_ex_new_index. ++ Manu
