USB transfer

How it works

Speed is high and the network is absent. Filesystems still disagree on names and forks. Eject before you pull the cable or the copy is partial. Hash if the files matter. There is no remote revoke.

A 30 GB card copies to a laptop over USB 3 in a few minutes. The operator pulls the cable at 90 percent. The folder exists and the last files are short. A later copy with a hash matches.

How it differs

USB transfer is not a NAS copy. No one else can fetch the result until a second transfer.

A drive formatted for one OS mounts read-only on another.

Agree the filesystem.

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 usb 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 usb 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.