BrainDump
  Home arrow BrainDump arrow Page 2 - Windows XP Startup Methods
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
BRAINDUMP

Windows XP Startup Methods
By: Nilpo/Developer Shed Staff Writer
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 3 stars3 stars3 stars3 stars3 stars / 5
    2007-05-02

    Table of Contents:
  • Windows XP Startup Methods
  • Startup Registry Keys
  • Startup Folders
  • Startup Files

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Windows XP Startup Methods - Startup Registry Keys


    (Page 2 of 4 )

    There are far too many startup registry keys to cover in this article.  I’m only going to focus on the most commonly used and exploited ones.  You can find links to more information at the end of this article.

    The most common of these registry keys are the ones commonly referred to as the Run Keys.  These are keys specifically used to schedule program startup.  There are three sets of them: one under the HKEY_LOCAL_MACHINE root, another under HKEY_CURRENT_USER, and the last under HKEY_USERS.

    HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRun
    HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRunOnce
    HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRunServices
    HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersion
    RunServicesOnce


    HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRun
    HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRunOnce
    HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRunOnce
    Setup


    HKEY_USERS.DefaultSoftwareMicrosoftWindowsCurrentVersionRun
    HKEY_USERS.DefaultSoftwareMicrosoftWindowsCurrentVersionRunOnce

    The keys under HKEY_LOCAL_MACHINE are executed regardless of who logs on to the computer.  These are system-wide startup settings.  HKEY_CURRENT_USER houses the settings specific to the currently logged on user and HKEY_USERS houses each user profile.

    The Run keys execute processes at every startup.  The RunOnce keys are only executed once and then deleted upon successful execution.  The same is true for the RunServices and RunServicesOnce keys except that they are executed as system services instead.

    One commonly exploited key is the one seen below.  Specifically, its Shell value is responsible for identifying the executable that starts the system shell, namely Explorer.exe.  However, this key can be changed to execute unwanted programs unbeknownst to the user.

    HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionWinlogon

    The Winlogon process is responsible for much of Windows startup.  It provides the user login system as well as starting the Windows environment.  There are two other common locations used to exploit this process as well.

    HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionWinlogonUserinit

    HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionWinlogonNotify

    The first is a value that contains another setting used internally by Windows and should never be changed from its default.

    The second is ended for use by Winlogon Notification Packages. These are programs designed to perform certain actions when Winlogon events, such as Logon or Logoff, are triggered.  Placing a harmful executable in this key will cause the exploit code to be executed every time one of these events occurs.

    As much as I would love to be complete, there are far too many of these to cover in this article.  Please read the links provided for more information.  If you have questions about specific keys or their intended purpose, please post those questions in this article’s blog.

    More BrainDump Articles
    More By Nilpo/Developer Shed Staff Writer


       · In this article we take a look at some of the more common ways of starting programs...
     

    BRAINDUMP ARTICLES

    - Internet Explorer 8 Review
    - Nilpo`s Top Windows Add-Ons
    - Beginning Silverlight 2.0 Development using ...
    - Fixing Vista`s Troubles
    - Preparing Windows Images for Mass Deployment
    - The Trouble With Vista
    - Slipstreamed and Unattended Windows Installa...
    - Microsoft Office SharePoint Server
    - Microsoft Office SharePoint Designer
    - Microsoft Windows SharePoint Services 3.0
    - Microsoft Live Mesh Overview
    - XAML Brushes and Silverlight
    - Silverlight and XAML Basics
    - Immortal XP
    - XAML Basics





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway
    Stay green...Green IT