Windows Internals

Question 1

Remote Procedure Call (RPC)

Answer 1

Microsoft Remote Procedure Call (RPC) is an interprocess communication (IPC) mechanism that enables data exchange and invocation of functionality residing in a different process. That process can be on the same computer, on the local area network (LAN), or across the Internet. The Microsoft RPC mechanism uses other IPC mechanisms, such as named pipes, NetBIOS, or Winsock, to establish communications between the client and the server. With RPC, essential program logic and related procedure code can exist on different computers, which is important for distributed applications. This section covers the architecture of RPC and the way in which RPC communication takes place.

http://technet.microsoft.com/fr-fr/library/cc738291(v=ws.10).aspx

Question 2

Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)

Answer 2

SPNEGO is the native Windows-to-Windows authentication service.

RFC : http://tools.ietf.org/html/rfc4178#section-1

Question 3

Secure Support Provider Interface (SSPI)

Answer 3

SSPI is a software interface. Distributed programming libraries such as RPC can use it for authenticated communications. One or more software modules provide the actual authentication capabilities. Each module, called a security support provider (SSP), is implemented as a dynamic link library (DLL). An SSP provides one or more security packages.

Question 4

ADVAPI32.DLL

KERNEL32.DLL

GDI32.DLL

USER32.DLL

NTDLL.DLL

Answer 4

rep

Question 5

Iterrupt Request (IRQ) / Iterrupt Request Level (IRQL)

Question 6

Advance Programmable Interrupt Controller (APIC)

Answer 6

rep

Question 7

Programmable Interrupt Controller (PIC)

Question 8

Advanced Configuration and Power Interface (ACPI)