On Sat, May 30, 2009, Guenter wrote: > Hi, > Ger Hobbelt schrieb: > > It's advised to register this at the OpenSSL issue tracker by > > forwarding this to [email protected] > > It's no guarantee to get serviced pronto, but at least it'll get the > > attention of the core devs when they have time. > > > > (The jury is still undecided on the statistics, but providing a patch > > as attachment /may/ help getting served. Also mention it's clashing > > under Netware in the subject header to make this particular bit pop up > > on the RT screens more prominently.) > sure, no prob, also creating a patch is no prob; though I was hoping > that Steve (who seems to have written these functions 10 years ago) > would comment a bit on them: why were these two functions not prefixed > with PKCS12_ like all other functions from the beginning on? Where they > perhaps never meant for exporting but as internal functions only? > A patch would depend on this info I think. >
Well this was in a time long ago when name clashes were pretty much unheard of. This was before we put headers under openssl/ and generic names like Malloc and Free were in use. They aren't really PKCS12 related functions just general purpose utility functions adding an OPENSSL_ prefix would be most appropriate. Changing or deleting function names is always controversial especially in stable branches as it can break binary compatibility. I second the comment about RT. When the dev team (I include myself in this) are seeing which issues need addressing in an upcoming release they can readily see issues in RT and any discussion on the matter. Trawling through months or even years or openssl-dev posts isn't likely to happen very often. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
