this post was submitted on 04 Feb 2026
511 points (99.4% liked)

Technology

80478 readers
3456 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
511
FBI Couldn’t Get into WaPo Reporter’s iPhone Because It Had Lockdown Mode Enabled (www.404media.co)
submitted 16 hours ago by tonytins@pawb.social to c/technology@lemmy.world
97 comments fedilink hide all child comments
 

The FBI has been unable to access a Washington Post reporter’s seized iPhone because it was in Lockdown Mode, a sometimes overlooked feature that makes iPhones broadly more secure, according to recently filed court records.

The court record shows what devices and data the FBI was able to ultimately access, and which devices it could not, after raiding the home of the reporter, Hannah Natanson, in January as part of an investigation into leaks of classified information. It also provides rare insight into the apparent effectiveness of Lockdown Mode, or at least how effective it might be before the FBI may try other techniques to access the device.

“Because the iPhone was in Lockdown mode, CART could not extract that device,” the court record reads, referring to the FBI’s Computer Analysis Response Team, a unit focused on performing forensic analyses of seized devices. The document is written by the government, and is opposing the return of Natanson’s devices.

Archive: http://archive.today/gfTg9

you are viewing a single comment's thread
view the rest of the comments
[–] 20dogs@feddit.uk 16 points 15 hours ago (1 children)

What distro are you using? This seems bizarre and the sort of thing you see on a less stable rolling release.

[–] MyNameIsAtticus@lemmy.world 0 points 5 hours ago (1 children)

I've hopped around. The 3 main ones I've touched though are:

  • Ubuntu (which had the Storage Bug. Especially weird considering the only thing that thing had going on was Firefox for Streaming at the time)
  • Bazzite (which ultimately i switched away from because Halo just wouldn't launch one morning)
  • CachyOS (specifically KDE), which has the issues with WiFi and Bluetooth. From what i understand The Wi-Fi and Bluetooth issues are mostly because Linux doesn't have great Realtek drivers.

All of which are the Stable Versions. I believe Bazzite and CachyOS are both Rolling Releases which would explain the issues. I don't think Ubuntu is as far as i know which makes it's storage issue especially interesting.

I also have an issue with Debian on my media server where despite telling it everywhere possible not to go to sleep, it decides it wants to go to sleep anyways. But i don't really consider that under these same issues because that's a media server and i expect it to be a little more "Tinkery" than my Main use PCs.

[–] 20dogs@feddit.uk 1 points 5 hours ago (1 children)

That's weird. Ubuntu has two tracks, the standard that gets updated every six months and the LTS track that updates every two years. I think the developers recommend the LTS versions, and it's the version I see that tends to get better corporate support. But even on LTS you can find some oddities sometimes I suppose.

[–] MyNameIsAtticus@lemmy.world 1 points 5 hours ago (1 children)

I have a hypothesis that it was some niche hardware compatibility issue, because streaming was that machines bare minimum. It had a 32 bit dual core CPU, an iGPU, 4 GB of DDR3 RAM, and a 500 GB HDD. All this was in the year 2020 and this PC was made in 2008, so suffice to say it wasn't winning any awards.

Like i said though, this is a hypothesis, so it's entirely possible it was just Ubuntu deciding it wanted to freak out on me.

[–] KryptonNerd@slrpnk.net 1 points 3 hours ago

It could've also been a snap issue (we've seen an issue recently with the VSCode Snap eating up storage) and IIRC Firefox on Ubuntu is a Snap (by default, obviously you can install it any other way as well but you shouldn't be expected to).

I've been on Fedora for 3 or so years and it has pretty much worked flawlessly (the only exception to that is it used to sometimes have issues with automatically sleeping correctly when I closed the laptop lid, but that hasn't been an issue for about a year)