Onion: peannyjkqwqfynd24p6dszvtchkq7hfkwymi5by5y332wmosy5dwfaqd.onion
On Thu, 3 Apr 2025 07:11:42 +0200
Gabx <info@tcpreset.invalid> wrote:
Onion: peannyjkqwqfynd24p6dszvtchkq7hfkwymi5by5y332wmosy5dwfaqd.onion
Hmm, I didn't know about this. Being on an anonymous network leaves it
well open to abuse. Do you limit public posting to people you know and
have approved accounts?
ipv6: 2a01:4f8:c0c:2f94::1
On 03.04.2025 07:11 Uhr Gabx wrote:
ipv6: 2a01:4f8:c0c:2f94::1
Connection refused from my system. Please investigate.
Nigel Reed wrote:
On Thu, 3 Apr 2025 07:11:42 +0200No,
Gabx <info@tcpreset.invalid> wrote:
Onion: peannyjkqwqfynd24p6dszvtchkq7hfkwymi5by5y332wmosy5dwfaqd.onion
Hmm, I didn't know about this. Being on an anonymous network leaves it
well open to abuse. Do you limit public posting to people you know and
have approved accounts?
our server intentionally operates as an open-access system: we do not
require registration or explicitly limit posting privileges only to
known users or pre-approved accounts.
However, to prevent abuse and spam effectively, we've implemented strong automated anti-abuse measures, including Cleanfeed, SpamAssassin, and a Hashcash-based proof-of-work mechanism.
A Hashcash token generation mechanism is designed to prevent automated
spam by requiring users to perform computational work (proof-of-work).
The higher the bits value, the greater the effort needed, significantly deterring spammers.
On 03.04.2025 22:10 Uhr Gabx wrote:
It should work now!
Still doesn't.
It should work now!
Thanks!
Nigel Reed wrote:
On Thu, 3 Apr 2025 07:11:42 +0200No,
Gabx <info@tcpreset.invalid> wrote:
Onion: peannyjkqwqfynd24p6dszvtchkq7hfkwymi5by5y332wmosy5dwfaqd.onion
Hmm, I didn't know about this. Being on an anonymous network leaves it
well open to abuse. Do you limit public posting to people you know and
have approved accounts?
our server intentionally operates as an open-access system: we do not
require registration or explicitly limit posting privileges only to
known users or pre-approved accounts.
However, to prevent abuse and spam effectively, we've implemented strong automated anti-abuse measures, including Cleanfeed, SpamAssassin, and a Hashcash-based proof-of-work mechanism.
A Hashcash token generation mechanism is designed to prevent automated
spam by requiring users to perform computational work (proof-of-work).
The higher the bits value, the greater the effort needed, significantly deterring spammers.
We are currently evaluating PyClean https://github.com/crooks/PyClean/tree/master and NoCeM to further
enhance these protections.
Additionally, we will soon implement secure NNTP connections via port
563, supporting TLS v1.2 and v1.3 with mandatory authentication.
Additionally, we actively monitor and moderate public postings to
maintain high standards without sacrificing user privacy or openness.
I understand your suggestion about requiring, for example, email-based authentication and registration as a means of identifying potential
abusers.
However, relying solely on email addresses doesn't necessarily guarantee
a clear or reliable identification of malicious users.
Email addresses are trivially easy for abusers to obtain anonymously or through disposable services, and thus cannot unequivocally distinguish legitimate users from abusers.
Consequently, our technical anti-abuse strategies and active moderation policies offer more practical, robust, and privacy-respecting protection against spam and malicious activities than email-based identification
alone.
Moreover, I believe there's a fundamental misunderstanding regarding the Onion network and spam: spam activities typically rely heavily on
clearnet due to the ease of automated bulk distribution and openness to
mass harvesting techniques.
Conversely, the Onion network, by design, introduces *latency* and complexity—conditions fundamentally incompatible with large-scale spam operations.
Far from facilitating abuse, Tor's nature often discourages spam and
mass attacks by making automated, high-volume transmissions costly and impractical.
I'd be happy to further discuss alternative strategies or enhancements
to address your concerns effectively.
I apologize for my lengthy explanations; however, i anticipated concerns being raised about the onion address and wanted to address them clearly.
Best regards
Gabx
Does news.tcpreset.net offer shell accounts for exteral users?
Given that you provide access via TOR and anonymous remailers using a mail2news gateway, how and where would you implement your "hashcash
proof of work", when there is no direct interaction between the users
and your server infrastructure?
I would suggest that you take a closer look at hashcash implementations, because they can slightly differ from the original. Maybe also useful for you, if you check how Omnimix does it.
https://www.danner-net.de/omom/tutorremailhashcash.htm
Stefan Claas wrote:
I would suggest that you take a closer look at hashcash implementations, because they can slightly differ from the original. Maybe also useful for you, if you check how Omnimix does it.
https://www.danner-net.de/omom/tutorremailhashcash.htm
BTW. I guess you changed something. My article was quoted at the beginning and shows now only the last paragraph. It also seems that you changed something
with the Newsgroups: header, so that it must appears first.
Before these changes, everything worked perfectly.
* Gabx wrote:
Nigel Reed wrote:
On Thu, 3 Apr 2025 07:11:42 +0200No,
Gabx <info@tcpreset.invalid> wrote:
Onion:
peannyjkqwqfynd24p6dszvtchkq7hfkwymi5by5y332wmosy5dwfaqd.onion
Hmm, I didn't know about this. Being on an anonymous network leaves
it well open to abuse. Do you limit public posting to people you
know and have approved accounts?
our server intentionally operates as an open-access system: we do not
require registration or explicitly limit posting privileges only to
known users or pre-approved accounts.
However, to prevent abuse and spam effectively, we've implemented
strong automated anti-abuse measures, including Cleanfeed,
SpamAssassin, and a Hashcash-based proof-of-work mechanism.
A Hashcash token generation mechanism is designed to prevent
automated spam by requiring users to perform computational work
(proof-of-work). The higher the bits value, the greater the effort
needed, significantly deterring spammers.
Given that you provide access via TOR and anonymous remailers using a mail2news gateway, how and where would you implement your "hashcash
proof of work", when there is no direct interaction between the users
and your server infrastructure?
* nobody wrote:
Full quote removed
Thanks!
| Injection-Info: news.tcpreset.net; posting-host="localhost:127.0.0.1";
^^^^^^^^^^^^^^^^^^^
logging-data="389427"; mail-complaints-to="usenet@news.tcpreset.net"
Does news.tcpreset.net offer shell accounts for exteral users?
-6 -sS 2a01:4f8:c0c:2f94::1
On 03.04.2025 07:11 Uhr Gabx wrote:
ipv6: 2a01:4f8:c0c:2f94::1
Connection refused from my system. Please investigate.
Marco Moock wrote:
On 03.04.2025 07:11 Uhr Gabx wrote:
ipv6: 2a01:4f8:c0c:2f94::1
Connection refused from my system. Please investigate.
????
gabriel1@victor:~$ ping6 2a01:4f8:c0c:2f94::1
PING 2a01:4f8:c0c:2f94::1(2a01:4f8:c0c:2f94::1) 56 data bytes
64 bytes from 2a01:4f8:c0c:2f94::1: icmp_seq=1 ttl=53 time=5.16 ms
64 bytes from 2a01:4f8:c0c:2f94::1: icmp_seq=2 ttl=53 time=2.85 ms
64 bytes from 2a01:4f8:c0c:2f94::1: icmp_seq=3 ttl=53 time=3.20 ms
Ray Banana wrote:
* nobody wrote:
Full quote removed
Thanks!
| Injection-Info: news.tcpreset.net;
posting-host="localhost:127.0.0.1"; ^^^^^^^^^^^^^^^^^^^
logging-data="389427";
mail-complaints-to="usenet@news.tcpreset.net"
Does news.tcpreset.net offer shell accounts for exteral users?
No.
Strange things happening.
tcp 0 0 0.0.0.0:119 0.0.0.0:*
LISTEN 1875963/innd
On 05.04.2025 09:29 Uhr Gabx wrote:
tcp 0 0 0.0.0.0:119 0.0.0.0:*
LISTEN 1875963/innd
Here is the problem. inn doesn't listen on the IPv6 general socket (::)
at all. Check the INN settings.
root@news:/var/www/usenet# systemctl restart inn2.service
Job for inn2.service failed because the control process exited with error code.
See "systemctl status inn2.service" and "journalctl -xeu inn2.service" for details.
Marco Moock wrote:
On 05.04.2025 09:29 Uhr Gabx wrote:
tcp 0 0 0.0.0.0:119 0.0.0.0:*
LISTEN 1875963/innd
Here is the problem. inn doesn't listen on the IPv6 general socket
(::) at all. Check the INN settings.
You are right,
i had this commented #sourceaddress6:
i have added the ip 2a01:4f8:c0c:2f94::1
root@news:/var/www/usenet# systemctl restart inn2.service
Job for inn2.service failed because the control process exited with
error code. See "systemctl status inn2.service" and "journalctl
-xeu inn2.service" for details.
What do i do of wrong?
And there is a typo for the Web Interface. It sends as MIME UTF-8 7bit, instead of 8bit.
Es schrieb einmal Stefan Claas:
And there is a typo for the Web Interface. It sends as MIME UTF-8 7bit, instead of 8bit.
7bit or 8bit depends on whether 8-bit characters appear in the body or not. The charset is irrelevant.
What do i do of wrong?
2a01:4f8:c0c:2f94::1 296.838 ms !<4-1> 296.597 ms !<4-1> 296.303 ms ! <4-1>
You have a filter dropping packets, or more likely hetzner has.
Surely hetzner has an FAQ on how to configure ipv6 to suite their
network if they dont auto configure it (which they should)
noel wrote:
2a01:4f8:c0c:2f94::1 296.838 ms !<4-1> 296.597 ms !<4-1> 296.303 msIt's not a filter, but it's hetzner:
!
<4-1>
You have a filter dropping packets, or more likely hetzner has.
root@news:~# cat /etc/netplan/50-cloud-init.yaml network:
version: 2 ethernets:
eth0:
addresses:
- 2a01:4f8:c0c:2f94::1/64 dhcp4: true match:
macaddress: 52:54:a2:02:2c:94
nameservers:
addresses:
- 2a01:4ff:ff00::add:2 - 2a01:4ff:ff00::add:1
routes:
- on-link: true
to: default via: fe80::1
set-name: eth0
Is dhcp6 and/or gateway6 missing?
On 05.04.2025 23:25 Uhr noel wrote:
Surely hetzner has an FAQ on how to configure ipv6 to suite their
network if they dont auto configure it (which they should)
It is NOT Hetzner's fault.
only listens on 0.0.0.0, which means IPv4 only.
[::] is all addresses on IPv6 and IPv4.
It is a config issue on INN,
Alfred Peters wrote:
Es schrieb einmal Stefan Claas:
And there is a typo for the Web Interface. It sends as MIME UTF-8 7bit,
instead of 8bit.
7bit or 8bit depends on whether 8-bit characters appear in the body or not. >> The charset is irrelevant.
In the Web Interface it displays UTF-8 characters properly but then the Usenet posting does not display the charaters correctly in a News Reader.
Es schrieb einmal Stefan Claas:
Alfred Peters wrote:
Es schrieb einmal Stefan Claas:
And there is a typo for the Web Interface. It sends as MIME UTF-8 7bit, instead of 8bit.
7bit or 8bit depends on whether 8-bit characters appear in the body or not.
The charset is irrelevant.
In the Web Interface it displays UTF-8 characters properly but then the Usenet posting does not display the charaters correctly in a News Reader.
Message-ID?
On Sat, 05 Apr 2025 15:27:53 +0200, Marco Moock wrote:
On 05.04.2025 23:25 Uhr noel wrote:
Surely hetzner has an FAQ on how to configure ipv6 to suite their
network if they dont auto configure it (which they should)
It is NOT Hetzner's fault.
and you know this how? since they already said they fixed that problem
maybe, surely its not that hard to configure ipv6 in inn.conf, they
showed it was commented, then stated "fixed", and one does assume
they restarted inn and tested to make sure, else one wouldnt state
"fixed".
You are right,
i had this commented #sourceaddress6:
i have added the ip 2a01:4f8:c0c:2f94::1
root@news:/var/www/usenet# systemctl restart inn2.service Job for
inn2.service failed because the control process exited with error code.
See "systemctl status inn2.service" and "journalctl -xeu inn2.service"
for details.
What do i do of wrong?
Gabx
Gabx wrote:
You are right,
i had this commented #sourceaddress6:
i have added the ip 2a01:4f8:c0c:2f94::1
More precisely I should have shown you this option also commented
#bindaddress6: 2a01:4f8:c0c:2f94::1
and restarting innd:
root@news:/var/www/usenet# systemctl restart inn2.service Job for
inn2.service failed because the control process exited with error
code. See "systemctl status inn2.service" and "journalctl -xeu
inn2.service" for details.
What do i do of wrong?
I didn't think I would have to use ipv6 so frequently but
unfortunately ....
I didn't think I would have to use ipv6 so frequently but unfortunately
....
Gabx
Es schrieb einmal Stefan Claas:
In the Web Interface it displays UTF-8 characters properly but then the
Usenet posting does not display the charaters correctly in a News Reader.
<vsoprv$pbto$1@news.tcpreset.net>
More precisely I should have shown you this option also commented
#bindaddress6: 2a01:4f8:c0c:2f94::1
I didn't think I would have to use ipv6 so frequently but unfortunately
....
I have found this:
https://freeimage.host/i/37Y5n4
I have corrected it with news tcpreset net.
On Mon, 7 Apr 2025, noel wrote:
unless I missed it, I don't recall Gabx confirming above nmap output on
their side of the great firewall. Also don't recall seeing the latest
netstat after they said they fixed it not listening.
I also see tcpreset domain has LE errors - check web redirections,
seems didn't include subdomains on cert generation, but still throws
errors becasue of next point.
DNSSEC conflict, must have upgraded old SHA1 key with 13/2, but not
removed the sha1 key (in most cases since do have a good 13/2 as well,
the sha1 might be ignored, but pedantic test scripts (like one we use
will issue a fail status), as will some services, saying the cert is
not trusted. https://zonecheck.org/zonemaster might be of use
What ports are supposed to be open on ipv6 ?
I only see imap and imaps on ipv6 but you have on ipv4 some 9 services.
if you can shell to that machine lynx https://zonecheck.org (it will
show you your IP, if it gives you an IPv6 display, select port scanner
and run the basic tcp check
I also not sure why you are using inn 2.6.2, thats some 4 years old now
with 2.7.2 current and 2.8 weeks from release IIRC.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 469 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 44:56:56 |
| Calls: | 9,449 |
| Calls today: | 6 |
| Files: | 13,596 |
| Messages: | 6,112,014 |
| Posted today: | 1 |