Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

10/18/2007
12:58 PM
50%
50%

Can The RIAA Close Down Usenet?

Those of us who remember the Internet before the Web -- and yes, Virginia, there was an Internet before the Web -- will remember when Usenet was one of the major destinations for discussion and file-sharing. It's still there, in a quiet corner where the cognizanti hoped it would go unnoticed by the great unwashed. No more.

Those of us who remember the Internet before the Web -- and yes, Virginia, there was an Internet before the Web -- will remember when Usenet was one of the major destinations for discussion and file-sharing. It's still there, in a quiet corner where the cognizanti hoped it would go unnoticed by the great unwashed. No more.For those unfamiliar with the term, Usenet is made up of a dispersed series of networked servers that offer a vast range of what are called newsgroups -- running collections of discussions and/or digital uploads that take in any subject matter imaginable. For example, years before social networking became the Web's Next Big Thing, I haunted newsgroups such as rec.arts.sf.written (a discussion group on science fiction literature) and comp.sys.psion.misc (for talk about Psion's long-ago orphaned line of PDAs).

The nice thing (and not-so-nice thing) about Usenet is that it is totally anonymous. It is very hard, if not impossible, to track Usenet users. For those of us who use it as a forum for discussion, that means you don't have to worry about privacy when leaving messages (unfortunately, neither do flamers, but that is the price you pay). For those who use the binary groups to exchange files, it also means that they feel safe from irritable music corporations. Exchanging files on Usenet is not simple -- files have to be split up for uploading and then reassembled after download, a task that most casual Web users don't want to take on. As a result, it never caught on with the majority of media file downloaders -- those who frequent Usenet do so quietly and, for the most part, under the radar.

However, the radar has found them. The RIAA, which has apparently dedicated itself to the mission of searching out copyright violators no matter where they might hide, has chosen for its next well-publicized target a Usenet access provider called Usenet.com. Now, keep in mind that the RIAA is not going up against the Usenet itself -- there's nobody really to sue in that huge decentralized tangle (unless you count the U.S. government, which started the whole thing). It is going up against one of those companies that offer users access to the vast library of Usenet newsgroups.

Admittedly, Usenet.com doesn't have the most subtle of marketing strategies. Its Web site states happily that, "We don't log your activity. We don't track your downloads, and neither can your ISP when you add Secure-Tunnel.com's Privacy Package." Them's fightin' words, as far as the RIAA is concerned. However, Usenet.com is certainly not the only company that provides access to binary newsgroups. In fact, almost any ISP offers some Usenet access, although that can vary.

So the question is: If the RIAA succeeds in its lawsuit, will ISPs and other access providers start restricting access to binary newsgroups? Can they? Keep in mind that these newsgroups are not simply there to trade in copyrighted material -- there are also newsgroups dedicated to media that are out of copyright, freeware and shareware, and a number of other perfectly legitimate downloads. (Of course, there are also probably a good many illegal copies of commercial software there as well -- I wonder how closely Microsoft's legal department is watching this.)

Usenet has been a relatively obscure playground for tech enthusiasts since 1979. Is that playground about to be invaded by lawyers -- and are the bulldozers far behind?

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31769
PUBLISHED: 2021-06-21
MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require autho...
CVE-2020-20469
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the log_edit.php files failing to filter the csa_to_user parameter, remote attackers can exploit the vulnerability to obtain database sensitive information.
CVE-2020-20470
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has web site physical path leakage vulnerability.
CVE-2020-20471
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has an unauthorized access vulnerability in default_user_edit.php, remote attackers can exploit this vulnerability to escalate to admin privileges.
CVE-2020-20472
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a sensitive information disclosure vulnerability. The if_get_addbook.php file does not have an authentication operation. Remote attackers can obtain username information for all users of the current site.