[GH-ISSUE #506] [Question] Rsync won't record the rsynced file names in ttyrec #128

New issue

Open

opened 2026-05-07 00:19:16 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:19:16 +02:00

Owner

Originally created by @SherifNagy on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/506

Just updated to latest release 3.17.00 to test the rsync functionality and it works great, however, I noticed that in the ttyrec session, it won't list the files names that being rsynced, is this expected?

just shows something like

>>> Hello sherif, running rsync through the bastion on XXX@XXX.XXX.XXX.XXX:22...
>>> Done, 44043 bytes uploaded, 40645437 bytes downloaded

Originally created by @SherifNagy on GitHub (Oct 23, 2024). Original GitHub issue: https://github.com/ovh/the-bastion/issues/506 Just updated to latest release 3.17.00 to test the rsync functionality and it works great, however, I noticed that in the ttyrec session, it won't list the files names that being rsynced, is this expected? just shows something like ``` >>> Hello sherif, running rsync through the bastion on XXX@XXX.XXX.XXX.XXX:22... >>> Done, 44043 bytes uploaded, 40645437 bytes downloaded ```

BreizhHardware added the

answered

label

2026-05-07 00:19:16 +02:00

BreizhHardware commented

2026-05-07 00:19:16 +02:00

Author

Owner

@speed47 commented on GitHub (Dec 4, 2024):

Hello, sorry for the response delay!

Yes, what you're seeing is expected, this is because the file list is not generated (or seen) on the bastion, nor on the remote server where you're rsync from/to, but on your local rsync client.

Using the bastion, you have:

(local rsync client) --ssh-> (bastion with rsync plugin) --ssh-> (remote server running rsync server)

The filelist display is generated by the local rsync client, and outputted to your terminal directly. What's flowing through ssh to the bastion and to the remote server is the binary rsync protocol directly.

If having the output list recorded is critical to you, you would need to ensure the rsync client is launched under ttyrec itself, which means something like:

(local computer) --ssh-> (bastion) --ssh-> (machine launching the rsync client) --ssh-> (bastion) --ssh-> (remote server running rsync server)

This way, the first bastion will have a ttyrec with the output of what is displayed on the rsync client machine's terminal.
Note that if your only concern is having this list, the second bastion is not even needed (if the rsync client has direct ssh access to the rsync server, and if this is allowed by your security/network constraints, that is)

@speed47 commented on GitHub (Dec 4, 2024): Hello, sorry for the response delay! Yes, what you're seeing is expected, this is because the file list is not generated (or seen) on the bastion, nor on the remote server where you're rsync from/to, but on your local rsync client. Using the bastion, you have: ``` (local rsync client) --ssh-> (bastion with rsync plugin) --ssh-> (remote server running rsync server) ``` The filelist display is generated by the local rsync client, and outputted to your terminal directly. What's flowing through ssh to the bastion and to the remote server is the binary rsync protocol directly. If having the output list recorded is critical to you, you would need to ensure the rsync client is launched under ttyrec itself, which means something like: ``` (local computer) --ssh-> (bastion) --ssh-> (machine launching the rsync client) --ssh-> (bastion) --ssh-> (remote server running rsync server) ``` This way, the first bastion will have a ttyrec with the output of what is displayed on the rsync client machine's terminal. Note that if your only concern is having this list, the second bastion is not even needed (if the rsync client has direct ssh access to the rsync server, and if this is allowed by your security/network constraints, that is)

BreizhHardware referenced this issue

2026-05-07 00:20:03 +02:00

[PR #128] [MERGED] feat: add --(in|ex)clude to groupList/accountList #260