Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by Fnord666 on Tuesday December 12 2017, @07:34AM   Printer-friendly
from the tilting-at-windmills dept.

The new FBI Director Christopher Wray has been repeating the broken rhetoric of the Crypto Wars:

In recent testimony before Congress, the director of the FBI has again highlighted what the government sees as the problem of easy-to-use, on-by-default, strong encryption.

In prepared remarks from last Thursday, FBI Director Christopher Wray said that encryption presents a "significant challenge to conducting lawful court-ordered access," he said, again using the longstanding government moniker "Going Dark."

The statement was just one portion of his testimony about the agency's priorities for the coming year.

The FBI and its parent agency, the Department of Justice, have recently stepped up public rhetoric about the so-called dangers of "Going Dark." In recent months, both Wray and Deputy Attorney General Rod Rosenstein have given numerous public statements about this issue.

Remember to use encryption irresponsibly, and stay salty, my FBI friends.

Previously: FBI Chief Calls for National Talk Over Encryption vs. Safety
Federal Court Rules That the FBI Does Not Have to Disclose Name of iPhone Hacking Vendor
PureVPN Logs Helped FBI Net Alleged Cyberstalker
FBI Failed to Access 7,000 Encrypted Mobile Devices
Great, Now There's "Responsible Encryption"
FBI Bemoans Phone Encryption After Texas Shooting, but Refuses Apple's Help
DOJ: Strong Encryption That We Don't Have Access to is "Unreasonable"


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Interesting) by Anonymous Coward on Tuesday December 12 2017, @08:47AM

    by Anonymous Coward on Tuesday December 12 2017, @08:47AM (#608678)

    Although it might not be enabled.

    The ARM TrustZone stuff dates back to at least the A20 era hardware and I believe earlier.

    The real solution at this point is coming up with VHDL/Verilog/etc chip designs, then process specific designs, then a set of unit tests against each with integrated support for fuzzing the inputs.

    If the chip can successfully pass a few months of fuzzing without unintended operations it should be considerable as a success and so long as each new manufacturer or mask revision gets similiar scrutiny shoudl ensure that no chips end up backdoored in an easy to exploit manner.

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1