Notably Minix, Windows...
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
Yet, I am unsure current versions of INN still work fine with very old >versions listed...
https://scorpio.home.xs4all.nl/diablo/faq.html
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
Our server is running a 3.16 kernel and glibc 2.19.
https://scorpio.home.xs4all.nl/diablo/faq.html
That FAQ hasn't been updated since 2002, alas. There are still some of us running Diablo today, however. I think everyone runs it on Linux.
The latest "stable" release was somewhere between 2007 and 2009 (5.1-REL), but most people will run 6-CUR (latest update in 2017). I still maintain
some patches at http://www.miquels.cistron.nl/diablo/ .
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
Well diablo consists of 'diablo' (storage and transit/feeding) and 'dreaderd' (reader frontend, overview database, article numbering etc). I've replaced the 'diablo' part with my own https://github.com/miquels/nntp-rs almost everywhere, but I'm probably the only one running it :) (on Debian 10).
Hi Miquel,
https://scorpio.home.xs4all.nl/diablo/faq.html
That FAQ hasn't been updated since 2002, alas. There are still some of us
running Diablo today, however. I think everyone runs it on Linux.
The latest "stable" release was somewhere between 2007 and 2009 (5.1-REL), >> but most people will run 6-CUR (latest update in 2017). I still maintain
some patches at http://www.miquels.cistron.nl/diablo/ .
There was an old discussion a few years ago in the diablo-users
mailing-list to move the project to Github, and officially release
6-CUR. I believe it would be a good thing for Diablo.
Well diablo consists of 'diablo' (storage and transit/feeding) and 'dreaderd'
(reader frontend, overview database, article numbering etc). I've replaced >> the 'diablo' part with my own https://github.com/miquels/nntp-rs almost
everywhere, but I'm probably the only one running it :) (on Debian 10).
Oh, nice job! Looks like it is very efficient (2000 articles received / >second).
I know one here who will be happy to see a news server coded in Rust :-)
I've had a look at your capabilities; I think SASL should not be
advertised (at least one mechanism is needed) contrary to AUTHINFO than
can be advertised without being followed by any keyword.
Hi Thomas,
I have compiled a list of news servers for Unix-like systems and
Windows on <https://th-h.de/net/usenet/servers/> (German language).
Great list, thanks!
--
Julien ÉLIE
« Si, si, si… Avec des si, on mettrait Lutèce en amphore ! » (Vacancier)
Hi Matthew,
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
Our server is running a 3.16 kernel and glibc 2.19.
OK, is it an INN, and which version?
I did not manage to "telnet chiark.greenend.org.uk 119" to have the banner.
Our server is running a 3.16 kernel and glibc 2.19.
Julien ÉLIE <iulius@nom-de-mon-site.com.invalid> writes:
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
Our server is running a 3.16 kernel and glibc 2.19.
Hi all,
A quick survey to know whether current supported systems are the right
ones or if we should consider new systems according to your needs.
https://www.eyrie.org/~eagle/software/inn/docs/install.html
"""
INN has been confirmed to work on the following operating systems:
AIX 4.3
FreeBSD 2.2.x and up
HP-UX 10.20 and up
Linux 2.x (tested with libc 5.4, glibc 2.0 and up)
Mac OS X 10.2 and up
NetBSD 1.6 and up
OpenBSD 2.8 and up
SCO 5.0.4 (tested with gcc 2.8.1, cc)
Solaris 2.5.x and up
UnixWare 7.1
UX/4800 R11 and up
"""
Yet, I am unsure current versions of INN still work fine with very old versions listed...
https://scorpio.home.xs4all.nl/diablo/faq.html
"""
Diablo was originally developed on FreeBSD and will perform very well on
it. Success has been reported on:
FreeBSD
BSD/OS
Linux
Solaris
"""
Any comments about these lists?
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
Several years ago I was successfully running INN on Windows with Cygwin.
IIRC it was Windows XP. I was just using it for some testing but didn’t notice any bugs.
I was succefully running (before 2003) Inn on Windows with Cygwin.
Don't remember wich version. Probably 2.5.x or below.
Several years ago I was successfully running INN on Windows with Cygwin.
IIRC it was Windows XP. I was just using it for some testing but didn’t
notice any bugs.
Interesting to know, thanks!
Do you remember which INN version it was? (2.5.x or 2.6.x ?)
Well, the question now is whether INN still works on recent Windows
systems (Server 2019 or Windows 10 notably).
For neodome.net, you're server is actually used to send abusive
cancels on the fr.* hierarchie.
I've send an email to your abuse address.
@+
Interesting to know, thanks!
Do you remember which INN version it was? (2.5.x or 2.6.x ?)
Well, the question now is whether INN still works on recent Windows
systems (Server 2019 or Windows 10 notably).
Sorry Gerard, there is no such thing as “abusive cancels”. Users are free to cancel any message they don’t want to see on their server.
If your server is also executing those cancel messages, and it’s not
what you want, I’d suggest you to implement some sort of
authentication such as Cancel-Lock/Cancel-Key, PGP signatures, or
NoCeM. Actually, this is the very group where you can ask for advice
on how to implement it. If you wish, I can provide you with Cancel-Lock/Cancel-Key Perl library.
Gerald Niel <gerald.niel+spam@gegeweb.invalid> wrote:
For neodome.net, you're server is actually used to send abusive
cancels on the fr.* hierarchie.
I've send an email to your abuse address.
@+
Sorry Gerard, there is no such thing as "abusive cancels". Users are
free to cancel any message they don't want to see on their server. If
your server is also executing those cancel messages, and it's not what
you want, I'd suggest you to implement some sort of authentication such
as Cancel-Lock/Cancel-Key, PGP signatures, or NoCeM. Actually, this is
the very group where you can ask for advice on how to implement it. If
you wish, I can provide you with Cancel-Lock/Cancel-Key Perl library.
. . .
Is there something to do on server side for cancel-lock ?
Or client side is enough.
. . .
Gerald Niel <gerald.niel+news@gegeweb.org> wrote:
Is there something to do on server side for cancel-lock ?
Or client side is enough.
If it's a first-party cancel (sent by the author of the article), isn't
he supposed to send the authenticated cancel through the same server
that injected the article being cancelled to begin with?
I don't agree. That any user can send a cancel message is just a matter
of syntax and use of a server that doesn't prohibit a user from sending a cancel message. Just because a user isn't prevented from doing something doesn't mean it's not abuse on Usenet.
Even if a News server has implemented authenticated cancellations, an automated process to send a significant number of cancels at once could
be a denial-of-service attack, and I'd hope you would agree that's abuse
of Usenet that should be prevented.
Is there something to do on server side for cancel-lock ?
Or client side is enough.
On server side, I'm using cleanfeed. So, now, I refuse cancel comming
from some severs.
Adam H. Kerman <ahk@chinet.com> wrote:
I don't agree. That any user can send a cancel message is just a matter
of syntax and use of a server that doesn't prohibit a user from sending a >>cancel message. Just because a user isn't prevented from doing something >>doesn't mean it's not abuse on Usenet.
Computers are very simple and straightforward things. They do exactly
what they are programmed to do. If some news server out there is
processing control messages without any authentication then it's doing >exactly what administrator wants it to do. I don't know and have no
means to find out if other administrators want to process those cancel >messages or not. What if they do want to process them? . . .
Your server, your rules. It's not my place to tell to disallow them. I
am observing, nevertheless, that third-party cancels that aren't issued
to address unsolicited advertising or spam are abuse on Usenet. News administrator don't always have to deal with abuse on Usenet.
Now back to the subject of this group:
To prevent that my own messages that are neither spam, nor messages
with shocking or illegal content (for the French jurisdiction I depend
on) are abusively canceled so I added the header Cancel-Lock with my
client (slrn).
I'm just one of the members of the committee of management of the
hierarchy fr.*, that the person who abuses this server took for target
like all the members of the committee.
This is at a time when we are trying, with our new Control, to
simplify our management rules to take into account the drop in media
traffic.
My question is, is this sufficient as a preventive measure, to prevent
my articles from being cancelled or that the committee announcements
are cancelled?
[...]
I want to allow my users to be able to cancel their own messages.
Or
possibly cancel another message by following the rules and that meet
the cancellation criteria on the network and in particular on the
fr.* hierarchy.
Some newsreaders can't create Cancel-Locks/Keys themselves. Most german servers therefore create them for all their users automatically.[…]
On his excellent website he gave some good links : <http://trigofacile.com/>
In French : <http://www.bortzmeyer.org/8315.html>
If so, we could talk about it in French on fr.*?
On fr.* there is a badly named thread on that subject : <rrgcka$s3k$1@dont-email.me>
It's a pity to have to do that...
Le Samedi 23 janvier 2021 à 12:20 UTC, Michael Bäuerle écrivait sur news.software.nntp :
[…]
Some newsreaders can't create Cancel-Locks/Keys themselves. Most german[…]
servers therefore create them for all their users automatically.
thanks for the reply, it's more clear now.
If I want to implement this on the server side, with Inn, there are
docs?
I searched, I couldn't find any that explain how to do it. Even less
in French, unfortunately.
Maybe Julien E. has that?
If so, we could talk about it in French on fr.*?
I already use NoCem.
And Cleanfeed, configured now to refuse cancel comming from some
servers.
Most german servers ignore cancel requests without authentication, but execute them if e.g. a matching Cancel-Key is provided.
Some newsreaders can't create Cancel-Locks/Keys themselves. Most german servers therefore create them for all their users automatically.
I have already read. But no references for a how-to with Inn.
Following Michael's discussion:
[...]
Some newsreaders can't create Cancel-Locks/Keys themselves. Most german servers therefore create them for all their users automatically.
Let's do it in France too!
<politics clich="on">
I see that even in Usenet, Germany is leading the way in Europe.
France always a follower :-)
</politics clich="off">
Hi all,
A quick survey to know whether current supported systems are the right
ones or if we should consider new systems according to your needs.
https://www.eyrie.org/~eagle/software/inn/docs/install.html
https://netz-rettung-recht.de/archives/1473-INN-Cancel-Lock-und-Cancel-Key.html
You can try an automatic translation to French.
Basically, you have to add Cancel-Lock support to both nnrpd and innd
via Perl hooks:
https://code.th-h.de/?p=usenet/INN.git;a=tree;f=filter
Basically, you have to add Cancel-Lock support to both nnrpd and innd
via Perl hooks:
https://code.th-h.de/?p=usenet/INN.git;a=tree;f=filter
Thanks.
Works fine to add Cancel-Lock and Cancel-Key headers with
filter_nnrpd.pl.
Now, I'll update cleanfeed.local.
No need to understand German, source code is enough. ;)
https://scorpio.home.xs4all.nl/diablo/faq.html
That FAQ hasn't been updated since 2002, alas. There are still some of us >>> running Diablo today, however. I think everyone runs it on Linux.
The latest "stable" release was somewhere between 2007 and 2009 (5.1-REL), >>> but most people will run 6-CUR (latest update in 2017). I still maintain >>> some patches at http://www.miquels.cistron.nl/diablo/ .
There was an old discussion a few years ago in the diablo-users
mailing-list to move the project to Github, and officially release
6-CUR. I believe it would be a good thing for Diablo.
Tell me about it, I started that discussion :) You know what,
I just sent a message to the list. Let's see if it still works.
I've had a look at your capabilities; I think SASL should not be
advertised (at least one mechanism is needed) contrary to AUTHINFO that
can be advertised without being followed by any keyword.
It isn't advertised as long as you don't set the SASL capability bit.
Lots of the other capabilities aren't advertised either right now,
for the same reason: no actual implementation yet.
Hi all,
A quick survey to know whether current supported systems are the right
ones or if we should consider new systems according to your needs.
https://www.eyrie.org/~eagle/software/inn/docs/install.html
"""
INN has been confirmed to work on the following operating systems:
AIX 4.3
FreeBSD 2.2.x and up
HP-UX 10.20 and up
Linux 2.x (tested with libc 5.4, glibc 2.0 and up)
Mac OS X 10.2 and up
NetBSD 1.6 and up
OpenBSD 2.8 and up
SCO 5.0.4 (tested with gcc 2.8.1, cc)
Solaris 2.5.x and up
UnixWare 7.1
UX/4800 R11 and up
"""
Yet, I am unsure current versions of INN still work fine with very old versions listed...
https://scorpio.home.xs4all.nl/diablo/faq.html
"""
Diablo was originally developed on FreeBSD and will perform very well on it. Success has been reported on:
FreeBSD
BSD/OS
Linux
Solaris
"""
Any comments about these lists?
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
As for INN more specifically, are there people here running INN 2.6.x on:
- AIX 4.3 or higher?
- HP-UX 10.20 or higher?
- SCO 5 and UnixWare 7 or higher? (or now Xinuos OpenServer?)
- UX/4800 R11 or higher?
I am tempted to drop the old list of versions for INN, and just mention
the ones where a successful build has really been tested. Which would
give:
"""
INN has been confirmed to work on recent versions of the following
operating systems:
AIX (including 7.2)
FreeBSD (including 12.1)
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
macOS (including 11)
NetBSD (including 9.0)
OpenBSD (including 6.8)
Oracle Solaris (including 10 and 11)
INN may also work on other operating systems like HP-UX, OpenServer or UnixWare but has not been confirmed to.
"""
Or do you have other expectations?
On 1/16/21 2:32 AM, Julien ÉLIE wrote:
Hi all,
A quick survey to know whether current supported systems are the right
ones or if we should consider new systems according to your needs.
https://www.eyrie.org/~eagle/software/inn/docs/install.html
"""
INN has been confirmed to work on the following operating systems:
AIX 4.3
FreeBSD 2.2.x and up
HP-UX 10.20 and up
Linux 2.x (tested with libc 5.4, glibc 2.0 and up)
Mac OS X 10.2 and up
NetBSD 1.6 and up
OpenBSD 2.8 and up
SCO 5.0.4 (tested with gcc 2.8.1, cc)
Solaris 2.5.x and up
UnixWare 7.1
UX/4800 R11 and up
"""
Yet, I am unsure current versions of INN still work fine with very old
versions listed...
https://scorpio.home.xs4all.nl/diablo/faq.html
"""
Diablo was originally developed on FreeBSD and will perform very well on
it. Success has been reported on:
FreeBSD
BSD/OS
Linux
Solaris
"""
Any comments about these lists?
If you know other news servers which work on other systems, please tell!
Notably Minix, Windows...
As for INN more specifically, are there people here running INN 2.6.x on:
- AIX 4.3 or higher?
- HP-UX 10.20 or higher?
- SCO 5 and UnixWare 7 or higher? (or now Xinuos OpenServer?)
- UX/4800 R11 or higher?
I am tempted to drop the old list of versions for INN, and just mention
the ones where a successful build has really been tested. Which would
give:
"""
INN has been confirmed to work on recent versions of the following
operating systems:
AIX (including 7.2)
FreeBSD (including 12.1)
Linux (including 4.19 and 5.10 kernels, glibc 2.28)
macOS (including 11)
NetBSD (including 9.0)
OpenBSD (including 6.8)
Oracle Solaris (including 10 and 11)
INN may also work on other operating systems like HP-UX, OpenServer or
UnixWare but has not been confirmed to.
"""
Or do you have other expectations?
csiph.com is FreeBSD (on ZFS, which works pretty nice for tradspool with >compression)
I maintain the inn port (packaging) on FreeBSD and would say we only
expect supported releases, so 11.4 is the oldest we need to support >https://www.freebsd.org/security/#sup
csiph.com is FreeBSD (on ZFS, which works pretty nice for tradspool with compression)
csiph.com is FreeBSD (on ZFS, which works pretty nice for tradspool with compression)
I maintain the inn port (packaging) on FreeBSD and would say we only
expect supported releases, so 11.4 is the oldest we need to support https://www.freebsd.org/security/#sup
Le vendredi 22 janvier 2021 à 20:40 GMT, Adam H. Kerman écrivait sur news.software.nntp :
Your server, your rules. It's not my place to tell to disallow them. I
am observing, nevertheless, that third-party cancels that aren't issued
to address unsolicited advertising or spam are abuse on Usenet. News
administrator don't always have to deal with abuse on Usenet.
Sorry, my English is not fluent enough.
I don't know if what I write really means what I want to express and
would express in my native language (French).
And please feel free to redirect this topic to the most appropriate
group.
From what I can see, the server news.deodome.net is an open server, it
can be used to read and post on usenet without authentication.
It can be used to post anonymously (I have no problem with that), but
with no way to trace the source if it is abused:
Injection-Info: neodome.net; mail-complaints-to="abuse@neodome.net"
The abuse address doesn't reply.
And its administrator answers that it's a feature and not a bug when a
abuse is reported about illegitimate cancel.
I will therefore, for my part, take more radical measures than simply refusing cancellations from this server. And report it to the
French-speaking newsmaster community. They will see on their side what
they think is good to do to protect themselves and their users from
possible abuses that could come from this server.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 218:50:35 |
| Calls: | 6,621 |
| Calls today: | 3 |
| Files: | 12,171 |
| Messages: | 5,317,787 |