public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Javier Martinez <tazok.id0@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Linux ephemeral port range defaults to "broken".
Date: Sun, 10 Aug 2025 23:59:40 +0200	[thread overview]
Message-ID: <e3da75e7-2b75-40eb-bdbd-35b12b30ffea@gmail.com> (raw)
In-Reply-To: <107b3j7$ikm$1@ciao.gmane.io>


[-- Attachment #1.1.1: Type: text/plain, Size: 952 bytes --]

El 10/8/25 a las 23:39, Grant Edwards escribió:
> On 2025-08-10, Javier Martinez <tazok.id0@gmail.com> wrote:
> 
>> PD: nc -l myip myultracriticalport breaks your countermeasure of
>> using proc to avoid port use (ip_local_reserved_ports)
> 
> You can not run "nc -l myip myultracriticalport" on the system in
> question.
> 
>> is part of the solution, not the solution itself. You need iptables
>> in all cases.
> 
> No, I do not.
> 
> --
> Grant
> 
> 
> 
> 
> 
> 
> 
> 
You can do this:

Create iptable rule that allows using this port for one user with -m owner
If it's not this user who is trying to use the port, use  LOG with a 
concrete string with a DROP default policy.
Instruct syslog-ng with a rule using the "concrete string" to write a 
file monitored by inotify that execs one script that locates the 
offending command and kills it.

If not any troll with access to anything can use any port over 1024

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2025-08-10 22:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07  1:38 [gentoo-user] Linux ephemeral port range defaults to "broken" Grant Edwards
2025-08-07  3:49 ` Alexandru N. Barloiu
2025-08-07  6:44 ` Zhixu Liu
2025-08-07 13:04 ` Javier Martinez
2025-08-07 13:12 ` Javier Martinez
2025-08-07 14:01   ` [gentoo-user] " Grant Edwards
2025-08-07 14:25     ` Javier Martinez
2025-08-07 14:37     ` Javier Martinez
2025-08-10  1:54 ` [gentoo-user] " Grant Taylor
2025-08-10 21:13   ` [gentoo-user] " Grant Edwards
2025-08-10 21:25     ` Javier Martinez
2025-08-10 21:35       ` Grant Edwards
2025-08-10 21:28     ` Grant Edwards
2025-08-10 21:30     ` Javier Martinez
2025-08-10 21:39       ` Grant Edwards
2025-08-10 21:43         ` Javier Martinez
2025-08-10 22:55           ` Grant Edwards
2025-08-10 23:12             ` Javier Martinez
2025-08-10 21:59         ` Javier Martinez [this message]
2025-08-10 23:00           ` Grant Edwards

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=e3da75e7-2b75-40eb-bdbd-35b12b30ffea@gmail.com \
    --to=tazok.id0@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox