|
|
|
Windows Secrets Newsletter • Issue 183 • 2009-02-05 • Circulation: over 400,000 |
|
AD
|
|
Table of contents TOP STORY: Watch a live video, share your PC with CNN KNOWN ISSUES: If NoAutoRun.reg doesn't work, you may need space WACKY WEB WEEK: Giving up on society? Get one of these! LANGALIST PLUS: Make sure your PC's BIOS supports USB WOODY'S WINDOWS: Microsoft claims Windows 7 UAC flaw is by design PATCH WATCH: Conficker/Downadup woes may not be over |
|
ADS
|
|
TOP STORY Watch a live video, share your PC with CNN
By
Brian Livingston
Many people who watched live streaming video of the inauguration of U.S. President Barack Obama on Jan. 20 may not realize that their PC was used to send the video to other PCs, too. Clicking "yes" to a CNN.com dialog box installed a peer-to-peer (P2P) application that uses your Internet bandwidth rather than CNN's to send live video to other viewers. The P2P application is called Octoshape Grid Delivery and is managed by Octoshape ApS, a company based in Copenhagen, Denmark. Web surfers who visit CNN.com and select a live video stream for the first time see in their browsers a dialog box, shown in Figure 1, saying, "This site requires the Octoshape Grid Delivery enhancement for Adobe Flash Player." The dialog box doesn't appear when playing an ordinary video file, only when starting a live feed. (Feeds labeled LIVE typically appear in the upper-right corner of CNN.com's home page during business hours.) ![]() Figure 1. Users who select a CNN.com live video feed see a dialog box to install the Octoshape Grid Delivery application. According to Octoshape's end-user license agreement (EULA), what's installed is a peer-to-peer app that will "deliver parts of the video and audio stream to other end users of the Software." Why should you care? Windows Secrets contributing editor Ryan Russell, using a network sniffer, measured Octoshape using upstream bandwidth of 320 kilobits per second on a broadband connection. Dan Ferrell, in a comment on contributing editor Susan Bradley's blog, reports seeing 600 Kbps of upstream traffic. At first glance, Ferrell adds, the multiple connections to his PC looked on his security alert system like some kind of SQL attack. The Internet Storm Center, an Internet security organization, reported that traffic on Jan. 20 had jumped to a level thousands of times higher than usual on port 8247, which is used for UDP, the User Datagram Protocol. (See Figure 2.) The center quickly identified the source as legitimate — CNN — but security consultant Raul Siles warned in his report, "It would be easy for an attacker to hide his actions on this port if we simply ignore it." ![]() Figure 2. The Internet Storm Center measured an enormous increase in UDP traffic on Jan. 20. In a telephone interview, Octoshape's P2P nature was confirmed by Mike Wise, group technical advisor for platform R&D at Turner Broadcasting System, the parent of CNN. Wise emphasized that the news network had selected the most considerate software for the job: "The Octoshape technology uses a congestion control mechanism that's less aggressive than TCP and most UDP implementations." As one example of the way Octoshape gives priority to user tasks, he explained, "we chose an implementation that wouldn't interfere with consumer's VoIP [Voice over Internet Protocol] applications." As a European company, Octoshape's technology was initially used on the continent to stream live feeds of such high-profile events as the Eurovision Song Contest and the UEFA Cup. "We're their first big United States customer, as least that I know of," says Wise. "We did some limited trials leading up to the election" on Nov. 4, as Wise describes it. The big test came with the Jan. 20 inaugural address. More than 26 million live feeds (including restarts of crashed streams) were served that day by CNN.com, according to a Jan. 25 article and chart in the New York Times. CNN's nearest rivals served "only" 9.1 million (MSNBC) and 8 million (AP). To my surprise, I've seen only a few blogs comment on the implications of CNN using so much upstream bandwidth — and almost no headlines in the mainstream U.S. media. Most Internet service providers support far less bandwidth in the upstream direction (from a PC to the Internet) than they do downstream (from the Internet to a PC). But that isn't the only concern with CNN's use of people's Internet connections:
But if all TV programs are going to be streamed live by media giants, as I'm sure will eventually happen, the question is what impact this will have on Internet bandwidth — and who will pay for it. I'd like to see the computer industry start a well-publicized discussion in the major news media about this. If we're going to stream TV across the Internet, shouldn't we select an open standard (the TorrentFreak blog likes P2P-Next), rather than proprietary technology that's restricted to a few parties with patents? What to do if you have Octoshape on your PC As I mentioned earlier, the Octoshape app isn't currently a threat. But I personally would rather put up with a slightly jerky video than run an application on my PC that's sending God-knows-what to who-knows-whom. Fortunately, the Octoshape program isn't hard to find or remove:
Brian Livingston is editorial director of WindowsSecrets.com and co-author of Windows Vista Secrets and 10 other books. |
|
ADS
|
|
KNOWN ISSUES If NoAutoRun.reg doesn't work, you may need space
Windows Secrets contributing editor Woody Leonhard authored a Jan. 22 Top Story on the Conficker/Downadup worm and included a link to a Nov. 8, 2007, article. That article, by associate editor Scott Dunn, explained how to add a Registry key to block Windows' AutoRun function. After you do this, if you unknowingly insert a hacked CD, DVD, USB drive, or other external drive, it won't automatically infect your PC. The technique involves copying and pasting three lines of code into a NoAutoRun.reg file, then right-clicking the file, merging it into the Registry, and rebooting. One of the lines of code is very long and looks as follows (it's all one line, but it word-wraps to two lines in small windows): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\Autorun.inf Reader Rob Oppenheim wasn't the only reader who found that merging into the Registry the file he created had no effect, because he'd entered a line break where his e-mail program had word-wrapped that line:
Regardless how the Registry key appears in your browser, if you copy the lines from Scott's article and paste them into your text editor to create a NoAutoRun.reg file, the space between "Windows" and "NT" will be included. Delete the key to restore your AutoRun Several people tried life without AutoRun and decided they missed the feature. For example, after disabling AutoRun, you must manually open the autorun.inf file on any software disc you might want to auto-install. Marlin Brutlag puts it succinctly:
See Microsoft Knowledge Base article 310516 for details on adding, deleting, and modifying Registry keys. Resuscitate a dead drive by giving it the gas After reading reader Scotty Burrous's description of how he brought a hard drive in his mother's PC back from the dead, I started to think I'd been watching too many scary movies:
The Known Issues column brings you readers' comments on our recent articles. Dennis O'Reilly is technical editor of WindowsSecrets.com. |
|
WACKY WEB WEEK Giving up on society? Get one of these!
|
|
AD
|
|
PERMALINKS Use these permalinks to share info with friends We love it when you include the links shown below in e-mails to your friends. This is better than forwarding your copy of our e-mail newsletter. (When our newsletter is forwarded, some recipients click "report as spam" and corporate filters start blocking our e-mails.) The following link includes all articles this week: http://WindowsSecrets.com/comp/090205 Free content posted on Feb. 5, 2009:
You get all of the following in our paid content:
Thanks in advance for your support! |
|
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 resulted from the merger of several 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 LLC, Attn: #120 Editor, 1700 7th Ave., Suite 116, Seattle, WA 98101-1323 USA. Vendors, please send no unsolicited packages to this address (readers' letters are fine). Editorial Director: Brian Livingston. Senior Editor: Ian Richards. Editor-at-Large: Fred Langa. Technical Editor: Dennis O'Reilly. Program Director: Tony Johnston. Program Manager: Ryan Biesemeyer. Web Developer: Damian Wadley. Editorial Assistant: Katy Abby. Copyeditor: Roberta Scholz. Contributing Editors: Susan Bradley, Scott Dunn, Mark Joseph Edwards, Stuart J. Johnston, Woody Leonhard, Ryan Russell, Becky Waring. 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 LLC. 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,
|