Linux file transfer

How it works

Case-sensitive paths and no drive letters surprise people arriving from Windows. Permissions and owners matter. Binary mode matters if an old FTP door is still in the path. The tools are native.

A Windows script sends Cut.mov and cut.mov to a Linux drop. Both land. A later Windows download of the folder keeps one. They rename to unique names before the next send.

How it differs

Linux file transfer is not a different protocol. It is the same protocols with POSIX path rules.

A umask that strips group read makes a file land that the partner group cannot fetch.

Set the mode in the job.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For linux file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive linux file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.