Skip navigation.

exploreopera

| Help

Sign up | Help

Penguin Stumblings

Here There Everywhere and Back to Nowhere...

Posts tagged with "Computer Help"

Create an Indestructible Shared PC

, ,

By Neil J. Rubenking

Need to put a PC in a public place? A free Microsoft tool makes it easy to lock down.

Schools, libraries, and other organizations often want to make computers available in public places. These can become tempting targets for hackers. Even well-intentioned users can wreak havoc by deleting important files or accidentally installing malware.


Microsoft's free Shared Computer Toolkit lets you configure a PC that can be used to search the Internet, look up resources, and run approved programs; it also stops users from making permanent system changes, running arbitrary programs, or introducing malware. Administrators on domain-based PCs have long been able to do this; the toolkit offers a similar level for any PC. You don't need an IT degree—the kit leads an administrator through the steps of locking down a system.

We evaluated a recent release candidate of the toolkit, which can be downloaded at www.microsoft.com/sharedaccess. The toolkit requires Windows XP Service Pack 2 or Windows XP Tablet PC Edition 2005, and you'll probably need to download the oddly named User Profile Hive Cleanup Service. Start by installing the toolkit while logged on to an account that will become the toolkit administrator account. It will open a Getting Started applet that lists the steps you'll follow to lock down the computer.

The first step is usually to adjust the disk's partitioning to make room for Windows Disk Protection. WDP requires a region of unallocated disk space that is located just beyond the boot partition and whose size is at least 10 percent of the boot partition's size but no less than 1 GB. Windows doesn't provide a nondestructive partition management utility; the toolkit suggests using PartitionMagic 8 or Terabyte Unlimited's BootIt. If you're configuring a new computer, you can adjust the partition size during installation of Windows XP. When active, WDP discards all changes to the boot partition when the computer is restarted, so you won't turn it on until the other configuration steps are completed.

The second step pulls together a number of security settings and suggests you enable them all. One key option removes the toolkit administrator account from the Welcome screen—users won't know the account name, much less the password. As the administrator, you'll log in by pressing Ctrl-Alt-Del twice at the Welcome screen, then entering the account name and password in the dialog box. Among other restrictions, the toolkit can prevent other users from shutting down or restarting the computer, block Windows from caching Passport or other credentials, and disallow unapproved user profiles. The Test Your Password button checks to be sure you haven't used a blank password or a weak password like your username.

Next you'll create a public account to be shared by all walk-up users. (You can make multiple accounts by repeating the next few steps.) The instructions advise making it a Limited account, but there are also instructions for dealing with an Administrative account, in case a critical program won't run under a Limited one. For the setup, you should set a password for this account, or else Windows will boot to it on each restart, forcing you to log off and then into the toolkit administrator account. Next, the wizard asks you to log on to this new account and configure it completely, including setting appearance, configuring the printer, enabling the Quick Launch toolbar (if desired), and setting up programs such as Microsoft Office that perform user-specific initialization. Be sure to install add-ons like Adobe Reader and Flash. Now log off the public account and back into the toolkit administrator account.

In the wizard, the User Restrictions applet offers a range of limitations from mild to draconian. The Lock This Profile check box tells the system not to save Internet history and other user changes. You can force a specific home page and limit which drives are displayed in My Computer in order to block the user from bringing in software on diskette or USB key. You can configure this profile to log off after a specified amount of time, or of idle time. And you can set it to restart at log-off; this is significant when WDP is enabled, because restarting discards all changes to the Windows partition.

Checking the Recommended Restrictions box really locks down the system. Start menu restrictions eliminate many icons such as Control Panel and My Network Places, force the classic Start menu style, and disable right-clicking on Start menu items. General XP restrictions eliminate the Recycle Bin (so one user can't paw through another's trash), block access to such tools as the Command Prompt, Registry Editor, and Microsoft Management Console, and prevent activating Task Manager to kill specific processes. Internet Explorer restrictions disable right-clicking within IE, block access to Internet Options, and suppress certain toolbar buttons. Office restrictions disable macros and VBA and prevent other inappropriate changes. The Software Restriction Policy blocks all programs not found in the Windows or Program Files folder and prevents use of tools that could bypass the toolkit's security.

You can go even further. You can block Internet access for the account, prevent IE or Windows Messenger from running, or disable Microsoft Office. And you can disconnect this account from the All Users account, so the only items on the Start menu are those specifically installed for this user.

Next the wizard asks you to test the account and make sure it's not so restricted as to be unusable. You'll find it a novel experience. Most of the right-click menus are disabled. You can't launch a Command Prompt or enter a program name in the Run dialog. You can't change the wallpaper or set the clock. All you can do is run the programs listed in the Start menu or log off. Do run all the programs to be sure they work.

Now, log back on as administrator; you'll have to press Ctrl-Alt-Del twice. Turn on Windows Disk Protection. When WDP is active, it takes control of all programmatic requests to read or write data to the Windows drive. The write requests are trapped and stored without changing the drive itself. For read requests, WDP reads from the physical drive, then applies any modifications based on those stored write requests.

The technique of inserting a layer between the system and the physical disk is used by other products, like Altiris Protect and ShadowUser. While WDP doesn't have all the flexibility of these programs, it has a nice feature they lack: It automates Windows Update installation. At the scheduled time, it will restart the computer to discard changes, run Windows Update, commit those changes to the physical hard disk, and restart with WDP protection active. You can also run a script to update your antivirus program during this process.

Once WDP is active, all changes, even those made under the toolkit administrator account, are discarded by default when you restart the computer. You get one warning about this, at the time you turn WDP on. After making configuration changes, you must set WDP to save changes on the next restart. It will commit your changes to disk and return to the default of discarding changes. You can also set it to retain all changes until actively placed back in the protection mode. Note that WDP protects only the boot partition (the one containing the Windows folder) and that it disables hibernation.


The system is now ready for public use. The shared public account is locked down so users can do only what you've allowed them to do. And the system is automatically wiped clean at each restart. You'll want to read the security advice in the Shared Computer Toolkit Handbook—in particular, to create a strong password for the powerful toolkit admin-istrator account.

If you decide to uninstall the toolkit, you'll want to be very careful. Many of its restrictions are simply existing features of Windows, brought together for convenience. The settings will remain even if the toolkit is removed. Before uninstalling, you must work backwards through the steps in the Getting Started applet, turning off WDP and undoing the restrictions for all accounts. Only then can you safely uninstall.

You might think it would be easier to uninstall the toolkit by restoring an earlier drive-image backup, but even here you need to act with care. WDP uses a nonstandard configuration for both the main partition and its data storage partition. If your drive-imaging tool supports it, you'd have to delete both partitions and restore the image into the resulting free space. You'd also have to configure the tool to restore the Master Boot Record and mark the restored partition as active.

We applaud Microsoft for making this security tool available. It should be a godsend for schools, libraries, and other havens of public computers.

Source: http://www.pcmag.com/article2/0,1895,1892666,00.asp

Examine e-mail headers to determine their real origin

, ,

by Jonathan Yarden

Takeaway:
E-mail forgeries are becoming more difficult to identify, but learning how to examine e-mail headers can help you separate the good from the bad. In this edition of Internet Security Focus, Jonathan Yarden tells you how.

In previous columns, I've mentioned that it's possible to identify forged e-mail by reading the e-mail headers. This generated a lot of feedback, mostly from readers wanting to know how to do it.

E-mail headers, as a topic for Internet security, aren't as exciting as an exploit or the latest Internet worm. But learning how to quickly determine the authenticity of e-mail is important—especially if someone is abusing an open SMTP relay on your network.

I remember when forging e-mail was unthinkable. Now, I get so many forged e-mails that I hardly consider any subject to be valid unless I know the sender personally—with the exception of forged e-mails that claim to have come from my own e-mail account. There's nothing that can stop people from manipulating e-mail headers, and they're generally not verifiable unless you understand how to read them.

When you receive a letter via postal mail, it has a postmark. If e-mail followed the same logic, you'd be able to see where the message originated before you opened it. Encrypted e-mails are the exception to this rule, but the vast majority of e-mail travels as clear text.

While e-mail headers show the path the message took in reverse order, this doesn't conclusively identify the e-mail as genuine and sourced from the specified sender. It's no surprise that thousands of e-mail plagues continue to eat bandwidth and infest the Internet.

Every e-mail program that I've seen can display message headers. How you view the headers depends on the program that you use.

You can toggle some programs, such as Mutt (the UNIX console e-mail program), to always show e-mail headers. In Mutt, simply press the [H] key to toggle the display of message headers.

To display e-mail headers in Microsoft Outlook, right-click a message, choose Options, and scroll through the Internet Headers section that's located at the bottom of the Options dialog box. For Outlook Express, right-click the e-mail, select Properties, and choose the Details tab. If you use a different e-mail program, the Help file should provide adequate instructions.

Here are the actual headers from a forged unsolicited commercial e-mail (UCE) that I received in one of my e-mail accounts. The only thing I've altered is my actual e-mail account to somebody@someplace.com:

From collegebabe@aol.com Mon Mar 27 16:54:12 2006
Return-Path: collegebabe@aol.com
Received: from trademeca.co.kr (unknown [211.219.20.86])
by mail.someplace.com (Postfix) with SMTP id 2304964253A
for ; Mon, 27 Mar 2006 16:54:10 -0500 (EST)
Received: from smtp0422.mail.yahoo.com (80.237.200.67)
by trademeca.co.kr (211.219.20.86) with [Nmail V3.1 20010905(S)]
for from ;
Thu, 23 Mar 2006 15:55:00 +0900
Date: Thu, 23 Mar 2006 11:34:52 GMT
From: "Prendawen" collegebabe@aol.com
Subject: Hey buddie! What's going on?
The Received: headers tell the real story of this poor forgery, but you have to examine several of these to truly understand the details. This particular e-mail is identifiable because it doesn't make any sense for a person with an AOL account to use one of Yahoo's e-mail servers to relay e-mail through a server in the .kr top-level domain, which is Korea.

Furthermore, a DNS lookup failed to find smtp0422.mail.yahoo.com, so this IP address doesn't exist. Even if it did, the IP address 80.237.200.67 belongs to a network in Germany, which I discovered by checking the online American Registry for Internet Numbers (ARIN) database. So don't waste your time sending a nasty reply, because chances are that collegebabe@aol.com didn't have anything to do with it.

http://www.arin.net

If it's so important to view e-mail headers, why don't all commercial e-mail programs display them by default? That's a good question, but I don't have the answer. In today's UCE-infested inboxes, companies should automatically display e-mail headers with the message. Despite the numerous e-mail filtering tools that are available, it's impossible to filter e-mail perfectly—unless you have the in-depth header information.

Since forgeries are becoming more difficult to identify, gain experience examining e-mail headers so you can differentiate the good from the bad. This knowledge will help you report junk e-mails to ISPs or reporting agencies that track junk e-mailers.

For example, Julian Haight's SpamCop service scans e-mail headers and identifies forged e-mail, plus it tells the ISP where the message originated. SpamCop's output will, at the very least, give you a better understanding of how to read e-mail headers.

Source: http://techrepublic.com.com/5100-1009_11-6056367.html?tag=nl.e044

Administrator unable to unlock a "locked" computer

SYMPTOMS
After you restart a computer running Windows and no one has logged on, you may be unable to log on to the computer either locally or to the domain.

The following error message may be displayed at logon:
This computer is in use and has been locked.
Only or an administrator can unlock this computer.
Press Ctrl + Alt + Del to unlock this computer.
If you try to unlock the computer, the following error message may be displayed:
This computer is locked. Only or an administrator can unlock this computer.
If a user has logged on and logged off, you may be unable to log on to the computer (locally or to the domain) and the following error message may be displayed:
This computer is in use and has been locked.
Only domain\username or an administrator can unlock this computer.
Press Ctrl + Alt + Del to unlock this computer.
If you try to unlock the computer, the following error message may be displayed:
This computer is locked. Only domain\username or an administrator can unlock this computer.
NOTES• In the error messages above, domain is the domain name of the last user who logged on to the server and username is the name of the user who last logged on to the server.

CAUSE
This behavior can occur for either of the following reasons: • When the default screen saver is set to use a non-existent screen saver program.
• When you use a corrupted screen saver that is password protected.

RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, use another screen saver program (such as Logon.scr) that is installed locally on the system or that is not corrupted. 1. Start Registry Editor (Regedt32.exe).
2. Locate the Scrnsave.exe value under the following registry key:
HKEY_USERS\.Default\Control Panel\Desktop
3. On the Edit menu, click String, type logon.scr, and then click OK.
4. Locate the ScreenSaverIsSecure value.
5. On the Edit menu, click String, type 0, and then click OK.
6. Quit Registry Editor.

WORKAROUND
To work around this problem, use the appropriate method.

Method 1: When the Error Message States the Computer Is Locked by domain\username
1. Press CTRL+ALT+DELETE to unlock the computer.
2. Type the logon information for the last logged on user, and then click OK.
3. When the Unlock Computer dialog box disappears, press CTRL+ALT+DELETE and log on normally.

Method 2: When the Error Message Does Not State Who Locked the Computer
1. Use the Shutdown tool in the Microsoft Windows Resource Kit and attempt to shut down the locked computer. The System Shutdown dialog box is displayed on the locked computer, but the computer does not restart.
2. When the shutdown timer expires, the Welcome to Windows dialog box is displayed.
3. Before the screen saver becomes active, press CTRL+ALT+DELETE, and log on normally.
NOTE: If you do not use one of these methods to log on, you must restart the computer and log on before the screen saver program starts.

STATUS
This behavior is by design.

MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
99590 (http://support.microsoft.com/kb/99590/) How to activate the screen saver during logon
229687 (http://support.microsoft.com/kb/229687/) Err Msg: "Workstation Is Locked" with invalid screen saver program

Source: http://support.microsoft.com/kb/242917/en-us

You may receive a "Limited or no connectivity" message on a computer that is connected to the Internet by a DSL modem or a cable

SYMPTOMS
After you install Microsoft Windows XP Service Pack 2 on a computer that is connected to the Internet by a digital subscriber line (DSL) modem or by a cable modem, you may receive a message that is similar to the following message when you try to connect to the Internet:
Limited or no connectivity: The connection has limited or no connectivity. You might not be able to access the Internet or some network resources.
You may also receive error message 678 or error message 769.
CAUSE
When a Point-to-Point over Ethernet (PPPoE) connection is created in Windows XP, Windows XP creates both a local connection and a broadband connection. Because Windows XP creates the two connections by design, and because the Automatic Private Internet Protocol Addressing (APIPA) address is expected, Windows XP should not indicate that the local connection has limited connectivity.

However, if your computer is not configured as a PPPoE client computer and the computer obtains an APIPA address, that is a situation where limited connectivity exists. Therefore, Windows XP should indicate that the local connection has limited connectivity. For example, this might occur if a Dynamic Host Configuration Protocol (DHCP) server is not available on your network.

You may also receive this message when one or more of the following conditions are true: 1. Your DHCP server is down on a hardwired network. On a home network, this server could be your Internet service provider's server, your personal router, or your DHCP provider.
2. Your DHCP server is down on a wireless network. On a home network, this server could be your ISP's server, your personal router, or your DHCP provider.
3. On a wireless network, this message may appear when you use an incorrect Wired Equivalent Privacy (WEP) key or if you do not have a WEP key.
4. You may not have an IP address, or your TCP/IP settings may be corrupted.
5. You may be experiencing other issues that are related to your Internet connection.

WORKAROUND
Sometimes, you may receive this message even if your computer is currently connected to the Internet. To disable the message, follow these steps: 1. Click Start, click Run, type ncpa.cpl, and then click OK.
2. Double-click Local Area Connection, and then click Properties.
3. On the General tab, click to clear the Notify me when this connection has limited or no connectivity check box, click OK, and then click Close.
Note This does not resolve an issue. It just turns the message off.
MORE INFORMATION
For more information about troubleshooting Internet connectivity in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
892889 (http://www.kbAlertz.com/Feedback.aspx?kbNumber=892889/) You may receive error 678 or error 769 when you try to connect to the Internet or when you try to browse the Internet after you install Windows XP Service Pack 2

Source: http://www.kbalertz.com/Feedback_892896.aspx
May 2008
SMTWTFS
April 2008June 2008
123
45678910
11121314151617
18192021222324
25262728293031