On 2001-09-23, Jean Francois Ortolo wrote:
>In this case, it's mysql, the client
>interface to the server mysqld. This mysql process makes an attempt to
>load the readline.so.4.1 library, then to use one of its functions (
>'readlixxxnternal_setup' as much as the error message said ). I can't
>understand how the mysql process could have been writing in the
>libreadline.so.4.1 file, from which its functionalities depend! That's not
>possible. Secondary, the mysqld process is not susceptible to change this
>library file. These packages are entirely separated from one another,
>there is no writing interaction between them.
Your thoughts go into the wrong direction IMO. What Martin has tried
to point out is that any process with sufficient capabilities could
modify the file. Just as it need not be the mysql process that has
damaged the library data on disk during dynamic linking, an intruder
damaging only libreadline doesn't sound plausible. It is likely that
any kind of hardware or software failure has been the cause of it.
Imagine physical harddisk malfunction due to dust, heat, or shock,
when reading or writing back parts of the disk. Imagine timing
problems, UDMA trouble, minor hardware instability, whatever. Keep
an eye on any other such "modifications".
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
