User avatar
girl who fucks @i_lost_my_bagel@mastodon.lilysthings.org
2y
fun fact: if you have a laptop or desktop that has an intel cpu with "vPro" on the sticker there's a chance the management engine in your CPU is just hosting a web server at all times.

It's at port 16992
Browser open to localhost at port 16992. The page says "Intel Active Management Technology. Page Not Found. Web browser access to Intel Active Management Technology is disabled on this computer, or the page in the address bar is unavailable."
:drgn_heart@not.an.evilcyberhacker.net:1:neocat_0_0@shonk.phite.ro:1:neocat_googly_shocked@very.tastytea.de:1:neofox_googly_woozy@mk.absturztau.be:1❤1⭐9
11
27
2
14
User avatar
Sqaaakoi flagEnby​ @Sqaaakoi@wetdry.world
2y
@i_lost_my_bagel how the hell does that work in the OS? localhost should be handled by the OS, right? so how would that work
1
0
1
0
User avatar
Samuel Chase @samebchase@fantastic.earth
2y
@Sqaaakoi @i_lost_my_bagel Management Engine is essentially an entire OS (Minix) running /on/ the CPU.

So pretty much every computer out there is running two OSes at all times.
:drgn_heart@not.an.evilcyberhacker.net:1⭐1
1
0
0
2
User avatar
Sqaaakoi flagEnby​ @Sqaaakoi@wetdry.world
2y
@samebchase @i_lost_my_bagel Not what I asked. (I already knew what it was.) I am wondering how it manages to expose ports on the main system OS' localhost.
⭐1
1
0
1
1
User avatar
Latte macchiato blobcoffee ablobcat_longlong @privateger@plasmatrap.com
2y
@Sqaaakoi @samebchase @i_lost_my_bagel It doesn't. It uses the NIC directly (vPro devices have Intel NICs), none of this traffic will ever reach the main OS. It's entirely handled by the coprocessor.
:drgn_heart@not.an.evilcyberhacker.net:1
1
0
0
1
User avatar
Latte macchiato blobcoffee ablobcat_longlong @privateger@plasmatrap.com
2y
@Sqaaakoi @samebchase @i_lost_my_bagel However, loopback still uses the same NIC, so you can access it regardless.
⭐1
2
0
0
1
User avatar
[GRLC] ralseiblunt @novenary@akko.wtf
2y
@privateger @Sqaaakoi @i_lost_my_bagel @samebchase loopback is not supposed to hit any NICs though?
⭐1
1
0
0
1
User avatar
Latte macchiato blobcoffee ablobcat_longlong @privateger@plasmatrap.com
2y
@novenary @Sqaaakoi @i_lost_my_bagel @samebchase I may be stupid. ​:spinny_fox:​

vPro is going to run anyway. Some features of it are part of the ME, some are at user level.

If you hit on the OS loopback, there's probably something also running on your OS. Maybe a management daemon that comes installed? You'd be correct in that it doesn't use the NIC there.

The out of band stuff most people will be using vPro for though is part of the ME.
2
0
0
0
User avatar
[GRLC] ralseiblunt @novenary@akko.wtf
2y
@privateger @Sqaaakoi @i_lost_my_bagel @samebchase yeah the most likely explanation here is some kind of driver or userspace service is listening on the loopback interface

the remote administration stuff is there of course but I sure hope it's not exposed to the network by default ​:blobcat_daradara:​
❤1
1
0
0
1
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@novenary @privateger @Sqaaakoi @i_lost_my_bagel @samebchase it's not, at least on my home server, i had to enable it myself
⭐1
0
0
0
1