HackerTube.dev

Source: FBI looking at wife's phone call

CNN · 76.7K views · 2013-05-02 · 1:24

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

A short CNN news segment reporting that the FBI is looking at a phone call between Tamerlan Tsarnaev's widow and her husband after his photos were released. It is brief 2013 coverage of the Boston bombing investigation.

On Hacker News

HN commenters cite it as an example of claims that government can access digital communications and that none is secure.

Discussed on HN; no positive recommendation is recorded in this export · HN mentions 2013–2013

Topics

Search by tags

What people said

espeed · 2013-08 · Reference

Reposting this from a previous thread ( [LINK] )... I remember during the Boston bombing investigation, Tim Clemente, a former FBI counter-terrorism agent, told Erin Burnett on CNN that they could go back and get access to the content of the calls between the deceased bomber and his wife, Katherine Russell. After some Googling, I found a partial transcript of the CNN interview... "Almost immediately Erin Burnett, the host of CNN's Outfront, wanted to know how the government knew. Aren't phone calls supposed to be private? She interviewed Tim Clemente, a former FBI counter-terrorism agent on May 1, asking:" Is there any way … they [the federal investigators] can try to get the phone companies to give that up … It’s not a voice mail. It's just a conversation. There’s no way they can actually find out what [was said on the call], right, unless she tells them? Clemente: There is a way. We certainly have ways in national security investigations to find out exactly what was said in that conversation. It's not necessarily something that the FBI is going to want to present in court, but it may help lead the investigation … we certainly can find that out. Burnett: So they can actually get that? … that is incredible. Clemente: Welcome to America. All of that stuff is being captured as we speak, whether we know it or like it, or not. Source: [LINK] CNN Interview Clip ( [LINK] ) CNN Follow-Up Interview ( [VIDEO] ) When I initially saw this on CNN, my first thought was, do they also have

Read the original HN comment ↗
fossuser · 2013-07 · Reference

I agree with your first two points and if the complexity of using pgp were reduced to that of simply using email then I think it'd become more widely used. I didn't mean to imply that cryptocat itself is a reasonable compromise (I don't know enough), but that a centralized system that implements encryption for its users might be which leads into your fourth point. Yes javascript client-side encryption is fundamentally flawed in its current form from targeted attacks, but I'm thinking of untargeted and immediate wide spread adoption. If you're collecting everything from everyone in perpetuity the risk for abuse I see is when someone becomes interesting to the government they can query their data set and use it against them. I'd think there would be a way to use client side encryption by these companies to protect a user's data until they become 'interesting' at which point they'd have to use more fundamentally secure methods (which is how it currently is anyway). Seems like the easiest way to get the most people generally protected from abuse. Is using https enough? If that's the case then it seems like most communication would be protected anyway. I got the impression that this wasn't true - not because I don't trust google, but because of something else (it seemed google genuinely didn't give access to everything yet people made comments about no digital communication being secure: [VIDEO] ).

Read the original HN comment ↗
lurchpop · 2013-06 · Reference

There's also this: FBI agent for the second time says all communications are recorded. "No digital communication is secure" [VIDEO]

Read the original HN comment ↗

Sources

Video by CNN, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources