Announcement

Collapse
No announcement yet.

The UVD/UVD2 thread.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • crispy
    started a topic The UVD/UVD2 thread.

    The UVD/UVD2 thread.

    I make this thread with the intention of gathering information on the current state of usability of UVD and UVD2 in linux.

    I am a novice when it comes to understanding driver architecture and difficulties concerning them, so if anyone would like to give an introduction to why UVD / UVD2 as of now is not useable, it would be much appreaciated.

    I'll come with the first (obvious) update:

    In fact, the official release of Catalyst 8.10 doesn't have a whole lot worth talking about. It does have UVD Linux support enabled to accelerate video playback via the XvMC extension and their own HD video interface. However, all attempts at using XvMC with mplayer have failed thus far and AMD has been mum on how to actually use this feature. This looks like another feature we'll need to wait until Catalyst 8.11 to find out more.
    from: http://www.phoronix.com/scan.php?pag...item&px=Njc4OA

    ----------------------------------------------------------------

    Now for some of my own questions:

    1. Will it ever be possible to use this feature? Will I ever be able to make the GPU decode my x264 encoded material?

    2. How will programs make use of this feature?

    3. As video tearing is a common problem at the moment many people are using built in graphics or a nVidia add-on card instead (in case of for example a 780g chipset) - will it be possible to make use of UVD when you are using another video card?

    Hope these questions make even remotely sense for you guys!

  • Fixxer_Linux
    replied
    Hey guys, for cracking a code for accessing a system, the best way ever made is still to grab a gun and respectfully ask for the password !


    I'm kiding, but not so much. Kevin MITNICK said that the best way ever made was simply to phone and simply ask the password, letting the user believe that it's an IT support call and the password must be confirmed for checking purposes (or any other story that seems true to the employee)...

    Leave a comment:


  • Qaridarium
    replied
    Originally posted by bridgman View Post
    It's a good thing most companies require strong passwords these days, so users write their passwords down on yellow sticky notes or leave them in clear-text files on the PC.
    LOL :-) thats a nice idear.. to get a blueray key.

    Leave a comment:


  • Qaridarium
    replied
    Originally posted by nanonyme View Post
    Oh, cool. So it would take only 48247532784267608970568097787748983353656788171230 145158795634555590179630324741547659478604 years to crack an alphanumeric password with spaces with length 60 by bruteforce methods by your calculations with the grid you visioned. You, sir, are a genious.
    But! AES has known flaws....

    Leave a comment:


  • bridgman
    replied
    Originally posted by nanonyme View Post
    Btw, I expect you are aware of the fact that if there is indeed even a fraction of organized crime behind piracy like media industry claims, someone will eventually reverse-engineer the cards no matter how well the information is guarded.
    I agree completely. If we thought that cracking the graphics card DRM implementation was a viable approach for content piracy we probably would not have been able to provide much support for open source driver development in the first place. If you want to pirate protected media content there are easier ways to do it.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by bridgman View Post
    It's a good thing most companies require strong passwords these days, so users write their passwords down on yellow sticky notes or leave them in clear-text files on the PC.
    Btw, I expect you are aware of the fact that if there is indeed even a fraction of organized crime behind piracy like media industry claims, someone will eventually reverse-engineer the cards no matter how well the information is guarded.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by Qaridarium View Post
    but in AES there are known flaws!
    I read the section about cracking AES you read. The first one if I understood just related to factorization which is hard unless someone starts building powerful quantum computers. While my German lacks, I'd say for relative certainty that the German Wiki page says that the second approach is purely theoretical.
    I might quote this thing from English Wikipedia page on timing attack which the Wiki page you talked of mentioned as the latest approach on the problem http://en.wikipedia.org/wiki/Timing_attack
    "Timing attacks are easier to mount if the adversary knows the internals of the hardware implementation, and even more so, the crypto system in use. Since cryptographic security should never depend on the obscurity of either (see security through obscurity, specifically both Shannon's Maxim and Kerchoff's Law), resistance to timing attacks should not either. If nothing else, an exemplar can be purchased and reverse engineered. Timing attacks and other side-channel attacks may also be useful in identifying, or possibly reverse-engineering, a cryptographic algorithm used by some device."
    Meaning someone would need to purposefully reverse-engineer the AMD security implementation to get absolute certainty that the cracking would actually work indefinitely.
    This seems to be one of the reasons for why AMD is so cautious about giving out full hardware specifications of their cards.

    Leave a comment:


  • bridgman
    replied
    It's a good thing most companies require strong passwords these days, so users write their passwords down on yellow sticky notes or leave them in clear-text files on the PC.
    Last edited by bridgman; 04-23-2009, 10:34 AM.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by Qaridarium View Post
    600000000*365*24*60*60=1,89216^16 valid tests!
    Oh, cool. So it would take only 48247532784267608970568097787748983353656788171230 145158795634555590179630324741547659478604 years to crack an alphanumeric password with spaces with length 60 by bruteforce methods by your calculations with the grid you visioned. You, sir, are a genious.

    Leave a comment:


  • Qaridarium
    replied
    Originally posted by deanjo View Post
    That's right, and to top it off that Cuda cracker is only effective against extremely weak passwords.

    Another great breakdown of real numbers.
    my point is diverend...

    NOW we have 100 000 valid tests per second..

    in 2 monds we have 150 000 valid tests per second becourse of 6 core CPU's

    and 40nm GPUs...

    2010 we have 32nm 12 core CPUs and 32 nm GPUs

    then we have 300 000 valid tests per second per PC unit....

    so if we make a P2P cluster and 1000 Linux users help with 2 PC units...

    we have 1000*2*300000= 600000000 valid tests per second:..

    so we now do this 1 year:

    600000000*365*24*60*60=1,89216^16 valid tests!

    "Brute forcing a 256 bits cryptographic code without any known flaws "

    but in AES there are known flaws!
    Last edited by Qaridarium; 04-23-2009, 09:31 AM.

    Leave a comment:

Working...
X