Видео

1:15:24 the dude falls asleep after listening to Windows Internals for an hour.... I know that feeling.

Very insightful as per security perspectrive.. well done @jasmine rice !

Thanks for sharing!

Potentially not bad presentation but the only way to listen is 1.5x original speed, still painfull "um um um" omg 52:00 defined in PATH by user, nothing said about protection UAC etc, system\drivers directory, services, syswo64 (32 bit dll) and system32 directory (64 bit dlls) lot about slashes backslashes.. sorry but its waste of time

love this!

6 years from now, the content concept is still relevant. Great presentation, thanks a lot!

Саня, можно было и на русском) Зачем выпендриваться

what should i have prior knowledge of before watching this video, cz i did not fully understand and i am a new student(first year ) but i do look to know what should i learn before jumping into windows architecture

Alternate Data Streams are fascinating! I wonder what some legitimate use cases are for them

8:54 I couldn't quite catch the name of the case that he mentioned which caused the release of several Native API documentations. Does anyone know that case?

Impressive

A bit mundane but with good explanation. Thanks!

thank for this content :D

This video taught me a lot about the NT Kernel Interface and I am grateful for that. Despite that, certain people will always find ways to be jackasses about it in the comment section. You do you, Mr. Sotirov, and thank you for the knowledge.

The fluctuations in voice making uncomfortable 😣

MyProgressTime 8:00

I was hoping this would be about the Windows 9x kernel

Great talk! One clarification for confusion at 1:11:05 It's file.txt::$DATA (2 colons) and file.txt:$FOO (1 colon) Also, command "type" will not read it, notepad.exe will.

Python program install by dafault user/vendor/appdata/.. which doesn't required any special permission . Interfer with doesn't required any special permission

Is the content of this talk still relevant today, particularly in regards to security?

I expected some Memory Management and other operating functionalities because of the title of the video, this was more of security related stuff, how windows can be vulnerable through different mediums, Nevermind, Got to learn something new.

You need to breathe man.

"Focus" Pronounced: Fow-kus Not: Fockus

What inbred thought I would want to load the DLL from the same folder as some random shortcut? Welcome to Windows NT. Population: misguided clusterf***

Windows Rocks

It's like he's not breathing while talking.

Windows is not bad, it's just too different from UNIX and costly to experience.

Thanks a lot @Jasmine Rice for sharing this, this is simply amazing. Always love Sotirov's presentations!

The linux kernel’s userspace interface is not stable. He’s confusing glibc and the kernel. Which btw is also not stable between versions.

He's using an overhead projector! Was this recorded in the 90's?

Anything wrong with the throat? Just wondering

12:25 this is impressive, but Linux was always designed to not only allow easy cross compilation between architectures so they can "use each others code", but is always inherently designed to run on anything. Windows OS internals is just slow experiments in realizing the Linux people know their shit better.

12:30 its functions are not as easy to use? WTF does that mean? its code, you call the code because it does a thing. OR we don't know what it does and we are not allowed to know, or make it simpler to know.

11:45 why is NTDLL not documented? Because MS is dumb and doesn't realize the value of documentation - that's why.

This video is very interesting! I tried in command prompt (Win10), the syntax should be: - To save to data stream with customized name: "type C:\Windows otepad.exe > D:\1.txt:test" (single colon) - To save in default data stream: "type C:\Windows otepad.exe > D:\1.txt::$DATA" (double colon) :)

I don't think it was recorded in 2017. It's a pretty old but good stuff. I also wish that lecturers like that besides pointing out the bad ways of doing things immediately followed up with a good example of how its recommended to do things. Otherwise everyone gets scared by a bad example but don't learn the good way.

Great talk, thanks so much!

Thnx :)