Cybersecurity Expert Answers Hacking History Questions | Tech Support | WIRED

0:00 – 5:41

From playful hacks to the first real cyber intrusions

The video opens with Jeff Crume joking that he hopes they stay out of jail, which is a fitting way to begin a story about a word that did not start out criminal at all. Asked about the most influential hacker in history, he picks Kevin Mitnick as the best known early figure, not because Mitnick represented all hacking, but because he made one tactic famous: social engineering. Crume describes it in plain terms, conning people by leaning on their desire to trust. That detail matters because it sets up one of the video's recurring surprises: the weak point is often not the machine, but the human standing next to it. He then rewinds to where the word "hack" came from. At MIT in the 1960s, a Model Train Club used it for clever, unconventional use of technology. Only later, in the 1970s and 1980s, did the public start tying hacking to unauthorized access. Crume uses the familiar black hat, white hat, and gray hat framing, but his deeper point is that intent changes how we judge the same technical skill. The same curiosity that once made someone a creative tinkerer can, with different motives, make them a criminal. From there he maps hacking onto the shape of computing itself. In the 1960s, there was no internet, so attacks mostly required physical access to data centers guarded by what he calls "guards, guns and gates." Then came phone phreaking, remote manipulation of the phone network, and after that the modem era, where systems became reachable over public lines if you knew the password. Once the internet spread in the 1980s and 1990s, everything changed because, as he puts it, everyone suddenly had access to everyone everywhere. That same expansion created opportunity for both innovation and attack. The examples get more concrete quickly. Crume recalls the CIA website defacement that briefly changed the name to "Central Stupidity Agency," a case of electronic graffiti more than serious sabotage. He uses it to pivot into hardening basics: change default credentials, turn off unnecessary services, keep software up to date, and use multifactor authentication. Then he tackles a question about Signal being open-source and flips the intuition many people have. Open code is not a weakness if the cryptography is sound. Invoking Kerckhoffs' Principle, he explains that the algorithm can be public, the secret is the key. Good security, in other words, should survive scrutiny, not depend on magic obscurity.