Announcement

Collapse
No announcement yet.

AMD Energy Driver Booted From The Linux 5.13 Kernel

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

  • DanL
    replied
    Originally posted by patrakov View Post
    DKMS to the rescue.
    it87 all over again?

    Leave a comment:


  • milkylainen
    replied
    The end result is just stupid. Overly reactive devs.
    Sure, don't build it as default if you think it's that bad as a distro developer.
    But if _I_ need it and have no security issues on a closed system. I'd like to have an option to use it.
    This is just backwards.
    In that case we can disable all hardware support. Because most of them are going to be security-defunct in one way or another?

    Leave a comment:


  • patrakov
    replied
    DKMS to the rescue.

    Leave a comment:


  • loganj
    replied
    i'm not sure if i understand correctly
    they remove it because you needed root access to use it?
    if so whats wrong with that? there are tons of feature that needs root access on any OS. and not using it because you don't have root access will not make your linux work worse than not having it at all in the linux

    Leave a comment:


  • zxy_thf
    replied
    Originally posted by cb88 View Post

    They did ... and a few other things, but that also makes it less useful. This isn't hardware bug. Its a general problem that all CPUS will have as long as they happen to consume power when doing work, and also are capable of reporting that somewhat accurately. The problem is that power consumption stats... can be used to increase the strength of other attacks.
    The funny situation is, being precise is now considered as bugs by paranoids.
    Someday they're gonna welcome processors that randomly yield 3 when computing 1+1 in the name of security.

    Leave a comment:


  • zxy_thf
    replied
    Originally posted by bug77 View Post

    iotop is not in the kernel

    AMD has fixed their hardware "problems", I hope this frees them from upping their software game.
    iotop uses kernel interfaces, so you're right the ultimate solution is to chop off all APIs related to iotop from the kernel.

    Leave a comment:


  • cb88
    replied
    Originally posted by Alexmitter View Post
    I wonder why they did not think about slightly delaying the readout.
    To exploit the hardware issue after all, precise timing is needed and a short delay of the readout would make that impossible.

    But I have to agree, AMD should rather fix their hardware.
    They did ... and a few other things, but that also makes it less useful. This isn't hardware bug. Its a general problem that all CPUS will have as long as they happen to consume power when doing work, and also are capable of reporting that somewhat accurately. The problem is that power consumption stats... can be used to increase the strength of other attacks.

    Leave a comment:


  • Alexmitter
    replied
    I wonder why they did not think about slightly delaying the readout.
    To exploit the hardware issue after all, precise timing is needed and a short delay of the readout would make that impossible.

    But I have to agree, AMD should rather fix their hardware.

    Leave a comment:


  • Alexmitter
    replied
    Originally posted by zxy_thf View Post
    Long story short, if this person maintained any linux distribution, iotop would be removed from this distro's software repo.
    iotop is not part of the kernel.

    Leave a comment:


  • schmidtbag
    replied
    I can kinda see why the AMD engineers didn't agree to the suggestion. If you have the means to exploit the vulnerability this driver provides, you also probably have the means to exploit whatever is used to help slightly skew the results, making the "fix" moot.
    So what I want to know is, do you need this driver in order for the random number generation (or whatever the security feature is) to work? Because if you do, then removing this driver is pointless.

    Leave a comment:

Working...
X