user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Julien ÉLIE <>
To: Eric Wong <>,,
Subject: Re: NNTP COMPRESS clients? RFC 8054
Date: Mon, 15 Jul 2019 22:17:49 +0200
Message-ID: <> (raw)
In-Reply-To: <20190715012546.ljpdiavoesixy3sp@whir>

Hi Eric,

> 	git clone
> 	(nntp-compress branch)

"sysread may call SSL_read, and SSL_read may buffer extra
data in userspace which can be returned via sysread without
making another read(2) syscall.  This makes it it possible for
select() to block indefinitely since select() only knows about
buffers in the kernel, not userspace."

Nice catch!  Hopefully it will be fixed in Net::NNTP.
For your information, INN also suffered from that annoying bug in 
earlier 2.4.x versions.  That was why we finally by-passed the use of 
select() because it generated dead connections.  And also implemented a 
timeout alarm signal around SSL_read().

+  croak("NNTP connection already compressed ($comp)") if $comp;
+  croak("$alg not supported (only 'DEFLATE')") if $alg ne 'DEFLATE';

Note that these messages have different response codes:  502 for the 
first one, 503 for the last one.

+  can_deflate() or die $nodeflate_warn;
+  $err == Z_OK or die "Inflate->new failed: $err\n";
+  $err == Z_OK or die "Deflate->new failed: $err\n";

It should be a 403 response code, and then the connections goes on 
uncompressed (same remark found in your patch against public-inbox-nntpd).

> My plan is to keep public-inbox-nntpd read-only; since (AFAIK)
> NNTP lacks good spam filtering

Isn't Cleanfeed good enough for your needs?

I am also aware of a use of SpamAssassin with INN.  Maybe it would 
better fit your expectations?

Installation guide in French:

> and most news->mail gateways get shut down because of that.

Too bad :-(

> I also don't want to hassle him or anybody at with
> migrating, given how little load it sees:

I see...  Too bad too :-(

Julien ÉLIE

« Ta remise sur pied lui a fait perdre la tête ! » (Astérix)

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190706044942.wmgjwbfy4vwntogu@dcvr>
     [not found] ` <>
2019-07-15  1:25   ` Eric Wong
2019-07-15 20:17     ` Julien ÉLIE [this message]
2019-09-21 20:35       ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone