>>Yupp, seems not far from my current take. They also mention dedicated SFTP server:
>>IMO having dedicated (at least logical, hardened VM) can be the key benefit.
>>You keep things there you have to expose for work, but keep internal to your company.
>>
>>Different from the way I view WebDAV: mapping Collaboration documents,
>>sky won't fall if the few currently being worked on are exposed before they are done.

>If you like overkill: Setup a gilab server, have clone of the repo on both sites and us git's mechanism to transport the data. The pro is, you do not need binary moduls, just git installed, the rest is a bunch of calls to CMD or the like. :)

For the Crown Jewel case KISS benefit of SFTP server and protocol still stand from my POV.

Gitlab/versioning as replacement for WebDAV is a thought I somtimes mull,
coupled with switching from Word plus PDF to MarkDown to view changes in pure text.

So I let fingers dance: first relevant link seems not problematic:
https://stackoverflow.com/questions/35337414/are-git-push-and-pulls-encrypted
esp if you scroll down to very bottom.

https://stackoverflow.com/questions/3777075/ssl-certificate-rejected-trying-to-access-github-over-https-behind-firewall
is not current, might be solved via updates as some passages hint, buuuuut reads worse.

https://ourtechroom.com/tech/https-vs-ssh-in-git/
reads workable, but after
https://github.com/BishopFox/sliver/wiki/Transport-Encryption
https://github.com/maxlandon/wiregost/wiki/Transport-Encryption
"overkill" does seem like a fitting description compared to Nextcloud WebDAV;-)

Nextcloud DOES include versioning, although less refined.
I might return to the topic AFTER manging the switch to MarkDown

regards
thomas