Usenet News HOWTO

Total Page:16

File Type:pdf, Size:1020Kb

Usenet News HOWTO Usenet News HOWTO Shuvam Misra (usenet at starcomsoftware dot com) Revision History Revision 2.1 2002−08−20 Revised by: sm New sections on Security and Software History, lots of other small additions and cleanup Revision 2.0 2002−07−30 Revised by: sm Rewritten by new authors at Starcom Software Revision 1.4 1995−11−29 Revised by: vs Original document; authored by Vince Skahan. Usenet News HOWTO Table of Contents 1. What is the Usenet?........................................................................................................................................1 1.1. Discussion groups.............................................................................................................................1 1.2. How it works, loosely speaking........................................................................................................1 1.3. About sizes, volumes, and so on.......................................................................................................2 2. Principles of Operation...................................................................................................................................4 2.1. Newsgroups and articles...................................................................................................................4 2.2. Of readers and servers.......................................................................................................................6 2.3. Newsfeeds.........................................................................................................................................6 2.3.1. Fundamental concepts.............................................................................................................6 2.3.2. Types of newsfeeds.................................................................................................................8 2.4. Control messages............................................................................................................................10 3. Usenet news software....................................................................................................................................13 3.1. A brief history of Usenet systems...................................................................................................13 3.2. C−News and NNTPd......................................................................................................................13 3.3. INN.................................................................................................................................................14 3.4. Leafnode.........................................................................................................................................14 3.5. Suck................................................................................................................................................15 3.6. Carrier class software......................................................................................................................15 4. Setting up CNews + NNTPd.........................................................................................................................17 4.1. Getting the sources and stuff...........................................................................................................17 4.1.1. The sources............................................................................................................................17 4.1.2. The key configuration files....................................................................................................18 4.2. Compiling and installing.................................................................................................................18 4.3. Configuring the system: What and how to configure files?...........................................................19 4.4. Testing the system..........................................................................................................................22 4.5. pgpverify and controlperms............................................................................................................22 4.6. Feeding off an upstream neighbour................................................................................................23 4.7. Configuring outgoing feeds............................................................................................................23 4.7.1. By UUCP...............................................................................................................................23 4.7.2. By NNTP...............................................................................................................................24 5. Setting up INN...............................................................................................................................................25 5.1. Getting the source...........................................................................................................................25 5.2. Compiling and installing.................................................................................................................25 5.3. Configuring the system...................................................................................................................25 5.4. Setting up pgpverify........................................................................................................................25 5.5. Feeding off an upstream neighbour................................................................................................25 5.6. Setting up outgoing feeds...............................................................................................................25 5.7. Efficiency issues and advantages....................................................................................................25 6. Connecting email with Usenet news............................................................................................................26 6.1. Feeding Usenet news to email........................................................................................................26 6.2. Feeding email to news: the mail2news gateway.............................................................................26 6.3. Using GNU Mailman as an email−NNTP gateway........................................................................27 6.3.1. GNU's all−singing all−dancing MLM...................................................................................27 i Usenet News HOWTO Table of Contents 6. Connecting email with Usenet news 6.3.2. Features of GNU Mailman.............................................................................................27 6.3.3. Gateway features connecting NNTP and email....................................................................27 7. Security issues................................................................................................................................................28 7.1. Intrusion threats..............................................................................................................................28 7.1.1. Generic server vulnerabilities................................................................................................28 7.1.2. Vulnerabilities in Usenet software........................................................................................29 7.2. Vulnerabilities unique to the Usenet service..................................................................................29 7.2.1. Unsolicited commercial messages.........................................................................................30 7.2.2. Spurious control messages....................................................................................................30 8. Access control in NNTPd..............................................................................................................................31 8.1. Host−based access control..............................................................................................................31 8.2. User authentication and authorisation.............................................................................................31 8.2.1. The NNTPd password file.....................................................................................................31 8.2.2. Mapping users to newsgroups...............................................................................................31 8.2.3. The X−Authenticated−Author article header........................................................................31 8.2.4. Other article header additions................................................................................................31 9. Components of a running system................................................................................................................32 9.1. /var/lib/news: the CNews control area............................................................................................32 9.2. /var/spool/news: the article repository............................................................................................33 9.3. /usr/lib/newsbin: the executables....................................................................................................33 9.4. crontab and cron jobs......................................................................................................................33
Recommended publications
  • Technical and Legal Approaches to Unsolicited Electronic Mail, 35 USFL Rev
    UIC School of Law UIC Law Open Access Repository UIC Law Open Access Faculty Scholarship 1-1-2001 Technical and Legal Approaches to Unsolicited Electronic Mail, 35 U.S.F. L. Rev. 325 (2001) David E. Sorkin John Marshall Law School, [email protected] Follow this and additional works at: https://repository.law.uic.edu/facpubs Part of the Computer Law Commons, Internet Law Commons, Marketing Law Commons, and the Privacy Law Commons Recommended Citation David E. Sorkin, Technical and Legal Approaches to Unsolicited Electronic Mail, 35 U.S.F. L. Rev. 325 (2001). https://repository.law.uic.edu/facpubs/160 This Article is brought to you for free and open access by UIC Law Open Access Repository. It has been accepted for inclusion in UIC Law Open Access Faculty Scholarship by an authorized administrator of UIC Law Open Access Repository. For more information, please contact [email protected]. Technical and Legal Approaches to Unsolicited Electronic Mailt By DAVID E. SORKIN* "Spamming" is truly the scourge of the Information Age. This problem has become so widespread that it has begun to burden our information infrastructure. Entire new networks have had to be constructed to deal with it, when resources would be far better spent on educational or commercial needs. United States Senator Conrad Burns (R-MT)1 UNSOLICITED ELECTRONIC MAIL, also called "spain," 2 causes or contributes to a wide variety of problems for network administrators, t Copyright © 2000 David E. Sorkin. * Assistant Professor of Law, Center for Information Technology and Privacy Law, The John Marshall Law School; Visiting Scholar (1999-2000), Center for Education and Research in Information Assurance and Security (CERIAS), Purdue University.
    [Show full text]
  • UNIX and Computer Science Spreading UNIX Around the World: by Ronda Hauben an Interview with John Lions
    Winter/Spring 1994 Celebrating 25 Years of UNIX Volume 6 No 1 "I believe all significant software movements start at the grassroots level. UNIX, after all, was not developed by the President of AT&T." Kouichi Kishida, UNIX Review, Feb., 1987 UNIX and Computer Science Spreading UNIX Around the World: by Ronda Hauben An Interview with John Lions [Editor's Note: This year, 1994, is the 25th anniversary of the [Editor's Note: Looking through some magazines in a local invention of UNIX in 1969 at Bell Labs. The following is university library, I came upon back issues of UNIX Review from a "Work In Progress" introduced at the USENIX from the mid 1980's. In these issues were articles by or inter- Summer 1993 Conference in Cincinnati, Ohio. This article is views with several of the pioneers who developed UNIX. As intended as a contribution to a discussion about the sig- part of my research for a paper about the history and devel- nificance of the UNIX breakthrough and the lessons to be opment of the early days of UNIX, I felt it would be helpful learned from it for making the next step forward.] to be able to ask some of these pioneers additional questions The Multics collaboration (1964-1968) had been created to based on the events and developments described in the UNIX "show that general-purpose, multiuser, timesharing systems Review Interviews. were viable." Based on the results of research gained at MIT Following is an interview conducted via E-mail with John using the MIT Compatible Time-Sharing System (CTSS), Lions, who wrote A Commentary on the UNIX Operating AT&T and GE agreed to work with MIT to build a "new System describing Version 6 UNIX to accompany the "UNIX hardware, a new operating system, a new file system, and a Operating System Source Code Level 6" for the students in new user interface." Though the project proceeded slowly his operating systems class at the University of New South and it took years to develop Multics, Doug Comer, a Profes- Wales in Australia.
    [Show full text]
  • Maximum Internet Security: a Hackers Guide - Networking - Intrusion Detection
    - Maximum Internet Security: A Hackers Guide - Networking - Intrusion Detection Exact Phrase All Words Search Tips Maximum Internet Security: A Hackers Guide Author: Publishing Sams Web Price: $49.99 US Publisher: Sams Featured Author ISBN: 1575212684 Benoît Marchal Publication Date: 6/25/97 Pages: 928 Benoît Marchal Table of Contents runs Pineapplesoft, a Save to MyInformIT consulting company that specializes in Internet applications — Now more than ever, it is imperative that users be able to protect their system particularly e-commerce, from hackers trashing their Web sites or stealing information. Written by a XML, and Java. In 1997, reformed hacker, this comprehensive resource identifies security holes in Ben co-founded the common computer and network systems, allowing system administrators to XML/EDI Group, a think discover faults inherent within their network- and work toward a solution to tank that promotes the use those problems. of XML in e-commerce applications. Table of Contents I Setting the Stage 1 -Why Did I Write This Book? 2 -How This Book Will Help You Featured Book 3 -Hackers and Crackers Sams Teach 4 -Just Who Can Be Hacked, Anyway? Yourself Shell II Understanding the Terrain Programming in 5 -Is Security a Futile Endeavor? 24 Hours 6 -A Brief Primer on TCP/IP 7 -Birth of a Network: The Internet Take control of your 8 -Internet Warfare systems by harnessing the power of the shell. III Tools 9 -Scanners 10 -Password Crackers 11 -Trojans 12 -Sniffers 13 -Techniques to Hide One's Identity 14 -Destructive Devices IV Platforms
    [Show full text]
  • Lesson 1 Key-Terms Meanings: Internet Connectivity Principles
    Lesson 1 Key-Terms Meanings: Internet Connectivity Principles Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 1 Publs.: McGraw-Hill Education Header Words • Header words are placed as per the actions required at succeeding stages during communication from Application layer • Each header word at a layer consists of one or more header fields • The header fields specify the actions as per the protocol used Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 2 Publs.: McGraw-Hill Education Header fields • Fields specify a set of parameters encoded in a header • Parameters and their encoding as per the protocol used at that layer • For example, fourth word header field for 32-bit Source IP address in network layer using IP Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 3 Publs.: McGraw-Hill Education Protocol Header Field Example • Header field means bits in a header word placed at appropriate bit place, for example, place between bit 0 and bit 31 when a word has 32-bits. • First word fields b31-b16 for IP packet length in bytes, b15-b4 Service type and precedence and b3-b0 for IP version • Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 4 Publs.: McGraw-Hill Education IP Header • Header fields consist of parameters and their encodings which are as per the IP protocol • An internet layer protocol at a source or destination in TCP/IP suite of protocols Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 5 Publs.: McGraw-Hill Education TCP Header • Header fields consist of parameters and their encoding which are as
    [Show full text]
  • Memetic Proliferation and Fan Participation in the Simpsons
    THE UNIVERSITY OF HULL Craptacular Science and the Worst Audience Ever: Memetic Proliferation and Fan Participation in The Simpsons being a Thesis submitted for the Degree of PhD Film Studies in the University of Hull by Jemma Diane Gilboy, BFA, BA (Hons) (University of Regina), MScRes (University of Edinburgh) April 2016 Craptacular Science and the Worst Audience Ever: Memetic Proliferation and Fan Participation in The Simpsons by Jemma D. Gilboy University of Hull 201108684 Abstract (Thesis Summary) The objective of this thesis is to establish meme theory as an analytical paradigm within the fields of screen and fan studies. Meme theory is an emerging framework founded upon the broad concept of a “meme”, a unit of culture that, if successful, proliferates among a given group of people. Created as a cultural analogue to genetics, memetics has developed into a cultural theory and, as the concept of memes is increasingly applied to online behaviours and activities, its relevance to the area of media studies materialises. The landscapes of media production and spectatorship are in constant fluctuation in response to rapid technological progress. The internet provides global citizens with unprecedented access to media texts (and their producers), information, and other individuals and collectives who share similar knowledge and interests. The unprecedented speed with (and extent to) which information and media content spread among individuals and communities warrants the consideration of a modern analytical paradigm that can accommodate and keep up with developments. Meme theory fills this gap as it is compatible with existing frameworks and offers researchers a new perspective on the factors driving the popularity and spread (or lack of popular engagement with) a given media text and its audience.
    [Show full text]
  • Nonprofit Security Grant Program Threat Incident Report
    Nonprofit Security Grant Program Threat Incident Report: January 2019 to Present November 15, 2020 (Updated 02/22/2021) Prepared By: Rob Goldberg, Senior Director, Legislative Affairs [email protected] The following is a compilation of recent threat incidents, at home or abroad, targeting Jews and Jewish institutions (and other faith-based organization) that have been reported in the public record. When completing the Threat section of the IJ (Part III. Risk): ▪ First Choice: Describe specific terror (or violent homegrown extremist) incidents, threats, hate crimes, and/or related vandalism, trespass, intimidation, or destruction of property that have targeted its property, membership, or personnel. This may also include a specific event or circumstance that impacted an affiliate or member of the organization’s system or network. ▪ Second Choice: Report on known incidents/threats that have occurred in the community and/or State where the organization is located. ▪ Third Choice: Reference the public record regarding incidents/threats against similar or like institutions at home or abroad. Since there is limited working space in the IJ, the sub-applicant should be selective in choosing appropriate examples to incorporate into the response: events that are most recent, geographically proximate, and closely related to their type or circumstance of their organization or are of such magnitude or breadth that they create a significant existential threat to the Jewish community at large. I. Overview of Recent Federal Risk Assessments of National Significance Summary The following assessments underscore the persistent threat of lethal violence and hate crimes against the Jewish community and other faith- and community-based institutions in the United States.
    [Show full text]
  • Ifdef Considered Harmful, Or Portability Experience with C News Henry Spencer – Zoology Computer Systems, University of Toronto Geoff Collyer – Software Tool & Die
    #ifdef Considered Harmful, or Portability Experience With C News Henry Spencer – Zoology Computer Systems, University of Toronto Geoff Collyer – Software Tool & Die ABSTRACT We believe that a C programmer’s impulse to use #ifdef in an attempt at portability is usually a mistake. Portability is generally the result of advance planning rather than trench warfare involving #ifdef. In the course of developing C News on different systems, we evolved various tactics for dealing with differences among systems without producing a welter of #ifdefs at points of difference. We discuss the alternatives to, and occasional proper use of, #ifdef. Introduction portability problems are repeatedly worked around rather than solved. The result is a tangled and often With UNIX running on many different comput- impenetrable web. Here’s a noteworthy example ers, vaguely UNIX-like systems running on still more, from a popular newsreader.1 See Figure 1. Observe and C running on practically everything, many peo- that, not content with merely nesting #ifdefs, the ple are suddenly finding it necessary to port C author has #ifdef and ordinary if statements (plus the software from one machine to another. When differ- mysterious IF macros) interweaving. This makes ences among systems cause trouble, the usual first the structure almost impossible to follow without impulse is to write two different versions of the going over it repeatedly, one case at a time. code—one per system—and use #ifdef to choose the appropriate one. This is usually a mistake. Furthermore, given worst case elaboration and nesting (each #ifdef always has a matching #else), Simple use of #ifdef works acceptably well the number of alternative code paths doubles with when differences are localized and only two versions each extra level of #ifdef.
    [Show full text]
  • Newscache – a High Performance Cache Implementation for Usenet News 
    THE ADVANCED COMPUTING SYSTEMS ASSOCIATION The following paper was originally published in the Proceedings of the USENIX Annual Technical Conference Monterey, California, USA, June 6-11, 1999 NewsCache – A High Performance Cache Implementation for Usenet News _ _ _ Thomas Gschwind and Manfred Hauswirth Technische Universität Wien © 1999 by The USENIX Association All Rights Reserved Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org NewsCache – A High Performance Cache Implementation for Usenet News Thomas Gschwind Manfred Hauswirth g ftom,M.Hauswirth @infosys.tuwien.ac.at Distributed Systems Group Technische Universitat¨ Wien Argentinierstraße 8/E1841 A-1040 Wien, Austria, Europe Abstract and thus provided to its clients are defined by the news server’s administrator. Usenet News is reaching its limits as current traffic strains the available infrastructure. News data volume The world-wide set of cooperating news servers makes increases steadily and competition with other Internet up the distribution infrastructure of the News system. services has intensified. Consequently bandwidth re- Articles are distributed among news servers using the quirements are often beyond that provided by typical Network News Transfer Protocol (NNTP) which is de- links and the processing power needed exceeds a sin- fined in RFC977 [2]. In recent years several exten- gle system’s capabilities.
    [Show full text]
  • Fortran Resources 1
    Fortran Resources 1 Ian D Chivers Jane Sleightholme May 7, 2021 1The original basis for this document was Mike Metcalf’s Fortran Information File. The next input came from people on comp-fortran-90. Details of how to subscribe or browse this list can be found in this document. If you have any corrections, additions, suggestions etc to make please contact us and we will endeavor to include your comments in later versions. Thanks to all the people who have contributed. Revision history The most recent version can be found at https://www.fortranplus.co.uk/fortran-information/ and the files section of the comp-fortran-90 list. https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=comp-fortran-90 • May 2021. Major update to the Intel entry. Also changes to the editors and IDE section, the graphics section, and the parallel programming section. • October 2020. Added an entry for Nvidia to the compiler section. Nvidia has integrated the PGI compiler suite into their NVIDIA HPC SDK product. Nvidia are also contributing to the LLVM Flang project. Updated the ’Additional Compiler Information’ entry in the compiler section. The Polyhedron benchmarks discuss automatic parallelisation. The fortranplus entry covers the diagnostic capability of the Cray, gfortran, Intel, Nag, Oracle and Nvidia compilers. Updated one entry and removed three others from the software tools section. Added ’Fortran Discourse’ to the e-lists section. We have also made changes to the Latex style sheet. • September 2020. Added a computer arithmetic and IEEE formats section. • June 2020. Updated the compiler entry with details of standard conformance.
    [Show full text]
  • Linux Network Administrators Guide
    Chapter 21. C News One of the most popular software packages for Netnews is C News. It was designed for sites that carry news over UUCP links. This chapter will discuss the central concepts of C News, basic installation, and maintenance tasks. C News stores its configuration files in /etc/news, and most of its binaries are kept below the /usr/lib/news/ directory. Articles are kept below /var/spool/news. You should make sure that virtually all files in these directories are owned by user news or group news. Most problems arise from files being inaccessible to C News. Use su to become the user news before you touch anything in the directory. The only exception is the setnewsids command, which is used to set the real user ID of some news programs. It must be owned by root and have the setuid bit set. In this chapter, we describe all C News configuration files in detail and show you what you have to do to keep your site running. Chapter 21. C News 402 21.1. Delivering News Articles can be fed to C News in several ways. When a local user posts an article, the newsreader usually hands it to the inews command, which completes the header information. News from remote sites, be it a single article or a whole batch, is given to the rnews command, which stores it in the /var/spool/news/in.coming directory, from where it will be picked up at a later time by newsrun. With any of these two techniques, however, the article will eventually be handed to the relaynews command.
    [Show full text]
  • ED381174.Pdf
    DOCUMENT RESUME ED 381 174 IR 055 469 AUTHOR Klatt, Edward C.; And Others TITLE Windows to the World: Utah Library Network Internet Training Manual. INSTITUTION Utah State Library, Salt Lake City. PUB DATE Mar 95 NOTE 136p. AVAILABLE FROMWorld Wide Web at http://www.state.lib.ut.us/internet.htm (available electronically) or Utah State Library Division, 2150 S. 3rd W., Suite 16, Salt Lake City, UT 84115-2579 ($10; quantity price, $5). PUB TYPE Guides Non-Classroom Use (055) EDRS PRICE MF01/PC06 Plus Postage. DESCRIPTORS Access to Information; *Computer Networks; Computer Software; Electronic Mail; *information Networks; *Information Systems; *Librarians; Online Catalogs; Professional Training; Telecommunications IDENTIFIERS *Internet; Utah ABSTRACT This guide reviews the basic principles of Internet exploration for the novice user, describing various functions and utilizing "onscreen" displays. The introduction explains what the Internet is, and provides historical information. The introduction is followed by a listing of Internet hardware and software (freeware and shareware), both lists including information fo: PC-compatibles and Macintosh computers. Users are introduced to and instructed in the use of the following Internet systems and services: EWAN telnet; OPACS (Online Public Access Catalogs); CARL (Colorado Alliance of Research Libraries; FirstSearch; UMI (University Microfilm Inc.); Deseret News; Pegasus E-Mail; Listservs; WinVN Newsreader; Viewers; Netscape; Mosaic; Gopher; Archie; and FTP (File Transfer Protocol). Over 100 computer screen reproductions help to illustrate the instruction. Contains 16 references and a form for ordering additional copies of this guide are provided. (MAS) *********************************************************************** Reproductions supplied by EDRS are the best that can be made from the original document.
    [Show full text]
  • Engineering at Johns Hopkins University! We Look Forward to Meeting You When You Arrive on Campus for Orientation
    Eng in eering 1 01 2019-2020 p rogr am p lanni ng gui de for fi rst-y ear e ngi neering s tudents Welcome to the Whiting School of Engineering at Johns Hopkins University! We look forward to meeting you when you arrive on campus for orientation. In the meantime, we have prepared the First-Year Academic Guide and Engineering 101 to get you started. The Academic Guide includes information for all first-year students at Hopkins, while Engineering 101 is directed specifically to engineering students. Engineering 101 contains information about all of the majors in the School of Engineering, including recommended first semester class schedules. You’ll also find out about some opportunities to join student groups. We hope that these materials help you learn about the Hopkins community and the options available to you. Again, welcome to Hopkins and we’ll see you in August! Linda Moulton, Denise Shipley, Lashell Silver, Eric Simmons, Janet Weise, and Betty Zee Johns Hopkins University Whiting School of Engineering Office of Academic Affairs—Engineering Advising Wyman Park Building Suite N125 3400 N. Charles Street Baltimore, MD 21218-2681 410-516-7395 [email protected] https://engineering.jhu.edu/advising/ Nondiscrimination Statement The Johns Hopkins University is committed to equal opportunity and providing a safe and non- discriminatory educational and working environment for its students, trainees, faculty, staff, post-doctoral fellows, residents, and other members of the University community. To that end, the university seeks to provide community members with an environment that is free from discrimination and harassment on the basis of sex, gender, marital status, pregnancy, race, color, ethnicity, national origin, age, disability, religion, sexual orientation, gender identity or expression, veteran status or other legally protected characteristic.
    [Show full text]