Computer-to-computer transfer

How it works

Locally it may be a share or a cable. Remotely it is SFTP, a link, or a tunnel. The interesting part is who is logged in and whether the destination path is the machine you think.

An editor sends 12 GB from a workstation to a remote suite over SFTP. Both ends are computers. A cloud bucket in the middle would still be computer-to-server-to-computer. They wanted the suite disk. The job writes there.

How it differs

This is not phone-to-computer. Mobile background rules do not apply.

A mapped drive that is actually a laptop asleep fails in a way a server will not.

Prefer a host that stays up.

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 computer to computer 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 computer to computer 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.