Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
FBI Director Urges New Encryption Legislation
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/21/2014 | 11:37:51 AM
Re: Tradeoff
Totally agree that law enforcement officials like FBI Director James Comey have a long way to go to reassure the public that they are not overreaching in the name of pubic security.  But getting out in front of public policy institutions like Brookings, is at least a small step in the right direction...
Robert McDougal
100%
0%
Robert McDougal,
User Rank: Ninja
10/17/2014 | 11:25:45 AM
Re: Tradeoff
"Law enforcement needs to be able to access communications in a lawful way in order to bring people to justice."

I'm very sorry but you (the government) didn't seem to be content with accessing communications in a 'lawful way' not too long ago, why would I trust you now?
RobertM866
100%
0%
RobertM866,
User Rank: Apprentice
10/17/2014 | 8:39:07 AM
Re: Tradeoff
Not when any such discussion will invariably lead to a lessening of protections against government spying and interference into the public's private affairs.  

The old saying was, the most frightening words one could here were "I'm from the government, and i'm here to help".  I would argue that more frightening is "in the name of public safety" or "national secuirty". 
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/17/2014 | 8:24:17 AM
Re: Tradeoff
"We are completely comfortable with court orders and lawful authority. "

Except when government agencies break the rules in the name of public safety. That said,  it's hard to argue against a full-throated debate about encryption and how to update existing laws. Is Congress up to the task? <sigh>
Joe Stanganelli
100%
0%
Joe Stanganelli,
User Rank: Ninja
10/17/2014 | 7:43:07 AM
Tradeoff
As Benjamin Franklin wrote: "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."

And besides, when people are like, "Thanks, government, but I'll take my chances with the murderers," you know that government has a huge credibility problem.


Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16632
PUBLISHED: 2021-05-15
A XSS Vulnerability in /uploads/dede/action_search.php in DedeCMS V5.7 SP2 allows an authenticated user to execute remote arbitrary code via the keyword parameter.
CVE-2021-32073
PUBLISHED: 2021-05-15
DedeCMS V5.7 SP2 contains a CSRF vulnerability that allows a remote attacker to send a malicious request to to the web manager allowing remote code execution.
CVE-2021-33033
PUBLISHED: 2021-05-14
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
CVE-2021-33034
PUBLISHED: 2021-05-14
In the Linux kernel before 5.12.4, net/bluetooth/hci_event.c has a use-after-free when destroying an hci_chan, aka CID-5c4c8c954409. This leads to writing an arbitrary value.
CVE-2019-25044
PUBLISHED: 2021-05-14
The block subsystem in the Linux kernel before 5.2 has a use-after-free that can lead to arbitrary code execution in the kernel context and privilege escalation, aka CID-c3e2219216c9. This is related to blk_mq_free_rqs and blk_cleanup_queue.