I took another look, and this turns out to be simpler than I thought.
The problem is that we explicitly attempt to parse the server match
config (an unnecessary copypasta from sshd -T code path). But, in the
generator, we only care about options that affect the listening
addresses, and the match section is for modifying settings on a per-
connection basis.

Hence, the fix for this is to just not attempt to parse the match
config, as it requires a connection spec, which we cannot have at
generator time.

** Changed in: openssh (Ubuntu Oracular)
       Status: Confirmed => Triaged

** Changed in: openssh (Ubuntu Noble)
       Status: New => Triaged

** Changed in: openssh (Ubuntu Noble)
   Importance: Undecided => Medium

** Changed in: openssh (Ubuntu Noble)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076023

Title:
  Failed to apply 'Match' directive in sshd_config with sshd-socket-
  generator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2076023/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to