Local file transfer

How it works

Throughput can be high. Identity and encryption are often weaker because people trust the building. Guest Wi-Fi isolation breaks peer copies. A local copy is not a backup.

Two suites copy 80 GB across the LAN in under an hour. The same package for a remote client is a separate Internet transfer. A guest VLAN that cannot see the NAS fails the local copy and the Internet path still works.

How it differs

Local is a path claim, not a protocol. SMB, HTTPS, and USB can all be local.

An open share on the LAN is still a disclosure if contractors are on that LAN.

Use accounts.

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