There’s no file’s for TCP communication. However TCP itself is a reliable protocol, it already tries to prevent corruption for data transferred.

This is a layer above TCP, not TCP itself. This would be like ssl, so look at :gen_ssl, which it itself runs on top of :gen_tcp.

TCP does not know about files or encryption by itself, so you need to implement another transfer protocol on top that suites your needs.

TCP only saves you for packet loss as it will rerequest packages that are missing from a sequence. AFAIR also packages are checksummed but I’m not sure about that one…

Nevertheless, gen_tcp won’t give you magically more or better guarantees that TCP would give you.

Depends on what you are transferring to or from?

If it’s multiple local erlang nodes, could just use the standard distribution, if it’s remote erlang nodes then standard distribution over an SSH tunnel. Honestly I’d just use :ssh_sftp regardless of what it is, or a web server.

Use ssh module if you can and setup SSH server on the other end. In that way you will not need anything extra.

SSH works just fine for that, one connects to the other, they just host a little ssh thing and the other connects and transfers what it needs fully encrypted.