wolfssh/src
John Safranek 2bfdbac2b3 Carry the EOF status through SFTP and SCP
wolfSSH_SFTP_buffer_send() and ScpStreamSend() keep driving the worker when the
peer half-closes. Both return any negative status, so a WS_EOF would have
aborted a transfer that is still perfectly able to finish: the peer closed its
sending direction, not ours.

- wolfSSH_SFTP_buffer_read() reports every negative peek but a rekey instead of
  spending a receive on it. A drained channel at EOF, a dead session and a
  channel that is gone all mean no more data can arrive, and the poll only
  overwrites the latched cause with WS_WANT_READ or blocks on a peer that has
  hung up.
- A rekey is not a drained channel: peek reports it before it looks at the
  buffer at all, so that one still needs the poll.
- DoScpRequest() reads its own EOF case the same way as the rest.
2026-08-31 11:53:29 -05:00
..
agent.c
certman.c Fix the cppcheck findings 2026-08-28 18:12:59 -05:00
include.am
internal.c Reject teardown on an unconfirmed channel 2026-08-31 11:53:29 -05:00
io.c
keygen.c Fix the cppcheck findings 2026-08-28 18:12:59 -05:00
log.c
misc.c
ossh.c
port.c Fix the cppcheck findings 2026-08-28 18:12:59 -05:00
ssh.c Reject teardown on an unconfirmed channel 2026-08-31 11:53:29 -05:00
wolfscp.c Carry the EOF status through SFTP and SCP 2026-08-31 11:53:29 -05:00
wolfsftp.c Carry the EOF status through SFTP and SCP 2026-08-31 11:53:29 -05:00
wolfterm.c