https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280487
--- Comment #4 from Andre Albsmeier ---
Didn't know about -C being taken (as I am on 14-STABLE). Of course, any free
letter will be fine. Any suggestions?
ID <-> PID: The man page talks about ID for -P and -p. Now that you've
mentioned it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280651
Mark Johnston changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280714
Mark Linimon changed:
What|Removed |Added
Keywords||crash
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280705
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280705
--- Comment #2 from Eirik Oeverby ---
Some rudimentary testing - on my own retro hardware and on copy.sh/v86/ - it
seems that many OSes with IP stacks of BSD origin share this trait. Notable
exceptions are OpenBSD and Windows 2000, but macO
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280518
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #2 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280679
--- Comment #4 from Cullum Smith ---
While I lack the inclination to grok all the arcane details of
termcap/terminfo, after comparing the `infocmp` output for xterm-256color with
a Linux system, I believe I understand the problem.
Termcap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280543
--- Comment #7 from наб ---
I think beside %'d, %lc (%ls) is the only real way to output wide characters
through narrow printf(3) and in that case, that's pretty much exactly what you
want?
This is only an "issue" if you treat the return v
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280705
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280543
--- Comment #6 from Ed Maste ---
(In reply to наб from comment #5)
Yes, I guess this is what printf(3) must do, which makes it somewhat useless
given the existence of multibyte characters.
--
You are receiving this mail because:
You are t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280487
--- Comment #3 from Juraj Lutter ---
If I get it right, it's suitable for situations where the command to be run
daemon()-izes itself, does not have any ability to run in foreground and a
shell wrapper with $! output written into a file is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280679
--- Comment #3 from Cullum Smith ---
Actually, do *not* merge this patch. It fixes color9-color14 but breaks the
display of 256 colors in ncurses.
I'll keep looking.
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280676
John Baldwin changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280651
--- Comment #3 from megaman...@gmail.com ---
I was unsure of the preference of where patches are uploaded, since this site
is probably easier for people to search in the future
But let's keep discussion on GitHub if that's that's (and the p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280676
--- Comment #3 from John Baldwin ---
Looks like macOS uses BSD grep, and it fixed the code to match the manpage.
BSD grep treats '-r' and '-R' as identical, whereas GNU grep uses '-r' to mean
the equivalent of '-rO' in BSD grep and '-R' to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280676
--- Comment #2 from Radosław Piliszek ---
(In reply to Ed Maste from comment #1)
Please note the bug report is not about GNU's grep but FreeBSD's grep where
`-R` = `-r` (indeed, you could replace all `-R` with `-r` in my report and have
it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280558
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280543
--- Comment #5 from наб ---
I mean, idk, probably not? This looks like exactly correct behaviour from
printf(3) (and thus printf(1) I'm pretty sure).
printf(3)'s widths, precisions, and the return value are in bytes (and
wprintf(3)'s would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280676
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280516
--- Comment #4 from Jose Luis Duran ---
(In reply to Mark Johnston from comment #3)
There are two issues:
1. The main issue: blacklistd-helper should discard stderr when invoking the
flush action (it already does for the add action). This
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280671
Mark Johnston changed:
What|Removed |Added
Status|New |Open
--- Comment #3 from Mark John
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280671
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #2 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280518
--- Comment #1 from John Baldwin ---
Presumably in this case all the permissions of regular files are also kind of
whacky for said NFS root? That is, binaries like /bin/ls are owned by a random
user ID and not root:wheel when accessed remo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280667
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280642
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #1 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280651
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280599
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280543
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #4 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280597
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280516
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280487
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280714
Bug ID: 280714
Summary: Kernel panic when unloading hms with hms disabled in
device.hints
Product: Base System
Version: 13.3-RELEASE
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280705
Bug ID: 280705
Summary: 0.0.0.0/32 is equivalent to 127.0.0.1/32, which may be
considered a security flaw
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
Dr. Uwe Meyer-Gruhl changed:
What|Removed |Added
CC||freebsd_em...@congenio.de
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #6 from doktornotor ---
Created attachment 252626
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252626&action=edit
PCAP - working with SA-24:05 reverted
(In reply to Kristof Provost from comment #4)
Relevant captur
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #5 from doktornotor ---
Created attachment 252625
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252625&action=edit
PCAP - broken with SA-24:05 applied
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #4 from Kristof Provost ---
Please include a network capture on the WAN side. `tcpdump -n -i $wan -s0 -w
wan.pcap`
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #3 from doktornotor ---
(In reply to Kristof Provost from comment #1)
This bug is trivially reproducible.
- Dead simple WAN (DHCP) and LAN (static /24).
- The traffic is a simple traceroute from a LAN machine.
- Ruleset attac
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #2 from doktornotor ---
Created attachment 252624
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252624&action=edit
pf ruleset
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
doktornotor changed:
What|Removed |Added
Summary|FreeBSD-SA-24:05 fix breaks |FreeBSD-SA-24:05 fix breaks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
Bug ID: 280701
Summary: FreeBSD-SA-24:05 fix breaks ICMP/ICMP6 (ping,
tracertoute) states handling in pf firewall
Product: Base System
Version: 14.1-RELEASE
Hardware:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280667
s_m...@os.rim.or.jp changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You
44 matches
Mail list logo