Windows Secrets

Subscribers: Sign in

Enter your e-mail address to get a free subscription.
We guarantee your privacy
Skip to content
  • Home
  • Newsletter Archives
    • Current
    • LangaList Plus
    • Patch Watch
    • Wacky Web Week
    • Security Baseline
  • E-Books
  • Lounge
  • About us
    • Refunds
    • Privacy Policy
    • Advertise
  • Contact
  • Your Account
    • Upgrade
    • Preferences
    • Bonus Download
    • Unsubscribe
Home>Pop-up ads can land you in jail

Windows Secrets Newsletter • Issue 97 • 2007-02-22 • Circulation: over 400,000


Table of contents 
  • Top Story: Pop-up ads can land you in jail
  • LangaList Plus: Make more space by deleting log files
  • Wacky Web Week: Gollum and Smeagol get their groove on
  • LangaList Plus: Avoid firewall confusion with insider secrets
  • Woody's Windows: Vista Timesaver #4 — the Windows Experience Index

 
Top Story

Pop-up ads can land you in jail

Ryan russell By Ryan Russell

If you find yourself the victim of pop-up ads on a computer, with children in the vicinity, you could face decades in prison.

I wish that I was exaggerating or being sensationalistic, but for Julie Amero this is far too real.

Meet Julie Amero, substitute teacher

There’s a good chance that you’ve already heard something about Julie. She’s perhaps better known as the Connecticut substitute schoolteacher who’s been convicted of "child endangerment." She now faces a sentence of up to 40 years in prison because porn pop-ups appeared on a school computer.

For background on the case, you can read articles from the New York Times, MSNBC, or SecurityFocus. (Full disclosure: WSN editorial director Brian Livingston is quoted in the New York Times piece supporting Julie. The article at the MSNBC site is also a good read, but I don’t recommend the accompanying video, which starts out with a falsehood and goes downhill from there.)

Let me begin by saying that I’m biased when it comes to Julie’s innocence. I’m doing my best to spread the word about her case, and have offered my technical skills to support her defense. I have access to some technical experts who are reviewing the trial transcripts and computer forensic evidence. I can’t point to a public reference to support all of my positions yet, so you’ll just have to take my word, for the time being.

There are many points I could make about what’s wrong with her case. But I’ll stick with my core competency and just point out some of the technical flaws.

Flawed technology condemns an educator

The key issues were set in motion before Julie ever arrived to substitute-teach on the day in October 2004 that the pop-ups occurred. The school district had allowed its Web-filtering software support contract to expire, preventing the software from receiving updates. The computer in question was running Windows 98, and the browser in use was IE 6.

According to evidence analysis performed by Alex Shipp, an independent malware researcher, the antivirus software was a trial version of Cheyenne Antivirus (CA). That product had been discontinued by Computer Associates on Mar. 17, 2004. It appears that CA issued a last courtesy update on June 30. Julie taught the class on Oct. 19. The computer had no antispyware software.

In other words, this computer had almost no protection and an unsecurable operating system. This is the machine Julie was given to use.

On the day in question, the regular teacher was there before class to log Julie into the computer. Substitutes didn’t have their own accounts, and were ordered not to log out or shut down the computer. Julie left briefly and, when she returned, the regular teacher was gone. She found students, some of whom didn’t even belong in the upcoming class, Web surfing on the teacher’s computer.

Experts now analyzing the hard-drive image have confirmed that the computer had been infected with adware days before Julie’s arrival. Unfortunately, in this case, that means that when a student tried to visit a hairstyle Web site, he or she was instead redirected to a different site that had adult products advertised. When Julie tried to close the site down, this started a pop-up cascade.

One thing I should mention about Julie: She’s a total "computerphobe." She can perform basic computing functions, but that’s about it.

So what did she do when she couldn’t get rid of the pop-ups? She turned the screen away from the students. It was at the front of the room, where the students would have had to be essentially at the teacher’s desk in order to see. She did her best to get rid of the images without making it obvious to the students that something was wrong. If a student approached, she reportedly chased them away.

During a break, Julie went for technical help to get rid of the pop-ups, which reappeared as fast as she tried to close them, but she received no help. No one would return to the classroom with her. She was told not to worry about it. However, she was worried about it, and it turns out she had reason to worry — she was later arrested for "child endangerment."

Legal system fails pop-up victim

When law enforcement became involved, sanity should have prevailed. Instead, the technical flubs continued, and the case sped downhill. A detective was assigned to take a forensic image of the computer and perform a technical analysis.

Let me briefly tell you what I know about taking a proper forensic image of a computer that will be involved in a criminal case. Keep in mind that I’m not a forensics expert; these standards are just common knowledge in the computer security field.

If you’re going to image a drive for evidence, you have to use special write-blocking hardware that helps take a sector-by-sector image of the entire hard drive, including the "empty" space. The image is then hashed so that any tampering will be evident, and you always work from copies.

Typically, only software tools with support from existing case law are used. Otherwise, questions can arise over the soundness of the tools and techniques. The imaging tools that have case law behind them are EnCase and the Unix dd utility.

The detective in this case took an “image” of the hard drive with Norton Ghost. Norton Ghost is a tool used to back up a computer’s hard drive in order to restore it to a known state after people have modified the configuration. It is often used on training or lab machines. There is nothing wrong with Ghost for what it does, but it is not a forensic tool.

So what did the detective use to examine the “image”? He used a program called ComputerCOP Pro. It appears that the program displays a version of the Internet Explorer history, which shows the URLs that were visited. At trial, this ended up translating to the prosecutor telling the jury that this means that Julie “physically clicked” those links. In fact, pop-ups show up in the history the same way as a link you click on.

In truth, the software also cannot tell you who was in front of the computer, who typed in a URL, or who saw the pictures displayed. It’s clear that someone who lacks the technical background to properly interpret the results, and is not willing to put in the time to figure it out, can jump to some very wrong conclusions. The detective never even looked for spyware on the computer.

This is the kind of technical evidence on which Julie was convicted.

An innocent teacher awaits sentencing

Julie is now awaiting sentencing, which is scheduled for Mar. 2. I could discuss jail-time possibilities, but many of us are still refusing to accept any possibility other than someone coming to their senses and throwing the verdict out.

To that end, the experts I mentioned are frantically preparing their report on the technical information. The hope is that the prosecution or court will recognize that there has been a basic mistake in the facts presented at trial before a sentence is handed down.

Despite my bias that I told you about, do you have reasonable doubt about Julie’s guilt? For more information, see the julieamer blog at Blogspot, which is largely maintained by Julie’s husband. There’s a PayPal button at the top of that blog so people can contribute to help pay Julie’s defense costs, which are reported to be over $20,000 so far.

Ryan Russell is quality assurance manager at BigFix Inc., a configuration management company. He moderated the vuln-dev mailing list for three years under the alias “Blue Boar.” He was the lead author of Hack-Proofing Your Network, 2nd Ed., and the technical editor of the Stealing the Network book series. His Perimeter Scan column appears twice a month in the paid version of the newsletter.

 
LangaList Plus

Make more space by deleting log files

Fred langa By Fred Langa

Log files can be useful, but they mainly just take up space.

Trim away your useless log files to gain space and make your backups and restores smaller and faster!

Hidden log files eat your disk space

Log files can be useful: They’re usually plain-text records of actions taken by software as it runs — changes made, files added or deleted, and so on. When something goes wrong, it may be possible to examine the appropriate log file to see what the software was trying to do when it encountered trouble. That, in turn, can be a valuable troubleshooting clue.

But over the years, log files have moved from front-line troubleshooting to a rarely used and obscure tool tucked away on your PC. Log files can be like weeds, growing in the quiet corners of your hard drive.

Try this experiment in order to see just how many log files are taking up space on your hard drive:

Click Start, Search, then search All files and folders on your hard drive for any files named *.log. Odds are, you’ll find hundreds of log files you probably never knew existed. (The Windows folder tree alone is a rich repository of log files.) My system currently has almost 900 of the suckers!

With today’s large disks, a passel of small log files isn’t worth worrying about. But sometimes log files can become huge, or a single active program may create a large quantity of log files. Karen Cleveland found one such instance in the ZoneAlarm Security Suite, which practically logs every heartbeat. Let’s take a look at her example, but keep in mind that the log-file proliferation caused by other programs can often be cured in similar ways:
  • "I’ve installed ZoneAlarm (ZA) Internet Security Suite 6.5, which I purchased in the box off-the-shelf at a major computer store. I’m having a problem with ZA writing multiple files to the c:WINNTInternet Logs directory. These files are continually modified by ZA and quickly become very large (i.e., many MBs).

    "I stumbled upon this phenomenon because I noticed the free space on my hard disk kept decreasing day after day. Another problem is that the storage space used by System Restore is also consumed, because these files are backed up when a restore point is created. The restore directory in c:System Volume Information was also growing by leaps and bounds. My hard disk is/was being cannibalized.

    "Do you know how to fix these problems? I don’t want to get rid of ZA, but I can’t continue using it the way it is now."
First and foremost, log files are usually simple plain-text files. You can open them in Notepad and see what they contain. You can delete them if you’re sure that neither you nor the application that created them will need the information inside. (Tip: Copy the log files to a CD or other safe place before you delete them from your hard drive. Then, if it turns out you need the information, it’s still recoverable.)

You also can use various disk-cleaning utilities to delete log files automatically, if you’re sure you no longer need them. For example, the free do-it-yourself CleanAll tool can easily be modified to delete any or all of the log files on your system each time it runs.

But sometimes, software will lock a log file while it’s in use, making it difficult to remove by normal means. A tool like the free and excellent MoveOnBoot (a more powerful paid version is also available) can delete files that are normally locked, in-use, or otherwise unable to be deleted from inside Windows.

The above steps can take care of log files after they’re created. But, of course, it’s best to keep unneeded log files from being generated in the first place. Most log-creating software, including the ZoneAlarm Security Suite, lets you turn off the log file function, if you’re sure you don’t need it.

ZoneAlarm logging
Figure 1. This example shows how the ZoneAlarm Pro firewall lets you control its log keeping. The "Advanced" button allows even finer control.

For example, to enable, disable, or alter event logging and program logging in the ZoneAlarm Security Suite and in the stand-alone Zone Alarm Pro firewall, follow these steps:

Step 1. Select Alerts & Logs.

Step 2. In the Event Logging area, select the desired setting. On creates a log entry for all events. Off means no events are logged.

Step 3. In the Program Logging area, specify the log level. High creates a log entry for all program alerts. Med. creates a log entry for high-rated program alerts only. Off means no program events are logged.

So, if you’re drowning in log files — even hidden log files you never knew existed — you can easily get your head above water. Back up and delete the log files you don’t want or need, and then adjust your software so that it doesn’t create new unnecessary log files in the first place.

Running floppy-based tools with no floppy drive

Some software still legitimately needs to boot from a floppy drive. Reader Chris Henshaw asks what to do when your PC no longer has a floppy to boot from:
  • "I was about to purchase Symantec Ghost for use as ghosting [imaging] software. In the Feb. 8, 2007, issue, you wrote that BootItNG was your favorite. So, after reading the Terabyte Web site, I purchased a copy. When I tried to install it, I found that it required a floppy disk drive. Nowhere was this mentioned — either in your article or on the Terabyte Web site. I have not had a floppy disk drive for some years. Buyer beware!"
Your immediate problem is easily solved, Chris. BootItNG will run happily from any bootable medium, including bootable CDs, and even some Flash drives (depending on your hardware). You can use Terabyte’s free MakeDisk utility, or any number of third-party tools and techniques to convert bootable floppy disk images into CDs or other bootable media. There’s a good tutorial at Ultimate Boot CD.

The reason why BootItNG requires a floppy is also the main reason why I personally like and recommend it: BootItNG is 100% self-contained. When it’s running from its boot medium, Windows is entirely inert. No files are open or in use. Nothing is "live" on the hard drive.

This means that BootItNG’s partition work and imaging work has no competition from other programs while it’s running. Instead, the self-booting utility completely "owns" the PC and so is not likely to run into any problems with locked or in-use files, or files that change during the imaging process.

Most other disk-imaging tools that run from inside Windows (including Terabyte’s own Image for Windows) rely on software sleight-of-hand; features like shadowing to create reliable backups and images of in-use and locked files.

This usually works, but is not 100% certain, as is booting from an external medium. In fact, this is also why some tools that use shadowing and similar techniques still recommend that you close all other programs before making an image or backup. That’s the only way to get the reliability on par with that of externally bootable tools.

Admittedly, it’s less convenient to use a tool that requires a separate boot. To me, it’s worth it for the extra certainty of the imaging/backup process. But, it may not be for you. Indeed, BootItNG has a free trial period in which you can experiment to see if it fits your needs. If it doesn’t, you haven’t lost a dime.

CD-Rs don’t survive freezing temperatures

It’s midwinter here in the northern hemisphere, while our friends on the bottom half of the Earth swelter through summer. Either extreme can be deadly for CDs you create yourself, as reader Dalton Seymour found out:
  • "Just had a look at your Feb. 8, 2007, newsletter comments on how long CDs will last, which referenced McFadden’s FAQ on the subject of CDs. This struck a chord with me because this year, I had the occasion to transport my computer system and collection of CDs from Michigan to Missouri in the dead of winter. Everything was packed up in the back of a pickup truck and covered with a tarp to make the trip. CDs were all in jewel cases packed in cardboard boxes.

    "When they finally arrived, many of the home-grown CDs containing music transferred from vinyl to CD had died. Most were of the gold variety. My guess is that subfreezing temperatures may actually crystallize the dyes embedded in the plastic. These were all CD-R, not CD-RW. I had this happen to me once a long, long time ago with floppy media, but the phenomenon there was related to the lack of hysteresis [persistence of magnetism] at freezing temps."
Right you are, Dalton. CD-Rs last longest in dark and cool (but not cold) environments. If you burn CDs to carry data between work to home, or to rip your own music mixes, or for any other reason, don’t leave them exposed to extreme hot or cold. If you leave a CD-R sitting in your car in subfreezing temperatures or baking in the summer sun, you’ll run the risk of losing the data on that CD in a remarkably short period of time.

Another look at HijackThis

Reader Chris DeWitt’s note focuses on an old favorite antimalware tool:
  • "I’ve done some PC housecleaning for various people and found that some of the common tools I’ve used (Ad Aware, Spybot, NAV) don’t always do the job. After I’ve used them, I turn to HijackThis.exe. It does a scan of your system and gives you a listing and log file of lots of potential malware files. It takes pains to tell you that these are not guaranteed to be malware, but could be. It’s up to you to then go through each line, research the item, and determine for yourself if it is a culprit.

    "If you then redo the scan, you can check the appropriate lines in the list and click the Fix Checked button. It will then remove most of these. Some of the remaining items may need more sophisticated removal techniques. If you send the log file to one of the many online forms, you can get help both in determining which of these is malware and in removing the more stubborn ones. It’s a lot of work, but it can be done. Here is a link to one of the places you can get HijackThis.”
HijackThis is indeed an excellent and powerful tool. It produces so much information that it can actually be intimidating the first time you run it! Windows Secrets has discussed and recommended HijackThis on several occasions, including in the March 10, 2005, issue. The advice given then still stands today:
  • “Several online forums provide free help to interpret the technical output from HijackThis. These forums are described in the HijackThis log recommendations provided by anti-adware guru Eric Howes. You’ll also want to read the HijackThis Quick Start and the HijackThis tutorial."
Thanks, Chris!

Fred Langa edited the LangaList e-mail newsletter from 1997 to 2006, when it merged with Windows Secrets. Prior to that, he was editor of Byte Magazine and editorial director of CMP Media, overseeing Windows Magazine and others.

 
Wacky Web Week

Gollum and Smeagol get their groove on

Gollum A hilarious new video that appeared on the Web recently is a creative, creepy, and delightful duet version of a Barry White classic. It’s performed by none other than those loveable Lord of the Rings creatures, Gollum and Smeagol.

The characters do a great job of lip-syncing the song, at least as edited by a director who goes by the handle of amds. This definitely puts a new twist on the old soul classic. Watch the video

 
LangaList Plus

Avoid firewall confusion with insider secrets

Mark edwards Firewalls are great tools, but some people find them a bit frustrating.

This week I explain a bit about firewall technologies, firewall performance, how to extract and use information from firewall logs, and how to remove a certain firewall if the need should arise.


How to uninstall the Comodo firewall

Several weeks ago in the Jan. 11 edition of this newsletter I mentioned Comodo firewall, which was recommended by one of our readers. Many of you tried it and found it to be problematic. Lloyd Lamouria wrote to share his experience:
  • “After seeing the recommendation about Comodo, I decided to try it. After half a day of unsuccessfully trying to get it to play nice with my system, I finally decided to uninstall it. After the uninstall, nothing worked. No Internet connection, nothing in the Control Panel would work, Firefox would not start, Spy Sweeper hung, etc. Had to resort to a system restore. After doing some research, a lot of others have had problems as well. Just a word of caution.”
Thanks for the warning, Lloyd. If any of you readers need help uninstalling Comodo, a thread in the Comodo Support forums mentions a standalone tool that can remove the firewall completely. You can download the tool from the forum, but be aware that you must be signed up for an account and be logged in to see the download link. If you don’t want to use your real e-mail address when signing up for an account, try using Mailinator for a temporary inbox.

What ‘stateful inspection’ means for you

There are two basic types of firewalls; one is a "stateless" filtering system, while the other is a "stateful" inspection system. Bill Norrie wrote to ask about this:
  • “I installed Comodo on my wireless laptop after reading the article in the Jan. 11 edition. However, I came across this information below on a forum and wonder if you would like to comment on it:
    • “Comodo is not a stateful firewall. It makes little difference how good Comodo does in the leaktests; it omits the one thing the firewall was originally invented for, and that’s keeping ALL intruders out at ALL times, not just when ports are closed and hidden. The only technology with this capability is SPI, which is why it’s the one you’ll find in a hardware firewall.”
Bill, whoever wrote the post you quoted is misinformed. Comodo is, in fact, a stateful inspection firewall.

A stateless filtering system is basically a system that filters data packets without any regard to why the packet is arriving at your computer. It performs its filtering based on a simple set of rules that govern whether packets are allowed in or not, and it bases its design on parameters such as desination port numbers, protocol types, etc.

Stateful packet inspection (SPI) also filters packets, similarly to a stateless system. But it does its work based on a table of "connection states," thereby offeringan added layer of protection.

For example, when your browser opens a connection to a Web site, the firewall makes a record of that connection and keeps track of the state of the connection — whether it’s open or closed, etc. Then, when a packet arrives at your computer, the firewall compares data in the packet to the firewall state table to determine if the packet was intended for any of the connections the firewall knows about. A stateful inspection system can also base its decisions on the actual data content of the packets it receives. Overall, stateful inspection makes for a stronger type of firewall.

Stateful inspection can slow down your system

In the previous item, I briefly explained stateful inspection, but what I didn’t discuss was how stateful inspection affects system performance. Adib Behi noticed a performance lag on his system and wrote to ask about it:

  • “Whenever there is a noticeable slowdown in response time on my system, I check Comodo and it reports a flurry of ‘Inbound Policy Violation.’ Most of the time, those violations come from the same few IP source addresses, mostly based in Australia or China.

    “I’m happy that Comodo catches them and prevents access. Now, since this attack happens a few times every second, sometimes with short delays of five seconds in between, I presume this may be causing the slowdown. I’m no techie or Internet wiz, but that’s the only odd activity that I see.

    This article is part of our paid content. Subscribe.

    Already a paid subscriber? Click here to login.


 
Woody's Windows

Vista Timesaver #4 — the Windows Experience Index

Woody leonhard Windows Vista incorporates many firsts for Microsoft — some good, some dubious.

Microsoft’s first officially sanctioned hardware performance benchmark, the Windows Experience Index (WEI), displays some useful information — if you understand its limitations. Save yourself time and money by looking behind the numbers.


The trouble with Vista’s benchmarks

Hardware benchmarks have suffered a long, checkered history. Once the talk of the computer magazine industry, hardware manufacturers since the dawn of the Bronze Age have tweaked, mangled, and goosed their designs to boost meaningless performance numbers. Scandals erupted when manufacturers cooked their products to increase ratings in the big-name computer magazines, frequently sacrificing overall performance to gain a slight advantage with this test or that index.

Now it’s happening again.

But this time, Microsoft is putting its seal of approval on a collection of benchmark tests, which are baked right into Vista itself. Microsoft tries to gussy things up by calling its hardware benchmark numbers an "Experience Index." That’s like calling the Internal Revenue Service’s Form 1040 a "Wealth Assistant." But whatever you call it, you can bet that every hardware manufacturer from Biloxi to Bangalore has its cooks stewing overtime to boost their products’ Windows Experience Index (WEI).

When you look at your computer’s WEI, and when you comparison shop for products based on their WEI, remember that benchmarks always lie, but the best ones don’t lie as much. A 20% difference in any single WEI score won’t be perceptible to the average human. More than that, the WEI scores are calculated in a way that, in some cases, defies any sort of logic I can discern.

Before you waste time and money chasing an elusive performance boost, make sure you understand the numbers.

How to understand your computer’s WEI

You probably hunted down your computer’s WEI the minute you first booted Vista. If you haven’t seen yours yet, it’s worth a gander. There are many ways to get to the WEI, but one of the easiest is to click Start, Control Panel, then click the System and Maintenance link. Under the System icon, click the link marked Check your computer’s Windows Experience Index base score. Vista shows you the WEI that it calculated the last time it ran its set of benchmarks. The WEI for one of my Vista machines appears here as Figure 1.

This article is part of our paid content. Subscribe.

Already a paid subscriber? Click here to login.


YOUR SUBSCRIPTION

The Windows Secrets Newsletter is published weekly on the 1st through 4th Thursdays of each month, plus occasional news updates. We skip an issue on the 5th Thursday of any month, the week of Thanksgiving, and the last two weeks of August and December. Windows Secrets is a continuation of four merged publications: Brian's Buzz on Windows and Woody's Windows Watch in 2004, the LangaList in 2006, and the Support Alert Newsletter in 2008.

Publisher: WindowsSecrets.com, 1218 Third Ave., Suite 1515, Seattle, WA 98101 USA. Vendors, please send no unsolicited packages to this address (readers' letters are fine).

Editor in chief: Tracey Capen. Senior editors: Fred Langa, Woody Leonhard. Copyeditor: Roberta Scholz. Program director: Tony Johnston. Contributing editors: Yardena Arar, Susan Bradley, Scott Dunn, Michael Lasky, Scott Mace, Ryan Russell, Lincoln Spector, Robert Vamosi, Becky Waring. Product manager: Andy Boyd. Advertising director: Eric Gilley.

Trademarks: Microsoft and Windows are registered trademarks of Microsoft Corporation. The Windows Secrets series of books is published by Wiley Publishing Inc. The Windows Secrets Newsletter, WindowsSecrets.com, Support Alert, LangaList, LangaList Plus, WinFind, Security Baseline, Patch Watch, Perimeter Scan, Wacky Web Week, the Logo Design (W, S or road, and Star), and the slogan Everything Microsoft Forgot to Mention all are trademarks and service marks of WindowsSecrets.com. All other marks are the trademarks or service marks of their respective owners.

HOW TO SUBSCRIBE: Anyone may subscribe to this newsletter by visiting our free signup page.

WE GUARANTEE YOUR PRIVACY:

1. We will never sell, rent, or give away your address to any outside party, ever.
2. We will never send you any unrequested e-mail, besides newsletter updates.
3. All unsubscribe requests are honored immediately, period.  Privacy policy

HOW TO UNSUBSCRIBE: To unsubscribe from the Windows Secrets Newsletter,
  • Visit our Unsubscribe page.
Copyright © 2012 by WindowsSecrets.com. All rights reserved.

Table of contents

Top-scoring articles in the past 12 months
  • Leaving long cookie trails throughout the Web 5.00
  • Windows-like security for Android devices 5.00
  • Win7′s no-reformat, nondestructive reinstall 4.53
  • The sorry tale of the (un)Secure Sockets Layer 4.42
  • RPV: Win7′s least-known data-protection system 4.33
  • Recovery: the last step in total data security 4.30
  • Time for a .NET update we can’t ignore 4.30
  • Getting the most from Windows Search — Part 1 4.25
  • Revising printing habits saves money and trees 4.25
  • Upgrades end in erratic, partial hangs 4.25
  • Pros and cons of a ‘keyfile’ password 4.21
  • Beating back Duku and a plethora of other threats 4.20
  • Office 2007 gets its final service pack 4.19
  • Putting Registry-/system-cleanup apps to the test 4.19
  • One year and 99 security bulletins later 4.18
  • 1.8TB external drive goes down hard 4.17
  • Don’t pay for software you don’t need — Part 3 4.16
  • Internet Explorer gets another round of patches 4.15
  • Is your free AV tool a ‘resource pig?’ 4.15
  • Vacation’s over; it’s a big round of patches 4.15
  • Remote access leads to remote attacks 4.15
  • Keeping you up to date: say no to .NET — again 4.14
  • Take control of Google’s privacy policy settings 4.14
  • Office File Validation patch leads to problems 4.14
  • The advanced system-recover toolkit 4.13
  • New “419″ scam involves PayPal and Western Union 4.12
  • Readers’ best personal-privacy tips 4.11
  • Getting the most from Windows Search — Part 2 4.11
  • Re-examining Dropbox and its alternatives 4.10
  • Easily edit Windows’ right-click context menus 4.09
Connect with us Follow us on Twitter Connect with us on Facebook View our RSS Feeds
  • Home|
  • Newsletter|
  • About Windows Secrets|
  • Advertise with us|
  • Unsubscribe|
  • Sitemap|
  • Affiliates|
Trademarks: Microsoft and Windows are registered trademarks of Microsoft Corporation. The Windows Secrets series of books is published by Wiley Publishing Inc. The Windows Secrets Newsletter, WindowsSecrets.com, WinFind, Windows Gizmos, Security Baseline, Patch Watch, Perimeter Scan, Wacky Web Week, the Logo Design (W, S or road, and Star), and the slogan Everything Microsoft Forgot to Mention all are trademarks and service marks of iNET Interactive. All other marks are the trademarks or service marks of their respective owners.
iNET Interactive Copyright © 2011 iNET Interactive.
All rights reserved.
Terms of Use  |  Privacy Policy
Internet Services
  • Web Hosting Talk
  • HostingCon
  • Hosting Catalog
  • Host Voice
Web Development
  • Hot Scripts
  • DB Forums
Digital Marketing
  • ABestWeb
  • Search Marketing Standard
  • PayPerClickUniverse
  • SEMCompare
Consumer Tech
  • Windows Secrets
  • Overclockers
  • Mac Forums

Learn more about
advertising opportunities across the iNET Interactive Network.

LiquidWeb