`Hiding' libc symbols

[Daniel C. Sobral]

Jacques A. Vidrine wrote:
> On Tue, May 06, 2003 at 09:56:06AM +0200, Harti Brandt wrote:
> 
>>There is no guarantee that you 'fix' the port by hiding the symbol.  You
>>may as well break it. This depends on the function itself and on the
>>internal relationships in libc. You have to go through each individual
>>port and see what happens anyway.
> 
> 
> Please explain.  I _am_ guaranteed that keeping the port from hijacking
> strlcpy calls in libc will not break the port.  How could the port rely
> on the internals of libc?

Well... if I instrument all memory allocating functions (by providing my 
own copies) and I call a function that allocates memory by itself and 
expects my application to free that memory at some point, I expect the 
kernel to use one of my functions to do it.

-- 
Daniel C. Sobral
Gerência de Operações
Divisão de Comunicação de Dados
Coordenação de Segurança
VIVO Centro Oeste Norte
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail:	Daniel.Capo at tco.net.br
	Daniel.Sobral at tcoip.com.br
	dcs at tcoip.com.br