RolandK
2026-Apr-26 11:04 UTC
rsync-ssl buffering problem - gnutls-cli issue being fixed with "--blocking-io"
Hello, rsync-ssl currently suffers from an issue with recent changes in openssl. gnutls-cli (other option for transport besides stunnel) also has an issue. from the manpage: ? ? ? ?This script also supports a --type=gnutls option, but at the time of this release the gnutls-cli command was dropping output, making it unusable.? If that bug has been fixed ? ? ? ?in your version, feel free to put gnutls into an exported RSYNC_SSL_TYPE environment variable to make its use the default. i have found that for gnutls-cli, the problem goes away when adding "--blocking-io" to rsync. anyhow, with gnutls-cli transfer is dead slow. i'm currently working on support for socat and ncat as ssl transport? options in rsync-ssl, and while ncat works on linux, i hit a similar issue when using rsync-ssl on macos. that on also getting fixed with "--blocking-io". i'm curious if we should see "--blocking-io"? as a solution to this problem , or if there better should be put work into ssl transport programs , so they be able to switch to unbuffered output, when binary data being sent to stdout. regards Roland gnutls issue: https://gitlab.com/gnutls/gnutls/-/work_items/1037 openssl issue: https://github.com/RsyncProject/rsync/issues/869 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20260426/c4f43425/attachment.htm>