Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Windbg - Symbol _TCP_ENDPOINT not found
Itistimetosleep
Member Posts: 3
I've been reading "The art of memory forensics", on chapter 11 page 327 they added the output of Windbg dt(_TCP_ENDPOINT)
I have been trying to get the same result with Windbg but I keep getting the same error -
dt(_TCP_ENDPOINT) Symbol _TCP_ENDPOINT not found.
even though I loaded the tcpip.sys symbols file
1: kd> lml start end module name ....... fffff8053bfc0000 fffff8053c2a9000 tcpip (pdb symbols) C:\ProgramData\Dbg\sym\tcpip.pdb\4EF7BCB071F28E1DAAAA937D59B39D121\tcpip.pdb
I dont get this kind of error when looking other Kernel structures,
1: kd> dt(_EPROCESS) ntdll!_EPROCESS +0x000 Pcb : _KPROCESS +0x2e0 ProcessLock : _EX_PUSH_LOCK ......
What am I doing wrong?
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
| Writing WDF Drivers | 7 Dec 2020 | LIVE ONLINE |
| Internals & Software Drivers | 25 Jan 2021 | LIVE ONLINE |
| Developing Minifilters | 8 March 2021 | LIVE ONLINE |
Comments
That book was written in 2005, right? Things have changed, systems get redesigned. Perhaps that structure is no longer used.
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.
Hey, The book was written in 2014 and they were referring to a structure that exists in windows 7.
so initially I thought that was the case, but when I looked into the plugin source code, I saw that they were using the same names.
This plugin ran perfectly on a similar crash dump of Windows 10.
Github source code - https://github.com/volatilityfoundation/volatility3/blob/master/volatility/framework/plugins/windows/netscan.py
Thanks,
It was a stupid mistake,
The output in the book was from the dt() command from the volshell plugin in volatility 2.7, not Windbg.
_TCP_ENDPOINT is an overlay used by Volatility -
http://axlotldunktank.blogspot.com/p/volshell.html