aioe.* technical data

 

Table of contents

  1. General Informations
  2. Checkgroup
  3. Moderators
  4. GPG Key
  5. Control.ctl
  6. AntiSpam settings
  7. List of GPG Keys used by Aioe.org

 

This document is intended only for those who’re running a real USENET site with regular real-time feeds with other peers. All other people - notably the end users - can safety forget it.

 
1. Introduction
Aioe.org hosts a small USENET hierarchy - aioe.* - with a few text only newsgroups. Since Aioe.org propagates these groups to the other USENET peers that have established a feed with our hosts and an increasing number of sites is starting to carry them, this pages offers all the informations needed to properly handle our hierarchy.
aioe.* is mostly used to provide our users with some sort of helpdesk or message board but if some customer asks for a group with sensible reasons we often agree to create it. Control Messages - except checkgroups - are rare and the traffic volume is low, about a few KBytes of traffic per day. Other useful informations about the aioe.* hierarchy are available in this specific page about it.
 

2. Checkgroup

The complete list of all newsgroups currently included in the aioe.* hierarchy - which is often called checkgroup - is available at http://news.aioe.org/hierarchy/checkgroup.txt. Those sites that are running INND should update their active file with the following commands:

 

$ su news $ wget http://news.aioe.org/hierarchy/checkgroup.txt 
$ /usr/lib/news/bin/docheckgroups <checkgroup.txt | /usr/lib/news/bin/mod-active

 

Those who prefer actsync, should add at the beginning of /etc/news/actsync.ign - after the set of BIG8 hierarchies - the following string:

 

c aioe.*

 

The synchronization is made with

 

$ su news
$ actsync -v 2 -i actsync.ign nntp.aioe.org | /usr/lib/news/bin/mod-active

 

A checkgroup - which is a control message that summarizes the list of all groups currently active - is sent once per month so those who have configured their hosts to process this kind of incoming control articles can safety forget checkgroups after the first initial sync

.

 
3. Moderators

Even if aioe.* doesn't contain at the moment any moderated group, we're planning to offer that kind of service. In order to properly handle messages sent to aioe.* moderated groups, it's needed to add to /etc/news/moderators this entry

 

aioe.*:%s-newsgroup@aioe.org

 

 
4. GPG Key

In order to avoid serious abuses, all control messages sent by aioe.org are signed with a PGP key. We strongly recommend to configure controlchan in order verify the sign of each control article before processing it. Our key - which has got a KeyId number 0x2322A7F8, fingerprint 2203 1AAC 51E7 C7FD 664F 1D80 90DF 6C71 2322 A7F8 and belongs to usenet@aioe.org - is available at http://news.aioe.org/hierarchy/aioe.txt or through every public keyserver. In order to import that key, these are the suggested steps:

 

$ su news
$ wget http://news.aioe.org/hierarchy/aioe.txt
$ gpg --import aioe.txt

 

 

5. Control.ctl

Control.ctl is the configuration file that determines how the news server has to threat the incoming control messages. In order to handle the control articles sent by aioe.org for the aioe.* newgroups, it's needed to add at the end of /etc/news/control.ctl the full contents of http://news.aioe.org/hierarchy/control.ctl in this way

 

$ su news
$ wget http://news.aioe.org/hierarchy/control.ctl
$ cat control.ctl >>/etc/news/control.ctl

 

Since this file includes all informations needed by the newsmasters about each public hierarchy, we reproduce it here:

 

## Aioe
# Contact: usenet@aioe.org
# URL: http://news.aioe.org/hierarchy/
# Admin group: aioe.system
# Key URL: http://news.aioe.org/hierarchy/aioe.txt
# Key ID: 0x2322A7F8
# Key fingerprint: 2203 1AAC 51E7 C7FD 664F 1D80 90DF 6C71 2322 A7F8
# Syncable server: nntp.aioe.org
newgroup:*:aioe.*:drop
rmgroup:*:aioe.*:drop
checkgroups:usenet@aioe.org:aioe.*:verify-usenet@aioe.org
newgroup:usenet@aioe.org:aioe.*:verify-usenet@aioe.org
rmgroup:usenet@aioe.org:aioe.*:verify-usenet@aioe.org

 
6. AntiSpam settings

aioe.* is protected against spam, floods and other massive abuses through NoCeM. When an aioe.* newsgroup is involved in some large abuse, those people who maintain the hierarchy detect by hands which articles have to be deleted than send a NoCem message. If the remote server are configured to accept and process those messages, all offending articles are locally rejected as shown in the NoCem notice. All NoCeM notices pertinent to aioe.* are sent to news.lists.filters and aioe.news.nocem from nocem@aioe.org with type aioe-spam and all messages are signed with the key 0xA9708492 that is available at http://news.aioe.org/hierarchy/nocem.txt
A good guide about NoCem and INND is available at http://wiki.killfile.org/projects/usenet/nocem.
In order to add our NoCem service to an existing server, it's needed to import the Aioe.org NoCem key in the keyring used by perl-nocem:

 

$ su news
$ wget http://news.aioe.org/hierarchy/nocem.txt
$ gpg --no-default-keyring --keyring /etc/news/pgp/ncmring.gpg --import nocem.txt

 

It's also needed to configure /etc/news/nocem.ctl in order to accept the NoCem notices sent by Aioe.org:

 

$ echo "nocem\@aioe.org:*" >>/etc/news/nocem.ctl

 
7. List of GPG Keys used by Aioe.org
pub   1024D/A9708492 2007-09-15 [expires: 2012-09-13]
      Key fingerprint = A7E0 C3DC 2F9F CEA6 76CC  800C 9629 2AD4 A970 8492
uid                  Aioe.org NOCEM key (Aioe.org key used to sign NOCEM messages) <nocem@aioe.org>
sub   1024g/E9EA9F05 2007-09-15 [expires: 2012-09-13]

pub   1024D/2322A7F8 2007-09-17 [expires: 2010-09-16]
      Key fingerprint = 2203 1AAC 51E7 C7FD 664F  1D80 90DF 6C71 2322 A7F8
uid                  usenet@aioe.org (Aioe.org Steering Group) <usenet@aioe.org>

sub   2048g/753B1E28 2007-09-17 [expires: 2010-09-16]