Page 1 of 4 123 ... LastLast
Results 1 to 10 of 59

Thread: A Backdoor In AMD's Catalyst OpenCL Library?

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,624

    Default A Backdoor In AMD's Catalyst OpenCL Library?

    Phoronix: A Backdoor In AMD's Catalyst OpenCL Library?

    There's a chance there might be a concealed backdoor within AMD's Catalyst driver, in particular within their closed-source graphics driver's OpenCL library...

    http://www.phoronix.com/vr.php?view=MTU2OTc

  2. #2
    Join Date
    Jan 2011
    Posts
    472

    Default

    I was considering buying an AMD mobo and cpu next upgrade as a means to step away from Intel. There goes that thought.

  3. #3
    Join Date
    Sep 2012
    Posts
    320

    Default

    AMD must be on of the the dumbest companies in the history. Not only having a backdoor but also labelling it backdoor is universally dumb.

  4. #4
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    543

    Default

    I'd say wait a bit. It's probably a funny name for some harmless debug hook.

  5. #5
    Join Date
    Apr 2010
    Posts
    87

    Default

    Well, either the most stupidly obvious back door code, or maybe exactly what it says: osTestBackdoor == API that bypasses the standard OpenCL APIs to do some form of testing of their OpenCL driver to check that it is interacting with local Operating System correctly.

  6. #6
    Join Date
    May 2012
    Posts
    944

    Default

    Quote Originally Posted by [Knuckles] View Post
    I'd say wait a bit. It's probably a funny name for some harmless debug hook.
    We'll get this type of explanation regardless of what it really does. That's what PR staff (and lawyers) are for - coming up with logically plausible bullshit.

  7. #7
    Join Date
    Sep 2013
    Posts
    248

    Default

    Quote Originally Posted by [Knuckles] View Post
    I'd say wait a bit. It's probably a funny name for some harmless debug hook.
    I'm betting on this too. If AMD really wanted to make a backdoor... do you really think they'd name it something as silly as "backdoor"? Plus, maybe it's a backdoor to other GPU features, not user-information.

    It's interesting how people blow stuff out of proportion without facts, but lets see what AMD's PR can come up with.

  8. #8
    Join Date
    Oct 2007
    Location
    Under the bridge
    Posts
    2,153

    Default

    Can 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.

  9. #9
    Join Date
    Sep 2007
    Posts
    365

    Default

    Quote Originally Posted by BlackStar View Post
    Can 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.
    I can confirm the existence:
    Code:
    $ nm /usr/lib/libamdocl64.so | grep -i backdoor
    000000000074dcf0 t osTestBackdoorATI
    Yet, who would lable a symbol for some backdoor "backdor"? This makes it to my list of the dumbest accusations I heard so far

  10. #10
    Join Date
    Nov 2012
    Posts
    206

    Default

    Quote Originally Posted by oleid View Post
    I can confirm the existence:
    Code:
    $ nm /usr/lib/libamdocl64.so | grep -i backdoor
    000000000074dcf0 t osTestBackdoorATI
    Yet, who would lable a symbol for some backdoor "backdor"? This makes it to my list of the dumbest accusations I heard so far
    Didn't Microsoft have a NSABackdoorKey in their strings at one point?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •