The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On Saturday, February 17th, 2024 a
From: "Leon M. Busch-George"
Signed-off-by: Leon M. Busch-George
---
iwinfo_nl80211.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/iwinfo_nl80211.c b/iwinfo_nl80211.c
index 8eab671..6270ef9 100644
--- a/iwinfo_nl80211.c
+++ b/iwinfo_nl80211.c
@@ -2031,7 +2031,9 @@ stat
From: "Leon M. Busch-George"
This prevents potential buffer overflows while writing to the phy name buffer
buffer.
Additionally, truncated data is not returned so consumers don't work with
unterminated data, preventing out-of-bounds access.
Sadly, consumers like lookup_phy or phyname don't the
Hi there :-)
While reviewing code using libiwinfo, I noticed that are no length garantuees
for the size of the phy name buffer.
These patches should help making phy names easier to deal with internally.
The strcpy that copies the internal buffer into the user-supplied buffer can
still overflow.
From: "Leon M. Busch-George"
Typically, returning a char * signifies to callers that they own the buffer.
Signed-off-by: Leon M. Busch-George
---
iwinfo_nl80211.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/iwinfo_nl80211.c b/iwinfo_nl80211.c
index 2ea59
On 2024-02-29 12:56, Ravi Paluri (QUIC) wrote:
Thanks, Paul for the reply.
Can you help us with a sample usage of "ubus subscribe" OR "ubus listen" OR "ubus
monitor", which helps us to learn, "running" flag change to false from true.
I know not whether such is even possible. Start here:
htt
