25-Apr-2024 13:14 GMT.
UNDER CONSTRUCTION
Anonymous, there are 159 items in your selection (but only 9 shown due to limitation) [1 - 50] [51 - 100] [101 - 150] [151 - 159]
[News] Offensive Elbox driver and consequences for PoseidonANN.lu
Posted on 14-Nov-2002 14:43 GMT by Chris Hodges159 comments
View flat
View list
Poseidon will refuse to load the usb.device with the next update. I could verify that the offensive RDB-killer code is inside the driver version (1.2) I had here. Permission to distribute Poseidon with their software has been withdrawn. Dear Poseidon Users,

in the last few days, there were rumours posted to ann.lu, claiming that the usb.device, that is provided by Elbox Computer Inc. for the Spider USB PCI card would contain malicious code. This code was posted disassembled on various websites. This source code, if assemblied into an executable, would indeed have the ability to kill the RDB (if it was found in block 0). Code destroying data on purpose like this is illegal in most countries (including Germany) and moreover, is one of the ethically worst things I've ever seen.

As the source of this security warning was an anonymous poster and therefore was not reliable, I wanted to check for myself. So I loaded the usb.device (some friendly Mediator user sent me, as Elbox never offered me a SpiderCD to check the contents of the CD), let it decrypt itself and just searched for the 'RDSK' string in the driver (as seen on the disassembled source code on the websites). No disassembly was used. The string was found. I could therefore verify that the offensive code is at least in version 1.2 of the device, I had here to test (there is absolutely NO reason why 'RDSK' would appear in an usb hardware device driver).

I gave Elbox the chance to clear things up in public by posting an apology and removing the code. They didn't. Instead, they said that all my "doubts" would be answered in the press statement released yesterday and ignored the consequences that I already had proposed to them.

Well, my "doubts", which actually are facts, that I could see with my own eyes, remain. Any Mediator user can check this by using a memory monitor and searching for the usb.device in memory (after loading up Poseidon) and see, if there's the 'RDSK' ID string within the next 10000 bytes.

As a consequence, I have to warn Mediator users that their machine is in danger, when running the usb.device. In the non-memory protected Amiga environment it might get damaged at any time and then cause the routine that kills the RDB to become active. The next update of Poseidon will refuse to load up the usb.device, if it detects malicious code. This is to protect yourself from damage and myself from being held liable for any loss of data or damage done.

Moreover, I hereby withdraw the permission to include Poseidon in ELBOX's software distributions, until they
a) admit, that the code was in their driver,
b) admit, that they have constantly lied to the users,
d) have placed a public apology for the first time in their life,
c) and have removed any malicious code.

I don't want Poseidon to be included with third party software, that's highly illegal and whose originators don't deserve any trust.

I do understand that people try to protect their work from being hacked. I do this too, but not by risking the data of legal users and I cannot tolerate this offensive behaviour any longer (I admit, I'm again rather upset and therefore this statement is not as objective as it could have been).

The Spider users out there are adviced to confront Elbox with the demands mentioned above, so to allow Poseidon again accept the usb.device driver.

I hope that you believe the facts and my worries and understand the steps taken.

Best regards

Chris Hodges

Offensive Elbox driver and consequences for Poseidon : Comment 151 of 159ANN.lu
Posted by Paul Maric on 15-Nov-2002 19:42 GMT
In reply to Comment 139 (Peter Gordon):
>Oh no, it wasn't that quote that mentioned the decryption, but theres nothing >to suggest the person did more than search for "RDSK" in the 1.10 binary, >which still proves nothing.
Yes, that's why I suggested someone else with the proper know-how should have a look at the v1.10 driver.
Offensive Elbox driver and consequences for Poseidon : Comment 152 of 159ANN.lu
Posted by Paul Maric on 15-Nov-2002 19:50 GMT
In reply to Comment 151 (Paul Maric):
Nevermind.... just read in the KDH-thread that spider drivers v1.9 and v1.10 are clean. So I guess we'll be seeing some other Elbox driver updates soon, eh? (pci.library and whatever other drivers they've put evil code in).
Offensive Elbox driver and consequences for Poseidon : Comment 153 of 159ANN.lu
Posted by RealHomer on 15-Nov-2002 20:35 GMT
In reply to Comment 145 (shocked):
>I bought a way, very very old PowerMac 6100 secondhand, and it FLOORED me
Huh!!? I have a PowerMac 6100 and it is and always has been a pile, ever heard of the term Road Apple? I would trade the 6100 for any Amiga any day.
Offensive Elbox driver and consequences for Poseidon : Comment 154 of 159ANN.lu
Posted by Alkis Tsapanidis on 15-Nov-2002 20:42 GMT
In reply to Comment 149 (redrumloa):
Not that the FM801 driver WORKS on G-Rex 1200:))) It disables parity checking.
Offensive Elbox driver and consequences for Poseidon : Comment 155 of 159ANN.lu
Posted by Kaminari on 15-Nov-2002 21:03 GMT
In reply to Comment 6 (quenthal):
Some people are obviously still believing hard that Mediators and SharkPPC will be supported by AmigaOS 4. You should read Amiga & Hyperion's executive updates more thoroughly. Elbox hardware will NOT be supported by Hyperion since the former is not willing to acquire any OS license from the latter. Of course Elbox could decide to hack the OS and make it run on their hardware (like they did with Picasso 96), but they'd be in serious trouble then.
I'm just reporting the legal fact here. I actually don't care a peanut whether OS 4 will run on their piece of junk or not. The only device I bought from Elbox was the Mroocheck adapter, and I'm still regretting it (and yes, I know how to read a doc, even one written in bad English).
If you want to deal with a GOOD Polish company, go the Matay way.
Offensive Elbox driver and consequences for Poseidon : Comment 156 of 159ANN.lu
Posted by strobe on 15-Nov-2002 23:23 GMT
In reply to Comment 153 (RealHomer):
Speaking of the 6100...
When the first PowerMacs came out, all the smart Mac users kept buying 68k-based Macs. The first PowerMacs were just plain slow and didn't even support old features like soft power (a sign of a rushed job imho). The main reasons it was slow were:
1) The PPC 601 was the first so-called "PowerPC" consumer-based CPU which had too many transistors (legacy POWER crap so compilers wouldn't have to be rewritten completely) so it ran hot+slow.
2) MacOS 7.5.x was mostly 68k running under emulation plus it was buggy as hell. Smart users tuck with 68k macs using 7.1 which needed only 800k of memory, 7.5 required 5MB (ouch). The whole PowerPC transition was a pain in the ass despite the fact that MacOS had good API abstraction.
The only people who found the first PowerMacs immediately useful were those who had specific PowerPC "accelerated" apps which had some PowerPC code fragments.
However about a year ago I got a 6100/AV second hand and it runs pretty well. System 8.6 is nearly completely PowerPC native and runs well on a 60mhz 601 provided you have plenty of RAM (which can be difficult since the 6100 has two slots of interleaved 72pin SIMM RAM, so they have to be matched). So amazingly my second impression is better than my first.
[Fair warning for early adopters of an emulated OS. At least one aspect of MorphOS on paper I like is the 3.x compatible libraries are PowerPC native]
Offensive Elbox driver and consequences for Poseidon : Comment 157 of 159ANN.lu
Posted by Matthew Garrett on 16-Nov-2002 17:54 GMT
In reply to Comment 147 (AdmV):
You don't have to. In the case of a civil case in UK law, the only concern is balance of probabilities (My RDB is overwritten with random data.There's code on the system that's intended to overwrite the RDB with random data. What's the most likely cause of my loss?). In the case of a criminal prosecution, there's no need for anyone to have lost data - the mere presence of the code is illegal under the Computer Misuse Act. It's pretty easy to prove that the code is there.
Offensive Elbox driver and consequences for Poseidon : Comment 158 of 159ANN.lu
Posted by Ik_Master on 18-Nov-2002 21:29 GMT
I agree with elbox ....
Offensive Elbox driver and consequences for Poseidon : Comment 159 of 159ANN.lu
Posted by T_Bone on 06-Nov-2003 08:55 GMT
hello old thread... just thought I'd visit, long time no see
Anonymous, there are 159 items in your selection (but only 9 shown due to limitation) [1 - 50] [51 - 100] [101 - 150] [151 - 159]
Back to Top