Most people do not have a problem with the jackboot of authority, so long as it is on their feet rather than their neck.

This is the worst crime of all.

Ah, yes, and "Preview"... Teach them to "Preview" posts too...

The right way is to talk to your kids about these things. Give examples of scams, tell them there is porn, there is violence, and always, always if they feel unsure about something they should talk to you (Mostly for scams, I'm pretty sure they'll handle porn. Hell, even weird porn isn't as bad as seeing ISIS chop someones head off). Software protection is just a crutch, the real protection is education and vigilance.The right way is to talk to your kids about these things. Give examples of scams, tell them there is porn, there is violence, and always, always if they feel unsure about something they should talk to you (Mostly for scams, I'm pretty sure they'll handle porn. Hell, even weird porn isn't as bad as seeing ISIS chop someones head off). Software protection is just a crutch, the real protection is education and vigilance.

ANYthing that reduces costs, enhances productivity, or makes life easier is a "fraud enabler."

Cell phone SIMs are the "Encryption Castle", really? From a practical perspective, they are essentially plaintext, since everything gets fully decrypted at each hop.

Maybe I will start calling my previous car a "Dining Palace" in honor of the epic glorious time that I once ate a chili dog while driving, shifting and making a left turn (alas, this was before I had a cell phone) without getting any chili on my shirt.

If a breach happens, just change your medical history.

Those Barbie thumb drives already have them. Not my fault you haven't discovered it yet.

Go work for a contractor. Get to know the feds. Then your resume magically moves to the top in usajobs.gov.

Rubber hoses are weak. You never get threatened with a rubber hose or a $5 wrench, without knowing it happened and your enemy revealing himself. It takes irrevocable commitment and admission of guilt on their part, and therefore risk of consequences, to take things to that level.

When they bring that stuff out, comply. Sing like a bird. They get the data they want, and then you call the media and your lawyer (or the cops, if your adversary with the hose/wrench doesn't happen to be the cops), and the TRUE bitchslapping (to whatever degree is possible, at least) may then commence.

Crypto is good. Sure, you can still find some bad things within that scenario: your privacy was still violated rather than protected. Maybe they're going to "disappear" you so that you never get to tell anyone about the threat or torture. Maybe they're going to torture you anyway after you give up your keys. But all those possibilities also exist in the plaintext scenario too! If they want to murder you, they'll do it. If they want to torture you, they'll do it. Psychopaths are going to do whatever they're going to to. But they slip up and get caught sometimes, and if you confront them with crypto, there's also the chance they'll do what many other criminals usually do: pick an easier target.

If you're talking about the Unix epoch, shouldn't it ve 1970? While I know the 0 of the Unix Epoch, I have no idea what weekday it was.

Thank you. I didn't have to think about this ever since college.

There are also a plethora of "technically correct" answers. You could say: "I scp the file to your server", where you presume the server is secure, and ssh is secure, so the documents confidentiality is guaranteed. (Upload the file using https works as an answer too). Hey, just connect to the companies VPN and copy the file to a Samba share. Valid too!
The question of what kind of file it was, isn't even that dumb. I'm not familiar with PDF, but I could -for example- imagine there is a standard for encryption within PDF. Someone from with a document management background would most likely think of such solutions.

It's a vast field, and expertise of people is usually just a subset. I'm not even sure what the answer you you expected was, but I'd say: I'd use your public key to encrypt the file to you and then send it to you. Personally, I wouldn't know which commands to invoke to do this, but I know that's the theory.

So, should any developer know this? That is debatable. I've had very competent developers who had next to no clue about how DNS works. They could do their job just fine with that. Me? Personally, I'm not up to snuff with the finer points of SQL queries and all the joins that exists and when it makes sense to create an index, etc. Could I find out? Most likely, but I haven't had the need to recently.

The problem is, that you are mapping your knowlegde to "what people must know". I used to do that too, and I probably still do often enough. The DNS example above didn't come from nowhere: I had the case, and I was really thinking "how could such a competent person not know this", but then this person could probably enlighten me about dozens of things I don't know well enough.

It all comes down to what you define as "general knowgledge" for a developer should be and that is highly subjective.

TL;DR Hiring people is hard. Especially, technical people.