AMD PR already contacted me to let me know they're working on an answer.
Announcement
Collapse
No announcement yet.
A Backdoor In AMD's Catalyst OpenCL Library?
Collapse
X
-
-
Originally posted by Michael View PostAMD PR already contacted me to let me know they're working on an answer.## VGA ##
AMD: X1950XTX, HD3870, HD5870
Intel: GMA45, HD3000 (Core i5 2500K)
Comment
-
Stallman was right
What if they have backdoors in the Firmware too? We need open devices, it's sad to see http://www.phoronix.com/scan.php?pag...tem&px=MTQ4MDU failed
Comment
-
Originally posted by BlackStar View PostCan someone please verify the existence of this string?
Not only does this make the Catalyst driver suspect, it also casts a shadow over the open-source driver. If you remember, AMD pushed *hard* to use a firmware blob in Radeon, instead of the clean-room approach of RadeonHD.
I used to think it didn't matter, but apparently I was naive. Luc Verhaegen was right all along.
Code:$ nm /usr/lib/libamdocl64.so | grep -i backdoor 000000000074dcf0 t osTestBackdoorATI
Comment
-
It's harder to put backdoors in the firmware and easier to spot compared to a whole driver. FOSS hardware it the next step of course but in the meantime I'm fine with FOSS drivers## VGA ##
AMD: X1950XTX, HD3870, HD5870
Intel: GMA45, HD3000 (Core i5 2500K)
Comment
-
Put my bet down for 'not actually a backdoor; humorously-named test function'.
If you were going to put a top-secret NSA backdoor into your driver, why would you give it such an obvious name? You'd call it osDefinitelyNotABackdoor instead, right?!
Comment
-
Originally posted by Kemosabe View PostLet me summarize:
I was considering moving away from Intel due to their allegiance to Microsoft.
Comment
Comment