The typical business traveler doesn't need gigabytes and gigabytes of documents. If you are traveling and need sensitive documents, buy a new laptop at your des

The typical business traveler doesn't need gigabytes and gigabytes of documents. If you are traveling and need sensitive documents, buy a new laptop at your destination and load the data you need on it. When leaving, wipe it and leave it in a place where you or another employee can pick it up next time they are in that country. It's unfortunate that business people (as opposed to programmers) typically don't have something as compact and transferrable as dotfiles for getting up and running on a branch new machine. The question is how to travel with a new set of private keys securely so you don't give them up on exit. Coming back isn't a problem because you can just revoke access for that temporary public-private key pair before you log off during your last ssh session before returning to the country. I don't think this is practical now. But it is a known problem and solutions for quickly getting a machine up and running are getting better and better. I imagine that a chef or puppet script could be used on the new machine to get everything up and running. You just need to ssh in once to fetch the script that would set up the machine at your destination.