Ex-CIA software engineer who leaked to WikiLeaks sentenced to 40 years
2 Feb 2024
Joshua Schulte had been found guilty of handing over classified materials in so-called Vault 7 leak.
 |
|---|
| The so-called Vault 7 leak was a major embarrassment for the CIA [File: Larry Downing/Reuters] |
A former CIA software engineer has been sentenced to 40 years in prison for leaking classified information and possessing child sexual abuse material.
Joshua Schulte, 35, was found guilty in 2022 of four counts each of espionage and computer hacking and one count of lying to FBI agents after handing over classified materials to whistleblowing organisation WikiLeaks.
Schulte was also convicted of contempt of court and making false statements in 2020, and possession of child abuse material last year.
The bulk of the sentence announced on Thursday was imposed over the so-called Vault 7 leak, which revealed embarrassing details of the CIA’s spying overseas.
The leak, which the CIA called a “digital Pearl Harbor”, showed how US spies hacked Apple and Android smartphones and sought to turn internet-connected televisions into listening devices.
The security breach prompted US officials to plan for an “all-out war” against Wikileaks, including discussing the possible kidnapping or assassination of its founder Julian Assange, Yahoo News reported, citing anonymous officials.
Assange was indicted on espionage charges in 2019 – a move that prompted condemnation by press freedom organisations – and is currently in Britain fighting extradition to the US.
Judge Jesse M Furman said the full extent of the damage caused by Schulte would likely never be known “but I have no doubt it was massive”.
Furman said Schulte had also continued to commit crimes while in jail by trying to leak more classified materials and by creating a hidden file on his computer that contained child sexual abuse images.
US Attorney Damian Williams said in a statement that Schulte had committed some of the “most brazen, heinous crimes of espionage in American history”.
“He caused untold damage to our national security in his quest for revenge against the CIA for its response to Schulte’s security breaches while employed there,” Williams said.
Addressing the court ahead of his sentencing, Schulte complained about harsh conditions he had endured in detention, including being denied hot water and being subjected to constant noise and artificial light.
Schulte also said it was unfair for prosecutors to seek a life sentence as they had previously offered a plea deal that would have seen him sentenced to 10 years in prison.
“This is not justice the government seeks, but vengeance,” he said.
It was a very good post, actually, and I didn’t relish deleting them. You’re welcome to resubmit it, in fact. But lemmy.ml users don’t like having their “Local” page filled up with several copies of the same post, which almost surely is why they were downvoted. That web UI feature is popular and works as intended; it’s not supposed to dedupe. Our users often flag posts as spam when this happens, which we admins then have to deal with.
So, as I’m reading this threat to learn some etiquette myself, I infer the ‘user’s not wanting their “local” page to include duplicates’ to mean that when posting to multiple communities, it would be a best practice to only pick one relevant community per server instance?
Like in this case, it was crossed to both: ‘worldnews@lemmy.world’ and ‘world@lemmy.world’
In order to avoid duplicates, only one of those should have been included?
Like community1@server1 community2@server2, etc? If there’s two relevant communities, just pick the best one?
It’s your job to recognize that it was a flag error.
Did you see the one user that said I had double posted. And when I pointed out that I had only posted once to each relevant comm, they apologized and said they wanted to undo their flagging it as spam?
This is a UI bug for the New sort filter. Its your job to weigh the flags and understand when users flag something by accident
Yes, I saw what the one kbin user said. And thank you for telling me what my job is.
Honestly I’m impressed that you’re still mansplaining a lemmy.ml admin—the archetypal Lemmy instance—on Lemmy etiquette, Lemmy UI flaws, how he’s a a fuck-up & an asshole, and how to do his job. You really know how to win hearts & minds.
You’re welcome to make the case for UI changes on GitHub through issue tickets and/or pull requests.
If you both want to debate moderation decisions on lemmy.ml, can you do that on lemmy.ml?
Its important to hold people in power accountable for their mistakes
The bugs I referenced are already open
@davel
I get both stand of points and it sounds like a dilemma. As a user I want relevant posts with info but I want a deduped Time line.
@clever_banana