What were you trying to do that didn't work?

When executing a command through ForceCommand, I would expect that the exit code of the command reflects on the client side.
This is the case, except for commands dying because of a signal, which in that case reflects as "255" on the client side, instead of "128+signumber".

What is the impact of this issue to you?

Issues knowing why a command failed.

Please provide the package NVR for which the bug is seen:

openssh-8.7p1 (RHEL9)
openssh-9.8p1 (Fedora 41)

How reproducible is this bug?:

Always

Steps to reproduce

1. Define a Match block forcing the command in /etc/ssh/sshd_config and restart sshd

   Match User user
       ForceCommand $SSH_ORIGINAL_COMMAND

2. Execute a command through ssh from a client system

   $ ssh user@localhost sleep 1234

3. From another shell, kill the command

   $ pkill -HUP sleep

Expected results

Exit code 129

Actual results

Exit code 255