深入研究Windows内部原理系列_电脑技术.ppt

? 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. * * * * * * * Session 0 Isolation Before, the console user ran in session 0 Names created by console user could collide with service and system object names Services that presented windows on the console could open the door for privilege elevation (“shatter” attacks) Session 1 ApplicationD ApplicationE ApplicationF Session 0 Service A Service B Service C ApplicationB ApplicationA ApplicationC Session 0 Isolation In Windows Vista, the console user starts in session 1 and cannot connect to session 0 Eliminates name collisions Poorly written services can’t display windows to the user Session 1 ApplicationA ApplicationB ApplicationC Session 0 Service A Service B Service C Session 2 ApplicationD ApplicationE ApplicationF Interactive Logon Architecture Credential Providers replace GINAs Plug into Logonui.exe Easier to write than GINAs Multiple concurrent providers are supported User selected or event driven Used to capture elevation credentials Inbox Credential providers: Password Smartcard WinLogon LogonUI Credential Provider 1 Credential Provider 2 Credential Provider 3 Delayed Auto Start Services Before, autostart services could severely impact login performance In Windows Vista, services can request delayed autostart Set by new ChangeServiceConfig2 API Stores new DelayedAutoStart value in service Registry key Service Control Manager (SCM) starts these services after the automatic start services I/O priority set to Very Low during startup Services configured this way include BITS, Windows Update client, Ehome… Clean Service Shutdown Before, services had no way to extend the time allowed for shutdown After a fixed timeout (default 20 seconds), SCM was killed and system halted (while services were running) This was a problem for services that needed to flush data In Windows Vista, se