You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your excellent copy of the tool said that there where no such device: /dev/mei
Checking the /dev there was a mei0 and I figured that had to be it on my system.
Changed compiled and it seemed perfect.
I looked at a official Intel Release tool to see if my system is vulnerable to SA-00086 as it should be, and in their python code they check for DEF_DEV_NAMES = ["mei0", "mei", "mei1", "mei2", "mei3"]
I know you just made a tool based on the fpt tool, but I just wanted to share this incase the tool could in time be modified to include these or anyone reading know why it's may not work on their system.
The text was updated successfully, but these errors were encountered:
This simple program I made 5 or 6 years ago to not depend on fpt because it's absent for linux
Now I prefer to use me_cleaner. Once patched ME is gone forever.
I did what you requested. Now it searches for multiple device names
I wanted to test this on a board I had on the shelf to better understand IME: http://www.asrock.com/MB/Intel/J3455M/index.asp. Running Ubuntu 18.04.2
Your excellent copy of the tool said that there where no such device: /dev/mei
Checking the /dev there was a mei0 and I figured that had to be it on my system.
Changed compiled and it seemed perfect.
I looked at a official Intel Release tool to see if my system is vulnerable to SA-00086 as it should be, and in their python code they check for DEF_DEV_NAMES = ["mei0", "mei", "mei1", "mei2", "mei3"]
I know you just made a tool based on the fpt tool, but I just wanted to share this incase the tool could in time be modified to include these or anyone reading know why it's may not work on their system.
The text was updated successfully, but these errors were encountered: