From: Brian <n1uro@n1uro.com>
To: linux-hams@vger.kernel.org
Subject: NetRom stack bug
Date: Tue, 26 Oct 2021 13:53:16 -0400 [thread overview]
Message-ID: <1635270796.2318.2.camel@n1uro.com> (raw)
Greetings;
Is there any status report on the NetRom status bug getting fixed?
Unfortunately many users feel this is a bug within URONode code and it
is NOT. This is a bug where the kernel protocol stack is NOT closing
unused sockets which could in theory make it vulnerable to compromise.
--
I crashed into a dwarf at a traffic light. He said "I'm not
happy." so I asked which one was he.
-----
73 de Brian N1URO
Linux Partner Developer
Decades long Linux SysAdmin, DNS Host, Email Host
IPv6 Certified
URONode, axMail-FAX, HTPPU Ham software developer
Nutmeg VHF NTS Net - Net Manager
reply other threads:[~2021-10-26 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1635270796.2318.2.camel@n1uro.com \
--to=n1uro@n1uro.com \
--cc=linux-hams@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.