[Bug 261349] Modernise hier(7)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261349

Graham Perrin  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|grahamper...@freebsd.org
   See Also||https://github.com/freebsd/
   ||freebsd-src/pull/763

--- Comment #16 from Graham Perrin  ---
 updated. 

PR 763 draft begun in GitHub.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

--- Comment #1 from Yuri Pankov  ---
There are 2 possible issues here:

1. Running "man -S 1p 1 grep" displays the grep(1) man page -- explicitly
specifying mansect overrides -S/MANSECT.
2. "No manual entry for 1p" -- 1p is missing from the default sections list, so
it's treated as man page name and not section.

What is the real use case here that is broken?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 258010] kqueue shortcoming for desktop usage

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258010

Mark C  changed:

   What|Removed |Added

 CC||f...@peralex.com

--- Comment #4 from Mark C  ---
This is an issue that I've been struggling with lately too, also with
syncthing.  The kqueue workaround works for smaller directory trees, but is
unworkable for large collections of files.  The number of file descriptors can
be increased, but with millions of files to watch, the system quickly becomes
unusable.

There was at least one previous attempt to add inotify-type functionality to
FreeBSD in a GSoC project, but I don't know what happened with that:

https://www.freebsd.org/status/report-2010-04-2010-06.html#File-System-Changes-Notification

A long-running discussion on the forums of the differences between inotify
(Linux), fsevents (Mac), and kqueue is here:

https://forums.freebsd.org/threads/inotify-for-freebsd.38162/page-3

I also wonder if something could be implemented based on the existing audit
framework, which seems to allow file alterations to be watched, although it
doesn't have an easy API to use from code.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271704] O_PATH and acl_get_fd_np doesn't work on FreeBSD 13(.2) and causes vfs_zfsacl in Samba to fail

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271704

--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=1e26f443cd2b8775ba50207aa9645ec12ead9e8a

commit 1e26f443cd2b8775ba50207aa9645ec12ead9e8a
Author: Konstantin Belousov 
AuthorDate: 2023-05-29 15:07:18 +
Commit: Konstantin Belousov 
CommitDate: 2023-06-05 08:35:01 +

__acl_get_fd(2), __acl_aclcheck_fd(2): enable for O_PATH filedescriptors

PR: 271704

(cherry picked from commit 7a292504bad8467915f072f0576b2a07c76de1f5)

 lib/libc/sys/open.2 | 3 ++-
 sys/kern/vfs_acl.c  | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

--- Comment #2 from Mohamed Akram  ---
The reason for filing this issue is to allow using custom sections, such as
man1p (used on Linux for POSIX man pages). As can be seen in the first
instance, because man is ignoring MANSECT it thinks 1p is a page and not a
section so this is impossible.

The second variation I posted is just to illustrate the same bug in a different
way. Fixing the first will likely fix this. It's more simple and
straightforward if what is considered a section is what the user specifies,
falling back to the default otherwise. This will lead to consistent behavior
instead of special casing "default sections" (this is how it works on Linux as
well).

Also, FYI, setting MANSECT in a file doesn't work at all because it reads the
config file after already deciding on the default list.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

--- Comment #3 from Mohamed Akram  ---
Created attachment 242606
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242606&action=edit
patch to fix the issue

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271835

Bug ID: 271835
   Summary: seeing inode issues/ file corruption in freeBSD13 on
long run
   Product: Base System
   Version: 13.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: meetshams...@gmail.com

Hi,
Looks like file inode is getting corrupted on writing multiple times on one of
the files.
Initially writing in same folder (incoming) as outbox is working fine but in
long run (~20-30days) observing file corruption issues for same folder/file.
Note : for this we are using haystack with luecene database, which uses this
folder.

Post reboot it runs fsck and then it becomes fine.

3727 Jun  2 13:15:19 sma1 kernel: ** Processing journal entries.
3728 Jun  2 13:15:19 sma1 kernel: /dev/da0p9: ino 2620925 nlink manipulation
error, new 18446744073709551600, old 0
3729 Jun  2 13:15:19 sma1 kernel: /dev/da0p9: UNEXPECTED SU+J INCONSISTENCY
3730 Jun  2 13:15:19 sma1 kernel: /dev/da0p9: INTERNAL ERROR: GOT TO reply()
3731 Jun  2 13:15:19 sma1 kernel: /dev/da0p9: UNEXPECTED SOFT UPDATE
INCONSISTENCY; RUN fsck MANUALLY.
3732 Jun  2 13:15:19 sma1 kernel: ** /dev/da0p9
3733 Jun  2 13:15:19 sma1 kernel: ** SU+J Recovering /dev/da0p9

OR

Jun  3 05:36:21 sma1 kernel:
Jun  3 05:36:21 sma1 kernel: DIR I=885977 CONNECTED. PARENT WAS I=2266482
Jun  3 05:36:21 sma1 kernel:
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: DIR I=359730 CONNECTED. PARENT WAS I=2266482
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: UNREF DIR  I=351356  OWNER=root MODE=40755
Jun  3 05:36:21 sma1 kernel: SIZE=512 MTIME=May 25 08:48 2023
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: RECONNECT? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: DIR I=351356 CONNECTED. PARENT WAS I=2266482
Jun  3 05:36:21 sma1 kernel:
Jun  3 05:36:21 sma1 kernel: UNREF DIR  I=349918  OWNER=root MODE=40755
Jun  3 05:36:21 sma1 kernel: SIZE=512 MTIME=May 25 08:48 2023
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: RECONNECT? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: DIR I=349918 CONNECTED. PARENT WAS I=2266482
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: ** Phase 4 - Check Reference Counts
Jun  3 05:36:21 sma1 kernel: LINK COUNT FILE I=350699  OWNER=root MODE=100644
Jun  3 05:36:21 sma1 kernel: SIZE=254 MTIME=Jan 13 11:18 2022  COUNT 16 SHOULD
BE 12
Jun  3 05:36:21 sma1 kernel: ADJUST? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: LINK COUNT FILE I=351284  OWNER=root MODE=100644
Jun  3 05:36:21 sma1 kernel: SIZE=1205 MTIME=Jan 13 11:18 2022  COUNT 16 SHOULD
BE 12
Jun  3 05:36:21 sma1 kernel: ADJUST? yes
Jun  3 05:36:21 sma1 kernel:
Jun  3 05:36:21 sma1 kernel: LINK COUNT DIR I=2266482  OWNER=root MODE=40755
Jun  3 05:36:21 sma1 kernel: SIZE=512 MTIME=May 25 08:48 2023  COUNT 18 SHOULD
BE 2
Jun  3 05:36:21 sma1 kernel: ADJUST? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: ** Phase 5 - Check Cyl groups
Jun  3 05:36:21 sma1 kernel: FREE BLK COUNT(S) WRONG IN SUPERBLK
Jun  3 05:36:21 sma1 kernel: SALVAGE? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: BLK(S) MISSING IN BIT MAPS
Jun  3 05:36:21 sma1 kernel: SALVAGE? yes
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: 209770 files, 591288 used, 3041595 free (0 frags,
3041595 blocks, 0.0% fragmentation)
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: * FILE SYSTEM STILL DIRTY *
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: * FILE SYSTEM WAS MODIFIED *
Jun  3 05:36:21 sma1 kernel: 
Jun  3 05:36:21 sma1 kernel: * PLEASE RERUN FSCK *
Jun  3 05:36:21 sma1 kernel: mount: /dev/da0p9: R/W mount of /data denied.
Filesystem is not clean - run fsck. Forced mount will invalidate journal
contents: Operation not permitted
Jun  3 05:36:21 sma1 kernel: da0 recovering is not needed
Jun  3 05:36:21 sma1 kernel: da0p9 resized

# find / -inum 2266482
/data/aggregator/incoming_queue/0/1minute/42145427B09C8E182260-02F017004D1B

Is there way to resolve it without rebooting the system? or is there any patch
available for this fix in FreeBSD13.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #3 from Sergey Fedorov  ---
Created attachment 242607
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242607&action=edit
An instance of USB errors

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #4 from Sergey Fedorov  ---
(In reply to Graham Perrin from comment #2)

I do not think so, since it happens on two different machines which otherwise
work perfectly fine.
However I add a pic now of USB-related issues.

Please notice those are not central to the matter though. Freezing happens
regardless.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #5 from Sergey Fedorov  ---
Created attachment 242608
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242608&action=edit
USB error upon intro screen load

This happened 2–3 times out of numerous install attempts. I.e. not consistent,
nevertheless did happen on both machines.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #6 from Sergey Fedorov  ---
I will re-upload pics, compression killed them. Sorry.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

Sergey Fedorov  changed:

   What|Removed |Added

 Attachment #242607|0   |1
is obsolete||

--- Comment #7 from Sergey Fedorov  ---
Created attachment 242609
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242609&action=edit
USB errors when booting (resolution fixed)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

Sergey Fedorov  changed:

   What|Removed |Added

 Attachment #242608|0   |1
is obsolete||

--- Comment #8 from Sergey Fedorov  ---
Created attachment 242610
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242610&action=edit
USB error upon intro screen load

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #9 from Sergey Fedorov  ---
Created attachment 242611
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242611&action=edit
Booted system on PMG5 2.3

Installed and booted system on PowerMac G5 2.3 DC. No errors on boot, but it
was badly freezing even when entering login/password and every other command.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #10 from Sergey Fedorov  ---
(In reply to Graham Perrin from comment #2)

> How are the HDD(s) and SSD(s) connected?

Native SATA bus connection. I.e. not a PCIe card, FW drive or anything else
non-default.
SSD were a direct replacement for HDDs. The PowerMac where I had FreeBSD
installed now has HDD in upper bay which is used for FreeBSD (I moved macOS
onto SSD).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #11 from Sergey Fedorov  ---
(In reply to Warner Losh from comment #1)

I don’t have spare DVDs around to check that. Is there a way to make install
image recognizable from a FW drive? That works fine for MacOS installation, but
I could not get it work for FreeBSD. USB drive might be an option too, late
PowerMacs support USB booting, unofficially.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

--- Comment #4 from Mohamed Akram  ---
Comment on attachment 242606
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242606
patch to fix the issue

--- man.sh.orig 2023-06-05 09:11:06.617877000 +
+++ man.sh  2023-06-05 09:43:16.432524000 +
@@ -562,7 +562,7 @@
P)  MANPAGER=$OPTARG ;;
S)  MANSECT=$OPTARG ;;
a)  aflag=aflag ;;
-   d)  debug=$(( $debug + 1 )) ;;
+   d)  ;; # handled in man_setup
f)  fflag=fflag ;;
h)  man_usage 0 ;;
k)  kflag=kflag ;;
@@ -603,7 +603,7 @@
fi

IFS=:
-   for sect in $man_default_sections; do
+   for sect in $MANSECT; do
if [ "$sect" = "$1" ]; then
decho "Detected manual section as first arg: $1"
MANSECT="$1"
@@ -619,6 +619,15 @@
 # Usage: man_setup
 # Setup various trivial but essential variables.
 man_setup() {
+   local cmd_arg
+   # Parse the debug flag prior to everything
+   OPTIND=1
+   while getopts ':d' cmd_arg; do
+   case "${cmd_arg}" in
+   d)  debug=$(( $debug + 1 )) ;;
+   esac
+   done
+
# Setup machine and architecture variables.
if [ -n "$mflag" ]; then
MACHINE_ARCH=${mflag%%:*}
@@ -787,8 +796,8 @@
trim "${line#MANCONFIG}"
config_local="$tstr"
;;
-   # Set variables in the form of FOO_BAR
-   *_*[\ \ ]*) var="${line%%[\ \   ]*}"
+   # Set other variables
+   *[\ \   ]*) var="${line%%[\ \   ]*}"
trim "${line#$var}"
eval "$var=\"$tstr\""
decho "Parsed $var" 3
@@ -1008,12 +1017,12 @@
 }

 do_man() {
+   man_setup "$@"
man_parse_args "$@"
if [ -z "$pages" -a -z "${Kflag}" ]; then
echo 'What manual page do you want?' >&2
exit 1
fi
-   man_setup

if [ ! -z "${Kflag}" ]; then
# Short circuit because -K flag does a sufficiently

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

Mohamed Akram  changed:

   What|Removed |Added

 Attachment #242606|0   |1
is obsolete||

--- Comment #5 from Mohamed Akram  ---
Created attachment 242612
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242612&action=edit
improved patch

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 136994] [patch] ifconfig(8) print carp mac address

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136994

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 263604] ifconfig: Low performance with many interface/IP

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263604

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

Mohamed Akram  changed:

   What|Removed |Added

 Attachment #242612|0   |1
is obsolete||

--- Comment #6 from Mohamed Akram  ---
Created attachment 242613
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242613&action=edit
fix issues in last patch

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 173871] [gif] process of 'ifconfig gif0 create hangs' when if_gif_load exists in /etc/loader.conf and 'device gif' exists in kernel config.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173871

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 255597] Feature request: allow ifconfig & route to run in jail context from host system

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255597

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
 Status|New |In Progress

--- Comment #1 from Alexander V. Chernikov  ---
ifconfig(8) support was added in
https://cgit.freebsd.org/src/commit/sbin/ifconfig?id=7e49aa86a2824e76e9d9becf61db12066bc0d79d
.
route(8) support patch: https://reviews.freebsd.org/D40377

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 255597] Feature request: allow ifconfig & route to run in jail context from host system

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255597

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

Mohamed Akram  changed:

   What|Removed |Added

 Attachment #242613|0   |1
is obsolete||

--- Comment #7 from Mohamed Akram  ---
Created attachment 242614
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242614&action=edit
fix whatis and apropos

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 262690] "driver bug: Unable to set devclass" for atrtc

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262690

John F. Carr  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 201466] ifconfig called from ruby shell class causes kernel panic

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201466

Alexander V. Chernikov  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed
 CC||melif...@freebsd.org

--- Comment #9 from Alexander V. Chernikov  ---
I'm sorry we didn't root caused it in reasonable time. Epair handling/creation
code changed significantly at least two times since FreeBSD 10. Also, FreeBSD
10.2 EOL happened 5 years ago.
I'm going to close this one. Please do reopen the issue if you encounter the
crash during epair creation on any of the supported FreeBSD version.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271839] crypto/openssh: Status of CVE-2023-28531

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271839

Bug ID: 271839
   Summary: crypto/openssh: Status of CVE-2023-28531
   Product: Base System
   Version: 12.4-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: pascal.bry...@hostpoint.ch

Since 03/17/2023 a critical vulnerability in openssh 8.9 up to 9.2 has been
reported:
https://www.openwall.com/lists/oss-security/2023/03/15/8

OpenSSH versions prior to 9.3 are susceptible to a vulnerability which when
successfully exploited could lead to disclosure of sensitive information,
addition or modification of data, or Denial of Service (DoS).

How is the status of this security-flaw?
According to https://nvd.nist.gov/vuln/detail/CVE-2023-28531 it has been rated
as 9.8/critical

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271839] crypto/openssh: Status of CVE-2023-28531

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271839

pascal.bry...@hostpoint.ch changed:

   What|Removed |Added

 CC||sect...@freebsd.org
  Flags||maintainer-feedback?(sectea
   ||m...@freebsd.org)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 217815] ifconfig wrap around line not indented

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217815

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
   Assignee|b...@freebsd.org|n...@freebsd.org

--- Comment #1 from Alexander V. Chernikov  ---
I agree it would be nice to see the indented options, when looking in the
long-list capabilities in a small shell window.
Unfortunately, I don't see how it can be implemented in a compatible fashion.
Tons of scripts assume ifconfig(8) has specific output format and splitting
options flag into multiple lines would cause the breakage for some users.

Given I don't see any reasonable way forward, I'll probably have to close it in
a ~week timeframe. Please do reply if you can think of any way that would
improve the visual representation while preserving compatibility.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 233554] ifconfig - Add feature to list interfaces summary.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233554

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
 CC||melif...@freebsd.org

--- Comment #2 from Alexander V. Chernikov  ---
I'd say that ability to provide the "concise" view of the large number of
interfaces is a desired thing.
However, there are many different variations of how this "concise" view should
look like and what should it contain. Even across the vendors (Cisco vs
Juniper, for example), the outputs varies.
I'd rather invest in the solution that allows to construct these views easily.
For example, enhancing ifconfig(8) with libxo may provide easily-parsable json
output that can be used to construct the view shown above. To my knowledge, we
don't have it funded, so I'm not sure if it can happen anytime soon.

If you have a different approach in mind, or have some patches, or are
considering to support of the feature development, please feel free to discuss.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 261572] ifconfig(8): extend formatting of MAC addresses to dotted

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261572

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
   Assignee|b...@freebsd.org|melif...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271843] ppp can crash due to wrapping subtract in FsmRecvEchoReq()

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271843

Bug ID: 271843
   Summary: ppp can crash due to wrapping subtract in
FsmRecvEchoReq()
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: r...@lcs.mit.edu
 Attachment #242617 text/plain
 mime type:

Created attachment 242617
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242617&action=edit
tickle wrapping subtract in ppp's FsmRecvEchoReq()

The follow HDLC frame sent to ppp causes it to dereference a null bp
pointer:

7e
c0 21   -- PROTO_LCP
09 ff 00 03 -- code=9 EchoReply, id=255, length=3
22 96   -- crc
7e

The null bp arises in fsm_Input() in src/usr.sbin/ppp/fsm.c:

  bp = mbuf_Read(bp, &lh, sizeof lh);

mbuf_Read() returns null if it consumes all of the data, which is the
case for the above frame, since sizeof(lh) is four and only the four
bytes 09 ff 00 03 are available.

For the above frame, the null dereference happens in FsmRecvEchoReq().
That function has a length check that could have caught this problem:

  if (lcp && ntohs(lhp->length) - sizeof *lhp >= 4) {

But the ntohs() returns unsigned 3, and the sizeof yields unsigned 4,
so the subtract wraps to unsigned 0x, so the code in
the if statement is executed and tries to dereference bp.

Here's a backtrace from the attached demo:

#0  0x0003e43c in FsmRecvEchoReq (fp=0x407f71e8, lhp=0x3fdd00, 
bp=0x0) at fsm.c:962
#1  0x0003c974 in fsm_Input (fp=0x407f71e8, bp=0x0) at fsm.c:1096
#2  0x0004c4be in lcp_Input (bundle=0x97338 , 
l=0x407f7000, bp=0x407fd300) at lcp.c:1307
#3  0x0005002c in Despatch (bundle=0x97338 , 
l=0x407f7000, bp=0x407fd300, proto=49185) at link.c:381
#4  0x0004fefe in link_PullPacket (l=0x407f7000, 
buf=0x407fa140
"~\377\377~\377\365\275\276\275\177\371\365]\177\346\370\334\354\370\325\346\205\351\326\345\370\370\374\374E|\365\234\314\314\326\346\365\305\346\377\377~\300!\t\377",
len=64, b=0x97338 )
at link.c:323
#5  0x00062b30 in physical_DescriptorRead (d=0x407f7f78, 
bundle=0x97338 , fdset=0x410069c0) at physical.c:569
#6  0x0003221e in datalink_Read (d=0x407f2000, 
bundle=0x97338 , fdset=0x410069c0) at datalink.c:474
#7  0x0001a6e2 in bundle_DescriptorRead (
d=0x97338 , bundle=0x97338 , 
fdset=0x410069c0) at bundle.c:546
#8  0x000548a0 in DoLoop (bundle=0x97338 )
at main.c:661
#9  0x00053d92 in main (argc=3, argv=0x3feb70) at main.c:535

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271839] crypto/openssh: Status of CVE-2023-28531

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271839

Ed Maste  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|ema...@freebsd.org
 CC||ema...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271820] libalias's AliasHandleQuestion() can run off the end of a ppp packet

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271820

--- Comment #1 from Robert Morris  ---
Also:

The subtract in libalias's ValidateUdpLength() can wrap to an unsigned
huge number if ip_len is less than ip_hl<<2. This causes the two
"dlen < ..." tests to be false, which causes the UDP packet to pass
muster even if uh_ulen is bigger than the packet size.

size_t dlen;
dlen = ntohs(pip->ip_len) - (pip->ip_hl << 2);
if (dlen < sizeof(struct udphdr))
return (NULL);
if (!MF_ISSET(pip) && dlen < ntohs(ud->uh_ulen))
return (NULL);

So an HDLC frame like this will also cause AliasHandleQuestion() to
read off the end of the packet buffer and perhaps crash.

7e 00 21 72 ff 00 00 ff ff e0 00 ff 11 00 89 39 9f 7a 3d 7f ff ff 7c
11 72 7e

(gdb) print/x *pip
$6 = {ip_hl = 0x2, ip_v = 0x7, ip_tos = 0xff, ip_len = 0x0, ip_id = 0x, 
  ip_off = 0xe0, ip_ttl = 0xff, ip_p = 0x11, ip_sum = 0x8900, ip_src = {
s_addr = 0x3d7a9f39}, ip_dst = {s_addr = 0x7c7f}}

(gdb) print/x *ud
$4 = {uh_sport = 0x11ff, uh_dport = 0x8900, uh_ulen = 0x9f39, uh_sum = 0x3d7a}

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 264205] freebsd-update: Fails to upgrade 12.1-RELEASE to 12.2-RELEASE or 13.0-RELEASE: The update metadata index is correctly signed, but failed an integrity check.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264205

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #3 from Ed Maste  ---
Is this reproducible when attempting to update to 12.4 or 13.2?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271830] man: ignores MANSECT and -S

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271830

--- Comment #8 from Mohamed Akram  ---
Please ignore the patches, I've created a PR instead -
https://github.com/freebsd/freebsd-src/pull/764.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271820] libalias's AliasHandleQuestion() can run off the end of a ppp packet

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271820

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2718
   ||43

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271843] ppp can crash due to wrapping subtract in FsmRecvEchoReq()

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271843

Ed Maste  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2718
   ||20

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271728] libunbound uses deprecated SSL_CTX_set_ecdh_auto

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271728

Ed Maste  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

--- Comment #1 from Ed Maste  ---
commit dc103686348d3205733a2c77e7d2ccbff6691022
Author: Ed Maste 
Date:   Tue May 30 14:28:44 2023 -0400

unbound: avoid calling deprecated OpenSSL function

SSL_CTX_set_ecdh_auto is deprecated and has no effect (for reference see
   
https://github.com/openssl/openssl/commit/2ecb9f2d18614fb7b7b42830a358b7163ed43221).

As unbound's config.h is manually maintained just turn off
HAVE_DECL_SSL_CTX_SET_ECDH_AUTO so that the deprecated function won't
be called.

Reviewed by:ngie
Sponsored by:   The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D40341

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271615] Update base system OpenSSL to 3.0.x

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271615
Bug 271615 depends on bug 271728, which changed state.

Bug 271728 Summary: libunbound uses deprecated SSL_CTX_set_ecdh_auto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271728

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271615] Update base system OpenSSL to 3.0.x

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271615

Ed Maste  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2716
   ||56

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271615] Update base system OpenSSL to 3.0.x

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271615

--- Comment #18 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=e730066a64e60b3ba39b7143aa40b5ba1e9c3949

commit e730066a64e60b3ba39b7143aa40b5ba1e9c3949
Author: Pierre Pronchery 
AuthorDate: 2023-06-01 19:07:23 +
Commit: Ed Maste 
CommitDate: 2023-06-05 17:48:05 +

decryptcore: Request the OpenSSL 1.1 API

OPENSSL_API_COMPAT can be used to specify the OpenSSL API version in
use for the purpose of hiding deprecated interfaces and enabling
the appropriate deprecation notices.

This change is a NFC while we're still using OpenSSL 1.1.1 but will
avoid deprecation warnings upon the switch to OpenSSL 3.0.

A future update may migrate to use the OpenSSL 3.0 APIs.

PR: 271615
Reviewed by:emaste
Sponsored by:   The FreeBSD Foundation

 sbin/decryptcore/Makefile | 1 +
 1 file changed, 1 insertion(+)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271835

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|f...@freebsd.org

--- Comment #1 from Graham Perrin  ---
> 13.1-STABLE

Which version, exactly? 

uname -aKU

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271853] pkgbase conflicts betweet *-dev and *lib32-dev with pkgconf data

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271853

Bug ID: 271853
   Summary: pkgbase conflicts betweet *-dev and *lib32-dev with
pkgconf data
   Product: Base System
   Version: 13.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: free...@igalic.co

when trying to install all but packages, except for -dbg and kernel packages, I
get the following conflicts:


Checking integrity... done (5 conflicting)
  - FreeBSD-utilities-dev-13.snap20230605162509 [FreeBSD-base] conflicts with
FreeBSD-utilities-dev-lib32-13.snap20230605162509 [FreeBSD-base] on
/usr/libdata/pkgconfig/libusb-0.1.pc
  - FreeBSD-libmagic-dev-13.snap20230605162509 [FreeBSD-base] conflicts with
FreeBSD-libmagic-dev-lib32-13.snap20230605162509 [FreeBSD-base] on
/usr/libdata/pkgconfig/libmagic.pc
  - FreeBSD-openssl-dev-13.snap20230605162509 [FreeBSD-base] conflicts with
FreeBSD-openssl-dev-lib32-13.snap20230605162509 [FreeBSD-base] on
/usr/libdata/pkgconfig/libcrypto.pc
  - FreeBSD-runtime-dev-13.snap20230605162509 [FreeBSD-base] conflicts with
FreeBSD-runtime-dev-lib32-13.snap20230605162509 [FreeBSD-base] on
/usr/libdata/pkgconfig/zlib.pc
  - FreeBSD-liblzma-dev-lib32-13.snap20230605162509 [FreeBSD-base] conflicts
with FreeBSD-liblzma-dev-13.snap20230605162509 [FreeBSD-base] on
/usr/libdata/pkgconfig/liblzma.pc
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 262 package(s) will be affected (of 0 checked):

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271853] pkgbase conflicts betweet *-dev and *lib32-dev with pkgconf data

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271853

Mina Galić  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|pkgb...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271854] pkgbase: cannot install FreeBSD-clibs-dev

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271854

Bug ID: 271854
   Summary: pkgbase: cannot install FreeBSD-clibs-dev
   Product: Base System
   Version: 13.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: free...@igalic.co

at least not over an existing system:

root@builder:~ # pkg install FreeBSD-clibs-dev
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
FreeBSD-clibs-dev: 13.snap20230605162509 [FreeBSD-base]

Number of packages to be installed: 1

The process will require 101 MiB more space.

Proceed with this action? [y/N]: y
[builder] [1/1] Installing FreeBSD-clibs-dev-13.snap20230605162509...
[builder] [1/1] Extracting FreeBSD-clibs-dev-13.snap20230605162509: 100%
pkg: Fail to rename /usr/include/c++/v1/.pkgtemp.__string.h9UvBQARenW2 ->
/usr/include/c++/v1/__string:Not a directory
root@builder:~ #

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271854] pkgbase: cannot install FreeBSD-clibs-dev

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271854

Mina Galić  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|pkgb...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

drk  changed:

   What|Removed |Added

 CC||drkatthel...@yahoo.com

--- Comment #12 from drk  ---
In attempting to install FreeBSD on PPC I found that utilizing the 13.2 DVD iso
with a G5 1.8 Ghz single processor and Nvidia FX5200, the install was smooth
and rapid, working nicely in text mode (but no success on the graphic side).
Moving forward I attempted an install of 13.2 on my favored device, a G5 1.8
Ghz dual processor with an ATI 9600XT card, but the install was painfully
slow... marginal graphic support (card is "supported"). So not to be thwarted,
I pulled out my last remaining G5, an identical G5 dual 1.8 with the 9600 card
and attempted the same install... once again, the process was incredibly slow
with the same outcome observed as with the first dual. Just to confirm my
suspicion, I wiped the drive on the original G5 single processor and began an
install. Once again, with the single, the process was quick and smooth.  So
basically I found 13.2 very workable on a G5 single.  However, it has been my
experience and that of others that install on a multiprocessor PPC is
exceedingly challenging and as noted by opening poster renders 13.2 essentially
unusable on these devices.
Good news:  Swapping in a 9600Xt card into the G5 single has yielded fully
functional FreeBSD on PPC.
Bad news:  13.2 would currently seem to be a no go on the multiprocessor
devices.
Hopeful that this may addressed and remedied to some extent.
P.S.  all drives standard HDD.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 271607] 14.0-RELEASE metabug

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271607

Graham Perrin  changed:

   What|Removed |Added

 Depends on||271772


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271772
[Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict)
failed
-- 
You are receiving this mail because:
You are the assignee for the bug.