Flutterby™! : Layered Security

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Layered Security

2015-12-22 17:40:49.404673+00 by Dan Lyke 2 comments

RT André Koot RCX ‏@meneer:

Why we need layered security

And, seriously, if you haven't been keeping up with the revelations from the Juniper backdoors story, in this entry, and you're technically minded, take a look at A Few Thoughts on Cryptographic Engineering: On the Juniper backdoor.

To sum up, some hacker or group of hackers attacker noticed an existing backdoor in the Juniper software, which may have been intentional or unintentional -- you be the judge! They then piggybacked on top of it to build a backdoor of their own, something they were able to do because all of the hard work had already been done for them. The end result was a period in which someone -- maybe a foreign government -- was able to decrypt Juniper traffic in the U.S. and around the world.

Note that side-effect from prng_reseed().

[ related topics: Interactive Drama Photography Weblogs Software Engineering moron Law Work, productivity and environment Archival ]

comments in ascending chronological order (reverse):

#Comment Re: Layered Security made: 2015-12-25 10:50:26.032798+00 by: meuon

Dear CEO, CTO, CIO. If you don't implement our requested secret backdoor, we will confiscate everything here for long term deep forensic analysis to determine what un- (insert country name here)-an activities you are hiding. Sincerely, your government of the people.

#Comment Re: Layered Security made: 2015-12-29 17:16:10.432305+00 by: Dan Lyke

In the end, it comes down to needing to build encryption into the applications themselves. And being damned careful about how much those applications trust the next layer up.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.