Of course, it used to be expertsexchange.com, which always got a giggle from me when I saw it in a URL.
It's worth pointing out that you can't know that this isn't a "disgruntled employee scenario" unless you have learned to read minds. They wouldn't be leaving if they were 100% happy.
Be careful what you ask for.
"So, the next time you complain about your phone service, why don't you try using two Dixie cups with a string? We don't care. We don't have to. We're the Phone Company."
Or by having someone else take the interview for you. Most profs in big courses don't know all their students.
The issue that Silent Circle points out is that SMTP is inherently unable to provide security against traffic analysis. Even if the body of the email is encrypted, the headers cannot be.
So yes, you can run your own email server, and require that only gpg traffic pass through it. But that won't keep you secure against traffic analysis (aka "metadata collection") with collection performed at your ISP.
You can't re-use nodes, but you _can_ put in crossing lines, which makes the grease smears less useful.
We have to protect our phoney baloney jobs here, gentlemen! We must do something about this immediately! Immediately! Immediately! Harrumph! Harrumph! Harrumph!
Most software (games being the obvious exception) has the possibility of creating harm to humans. Payroll, accounting, project management, word processing, etc. all have that potential.
Also *raises hand*.
On one system we stored programs by wiring them into a ROM. By hand. One wire per word, wrapped around the center pole of the E-cores clockwise for a 1, or counterclockwise for a 0. Then solder one end of the wire to the correct X address, and the other end to the correct Y address. Total, 256 16-bit words per board (Z was decoded to board-select).
Yes, I am old.
Once it hits the fan, the only rational choice is to sweep it up, package it, and sell it as fertilizer.