Newsgroup changes (2021-04-25 to 2021-05-02)

[Rink]

<ftp://ftp.isc.org/pub/usenet/CONFIG/>.
<ftp://ftp.isc.org/pub/usenet/CONFIG/control.ctl>
<ftp://ftp.isc.org/pub/usenet/CONFIG/README>
<ftp://ftp.isc.org/pub/usenet/CONFIG/LOGS/>

Could you please change the ftp:// in these links in :
http://
or
https://
(I think https:// )

Because Firefox stopped accepting ftp:// links.
I downloaded FileZilla, but then I get a warning
that my password will be sent over internet in clear text
(sorry I do not know the exact warning text and it is in Dutch).

If I change ftp:// in https:// my Firefox opens the page
in Firefox without warnings.

Thank you!

Rink

[Adam H. Kerman]

Post by Rink

<ftp://ftp.isc.org/pub/usenet/CONFIG/>.
<ftp://ftp.isc.org/pub/usenet/CONFIG/control.ctl>
<ftp://ftp.isc.org/pub/usenet/CONFIG/README>
<ftp://ftp.isc.org/pub/usenet/CONFIG/LOGS/>

http://
or
https://
(I think https:// )

Please do not make any such change.

Post by Rink
Because Firefox stopped accepting ftp:// links.
I downloaded FileZilla, but then I get a warning
that my password will be sent over internet in clear text
(sorry I do not know the exact warning text and it is in Dutch).

It's anonymous ftp. Your user name is anonymous, and your password is
traditionally your email address. There is absolutely no security
implication.

Sometimes you have to use pftp rather than ftp depending on your setup.

Post by Rink
If I change ftp:// in https:// my Firefox opens the page
in Firefox without warnings.

But ftp sites have the advantage over http sites in that the user is
given access to the index. A Web site must generate a site index, which
they tend not to do.

Access to the directory index is critical at ftp.isc.org.

[Julien ÉLIE]

Hi Adam,

Post by Adam H. Kerman

Post by Rink

<ftp://ftp.isc.org/pub/usenet/CONFIG/>.

http://
or
https://
(I think https:// )

But ftp sites have the advantage over http sites in that the user is
given access to the index. A Web site must generate a site index, which
they tend not to do.
Access to the directory index is critical at ftp.isc.org.

Hopefully the site index is also generated via https access:
https://ftp.isc.org/pub/usenet/CONFIG/

A downloads.isc.org alias is also possible:
https://downloads.isc.org/pub/usenet/CONFIG/

[Richard Kettlewell]

Julien ÉLIE
L'espace d'un matin. »
(François de Malherbe)

I've got my terminal emulation xfce4 set to translate UTF-8, and I'm
still getting improperly translated or nonprinting characters in your
last name and your .sigfile. In all these decades, I've yet to see your
name rendered correctly on my terminal emulation.
Ã<89>LIE
The <89> displays because something didn't translate, and it looks like
there are some nonprinting characters in your .sigfile.

The bytes on the wire are C3 89, which is UTF-8 for LATIN CAPITAL LETTER
E WITH ACUTE. Perhaps your newsreader is misinterpreting it?

[Adam H. Kerman]

Post by Richard Kettlewell

Julien ÉLIE
L'espace d'un matin. »
(François de Malherbe)

I've got my terminal emulation xfce4 set to translate UTF-8, and I'm
still getting improperly translated or nonprinting characters in your
last name and your .sigfile. In all these decades, I've yet to see your
name rendered correctly on my terminal emulation.
Ã<89>LIE
The <89> displays because something didn't translate, and it looks like
there are some nonprinting characters in your .sigfile.

The bytes on the wire are C3 89, which is UTF-8 for LATIN CAPITAL LETTER
E WITH ACUTE. Perhaps your newsreader is misinterpreting it?

My newsreader doesn't interpret anything, leaving it to the terminal
emulation. I know his last name starts with E, but it displays as A with
inverted breve, plus the untranslated <89>.

It doesn't seem to matter what emulation I use.

[Richard Kettlewell]

Post by Adam H. Kerman

Post by Richard Kettlewell
The bytes on the wire are C3 89, which is UTF-8 for LATIN CAPITAL
LETTER E WITH ACUTE. Perhaps your newsreader is misinterpreting it?

My newsreader doesn't interpret anything, leaving it to the terminal
emulation. I know his last name starts with E, but it displays as A with
inverted breve, plus the untranslated <89>.
It doesn't seem to matter what emulation I use.

Something after the bytes on the wire and before the pixels on your
screen is misinterpreting it. I can only guess at which layer is getting
it wrong, but at least one of them is.

LATIN CAPITAL LETTER A WITH INVERTED BREVE is C8 82 in UTF-8, which
would require quite a bizarre misinterpretation to reach from C3. On the
other hand LATIN CAPITAL LETTER A WITH BREVE is C3 in ISO-8859-2 and
ISO-8859-16, so if that’s what you’re actually seeing then it implies a
very straightforward misinterpretation somewhere.

[Retro Guy]

Post by Adam H. Kerman

Post by Richard Kettlewell

Julien ÉLIE
L'espace d'un matin. »
(François de Malherbe)

I've got my terminal emulation xfce4 set to translate UTF-8, and I'm
still getting improperly translated or nonprinting characters in your
last name and your .sigfile. In all these decades, I've yet to see your
name rendered correctly on my terminal emulation.
Ã<89>LIE
The <89> displays because something didn't translate, and it looks like
there are some nonprinting characters in your .sigfile.

The bytes on the wire are C3 89, which is UTF-8 for LATIN CAPITAL LETTER
E WITH ACUTE. Perhaps your newsreader is misinterpreting it?

My newsreader doesn't interpret anything, leaving it to the terminal
emulation. I know his last name starts with E, but it displays as A with
inverted breve, plus the untranslated <89>.
It doesn't seem to matter what emulation I use.

I just tried trn (in kde) and notice exactly the same issue.

I had this exact problem with a web interface I develop, which was also displaying this way. I finally figured out that I was decoding only the name (I was testing using messasges from Julien :). When I changed the code to decode the entire From: line and then entire body at one time, the problem disappeared and it now works just fine.

Is it possible that trn is doing this also? I have no idea but thought I'd mention it as I've seen the problem myself.

[Adam H. Kerman]

Post by Retro Guy

Post by Adam H. Kerman

Post by Richard Kettlewell

Julien ÉLIE
L'espace d'un matin. »
(François de Malherbe)

I've got my terminal emulation xfce4 set to translate UTF-8, and I'm
still getting improperly translated or nonprinting characters in your
last name and your .sigfile. In all these decades, I've yet to see your
name rendered correctly on my terminal emulation.
Ã<89>LIE
The <89> displays because something didn't translate, and it looks like
there are some nonprinting characters in your .sigfile.

The bytes on the wire are C3 89, which is UTF-8 for LATIN CAPITAL LETTER
E WITH ACUTE. Perhaps your newsreader is misinterpreting it?

My newsreader doesn't interpret anything, leaving it to the terminal
emulation. I know his last name starts with E, but it displays as A with
inverted breve, plus the untranslated <89>.
It doesn't seem to matter what emulation I use.

I just tried trn (in kde) and notice exactly the same issue.
I had this exact problem with a web interface I develop, which was also
displaying this way. I finally figured out that I was decoding only the
name (I was testing using messasges from Julien :). When I changed the
code to decode the entire From: line and then entire body at one time,
the problem disappeared and it now works just fine.
Is it possible that trn is doing this also? I have no idea but thought
I'd mention it as I've seen the problem myself.

It's not possible that trn is doing anything because trn translates
nothing. It merely outputs to the screen.

In the profile in my account on the host, I've got TERM set to vt102, so
I suppose it could be the local emulation too perfectly implemented that
terminal. With Julien, there always seem to be characters that get
misinterpreted that I don't notice when I followup to anyone use using
UTF-8.

[Julien ÉLIE]

Hi Adam,

Post by Adam H. Kerman
With Julien, there always seem to be characters that get
misinterpreted that I don't notice when I followup to anyone use using
UTF-8.

Pretty strange. I'm only using French characters in my signatures, like
French quotation marks preceded or followed by a non-breakable space.

Did you try to read French newsgroups, especially messages encoded in UTF-8?
Is the checkgroups for fr.* appearing fine in your newsreader?

And what for internationalized newsgroup names in UTF-8?
I have for instance trigofacile.test.ᾅ and trigofacile.test.υτφ8 in my
news server (news.trigofacile.com)? Happy testings :-)

[Adam H. Kerman]

Post by Julien ÉLIE
Did you try to read French newsgroups, especially messages encoded in UTF-8?
Is the checkgroups for fr.* appearing fine in your newsreader?

That's a good idea.

Post by Julien ÉLIE
And what for internationalized newsgroup names in UTF-8?
I have for instance trigofacile.test.ៅ and trigofacile.test.υτφ8 in my
news server (news.trigofacile.com)? Happy testings :-)

Thanks

[Retro Guy]

Post by Julien ÉLIE
Hi Adam,

Post by Adam H. Kerman
With Julien, there always seem to be characters that get
misinterpreted that I don't notice when I followup to anyone use using
UTF-8.

Pretty strange. I'm only using French characters in my signatures, like
French quotation marks preceded or followed by a non-breakable space.
Did you try to read French newsgroups, especially messages encoded in UTF-8?
Is the checkgroups for fr.* appearing fine in your newsreader?

I notice the same with other messages. For example 'Michael Bäuerle' in
news.software.readers does not decode properly in trn.

It's not just French. I have some Russian users and koi8-r also does not
decode properly in trn (in my testing anyway)

Retro Guy

[Retro Guy]

Trust me on this: trn4 isn't mishandling anything because it has nothing
to do with translation nor display. All it does is pass the character
codes to the terminal emulation. You must set the terminal emulation to
decode and the host's LOCALE has to be set to the same translation as
the terminal emulation.
There simply is no graphical interface in trn so there's nothing for trn
to screw up.

Yes, I shouldn't have said that trn is not displaying properly, it's just that
it is the reader I was using. What I had noticed is that it's not just Julien's
posts, but encoded lines in other messages that don't display properly also, so
nothing specific to his messages.

[Marcel Logen]

Post by Julien ÉLIE
And what for internationalized newsgroup names in UTF-8?
I have for instance trigofacile.test.ᾅ and trigofacile.test.υτφ8 in my
news server (news.trigofacile.com)? Happy testings :-)

Thank you!

BTW, FYI:

| t20$ printf '%s\r\n' 'QUIT' | openssl s_client -connect news.trigofacile.com:563 | openssl x509 -issuer -subject -noout -dates
| depth=0 C = FR, ST = Some-State, O = news.trigofacile.com, OU = news.trigofacile.com, CN = news.trigofacile.com
| verify error:num=10:certificate has expired
| notAfter=Sep 16 14:19:32 2019 GMT
| verify return:1
| depth=0 C = FR, ST = Some-State, O = news.trigofacile.com, OU = news.trigofacile.com, CN = news.trigofacile.com
| verify error:num=18:self signed certificate
| verify return:1
| depth=0 C = FR, ST = Some-State, O = news.trigofacile.com, OU = news.trigofacile.com, CN = news.trigofacile.com
| verify error:num=18:self signed certificate
| verify return:1
| DONE
| issuer= /C=FR/ST=Some-State/O=news.trigofacile.com/OU=news.trigofacile.com/CN=news.trigofacile.com
| subject= /C=FR/ST=Some-State/O=news.trigofacile.com/OU=news.trigofacile.com/CN=news.trigofacile.com
| notBefore=Sep 15 14:19:32 2018 GMT
| notAfter=Sep 16 14:19:32 2019 GMT
| t20$

Marcel

[Julien ÉLIE]

Hi Marcel,

Post by Marcel Logen
| verify error:num=10:certificate has expired
| notAfter=Sep 16 14:19:32 2019 GMT

Oh, you're right. Now fixed.

"make cert" (with INN) works like a charm for a self-signed certificate,
just re-rested again :-)

% make cert
umask 077 ; \
/usr/bin/openssl req -new -x509 -nodes \
-out /home/news/etc/cert.pem -days 366 \
-keyout /home/news/etc/key.pem
Generating a RSA private key
[...]

And that's done, installed at the right path.


% printf '%s\r\n' 'QUIT' | openssl s_client -connect
news.trigofacile.com:563 | openssl x509 -issuer -subject -noout -dates
verify error:num=18:self signed certificate
notBefore=Jun 11 15:15:07 2021 GMT
notAfter=Jun 12 15:15:07 2022 GMT

[Julien ÉLIE]

Hi Retro Guy,

Post by Retro Guy
I had this exact problem with a web interface I develop, which was also
displaying this way. I finally figured out that I was decoding only the
name (I was testing using messages from Julien :).

Glad my messages serve for testing purposes :-)

Post by Retro Guy
When I changed the code to decode the entire From: line and then entire body at one time,
the problem disappeared and it now works just fine.

The From: line is MIME-encoded using Quoted-Printable. And the body in
raw UTF-8.

[Retro Guy]

On Mon, 7 Jun 2021 15:55:33 +0200

Post by Julien ÉLIE
Hi Retro Guy,

Post by Retro Guy
I had this exact problem with a web interface I develop, which was also
displaying this way. I finally figured out that I was decoding only the
name (I was testing using messages from Julien :).

Glad my messages serve for testing purposes :-)

And also plenty of useful/helpful information :)

It was your messages that caught my attention first. I was decoding, but it wasn't quite right, and I saw that with display of your name, so I just kept testing with it.

Once I got that working, display of other messages all worked correctly and now I almost know what I'm doing.

Retro Guy