In the interview of Maciej Binek, President, Elbox Computer, Elbox denies any existence of RDB trashing code.
RS: Rafal Sanda, ACP Interviewer
MB: Maciej Binek, President, Elbox Computer
SR: Is it true that your drivers had code erasing the RDB?
MB: No, our drivers never included code aimed at erasing RDB.
Erasing RDB by a cracker (if it had happened at all: you see, no-one
contacted us on this issue) could only result from operating code created by
the cracker from modification of our software.
It is obvious that we cannot be responsible for effects of software
resulting from illegal modification of our software code.
--
pci.library before version 5.9 was confirmed to contain the RDB trashing routine, by several independent sources.
Please feel free to check the claim by using elboxdecrypt on pci.library earlier than 5.9.
Anyone with basic programming skills can see that the elboxdecrypt is not adding anything to the resulting decrypted binary. Someone with more skills can tell you that the routine is not "creating" anything, it is merely performing the decryption process that is done each time the library is initialized. So the RDB trashing code is always present in memory if the pre-5.9 pci.library is loaded.
| 