[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: SHA384_Update symbol clash with libgs
On 04/05, Edgar Fuß wrote:
> Apart from a GS rendering library exporting symbol with the name of a
> well-known crypto function being a strange idea, who is at fault?
IMO, they're both at fault. To avoid this kind of problem, all global
symbols should be namespaced, so OpenSSL's SHA384_Update should really
be OpenSSL_SHA384_Update or similar, and GS's global symbol should be
GS_SHA384_Update or similar.
Main Index |
Thread Index |