Finally, updated the RCE article on AMD K7 undocumented debug extensions... nearly 4 years belated due to real life not so happy events..

http://www.woodmann.com/collaborative/knowledge/Super-secret_debug_capabilities_of_AMD_processors_!

(Note: the final ! is part of the URL)

This new version has corrected a couple errors, been made shorter and, hopefully, clearer !

keeping it secret for so long

i wonder how deep this really goes no1 really can know out of the "billions of transitors on the cpu" if theres more hidden things inside like a spyware for goverments like NSA and things

while many things are known to people on this forum like mac address (it basicly has no real use on the tcp header if you look closely), hardware ids like disk/board/specific hardware (i mean hardware guids or specific I/O musters), bios id , cpu id , cookies or serials numbers other other GUIDīs, tracing (via ip) ect.

they do even more things like catching mails, logging handy talking + actual position of the handy , sms , loggin almost all online chats/forums/facebook/chatprograms ect., sending information before searching like google does

in combination it should be easy to identify a person

for example lets say they make a trace of a ip and find out where it was from they also can read the mac address to identify the computer

its not new stuff its rather used malicious and a lot is avoidable

Wow, so much ignorance in a single post. Guessing you're just trolling and not being serious, but just in case...

The MAC address is not part of the TCP header, it's part of the 802.3 Ethernet header or 802.11 WLAN header. And for both cases, it most certainly has a real use.

CPU IDs identify the processor architecture, so yes, they're important. And they're not GUIDs so they can't be used for tracking purposes.

As for cookies... it's 2014 and you really don't understand why they're useful on certain sites?

And good luck finding the MAC address for a computer just based on a trace of its IP address

maybe the sneaky spyware propagandist comes out now ?

so tell me what happens if the mac address is just removed and what is NOT doable without it

cpuid ? i wonder why you need this but i remember they added the cpuid
in case cpuid was not part of old cpus and the argument was to find out faked hardware
again it leads me to the question why we have model specific registers and such theres no need of a ID what can very limit the current computer
http://en.wikipedia.org/wiki/Model-specific_register

yes indeed we have 2014 i wonder what really changed of the cookie use but we all know what it was for dont we ?

If you spoof your MAC address in your outgoing packets, then the server (typically a router) with which you're communicating via Ethernet/Wifi will respond to those packets with the spoofed address as the destination, which your kernel will drop when it sees them, thus preventing you from using any connection-based protocols. And changing your MAC address on the host won't have much effect since the remote server with which your communicating never sees your host MAC address anyway unless its on your local LAN.


It was for tracking session states, and that's how it's still used by most websites.

i totally agree with the cookie part i wasnt sure into like it isnt used anymore in 2014 or something like that

im not sure what you mean with the "host/lan part" raw packets also show mac addresses for the target

i dont know all the RFC protocols what protocols are effected ?
http://www.ietf.org/rfc/rfc2616.txt

the proof and change is nothing for the casual user who dont know it exits what i meant if you need an identifier a mac address can be changed/spoofed a software identifier what is send is even more secure

about the cpuid i question the Vendor ID
http://en.wikipedia.org/wiki/CPUID