In this sponsored Weekly Show, Jesse Rothstein, co-founder & CTO of ExtraHop joins the Packet Pushers to talk about how ExtraHop helps organizations tap the network for real-time visibility into all IT systems. The post Show 328: Wire Data Analysis With ExtraHop (Sponsored) appeared first on Packet Pushers.
How Does Internet Work - We know what is networking
Computer networks are probably the best example of graphs these days. I started therefore to consider graph database as an excellent tool for storing experimental results of my networking complexity analysis method. It’s a project that I’m doing (starting to do) in which I will try to create a better method of computer network complexity audit by combining few of already existing methods and by additionally enhancing some of their algorithms to get more precise results out of the whole thing. The idea is that most of network complexity measurement mechanism rely strongly on graph theory in which most metrics
Once robots can distinguish objects in 3D, maids may be the next workers to be automated.
Below is the Google Analytics page views for the articles between January 1st 2016 and January 1st 2017. I didn’t include Home page , CCDE Course and the CCDE E-book pages but just the technical articles. If you haven’t looked at some of those yet, I recommend definitely read them now. BGP Route Reflector […]
The post 10 Most Popular articles of 2016 on orhanergun.net and statistics appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
Moore’s Law has been the driving force behind computer evolution for more than five decades, fueling the relentless innovation that led to more transistors being added to increasingly smaller processors that rapidly increased the performance of computing while at the same time driving down the cost.
Fifty-plus years later, as the die continues to shrink, there are signs that Moore’s Law is getting more difficult to keep up with. For example, Intel – the keeper of the Moore’s Law flame – has pushed back the transition from 14-nanometers to 10nm by more than a year as it worked through issues …
A Glimmer of Light Against Dark Silicon was written by Jeffrey Burt at The Next Platform.
Lo is known for identifying promising markets and launching thriving startups.
This post addresses a (mostly) cosmetic issue with the current way that Arista distributes its Vagrant box for vEOS. I say “mostly cosmetic” because while the Vagrant box for vEOS is perfectly functional if you use it via Arista’s instructions, adding metadata as I explain here provides a small bit of additional flexibility should you need multiple versions of the vEOS box on your system.
If you follow Arista’s instructions, then you’ll end up with something like this when you run vagrant box list:
arista-veos-4.18.0 (virtualbox, 0)
bento/ubuntu-16.04 (virtualbox, 2.3.1)
centos/6 (virtualbox, 1611.01)
centos/7 (virtualbox, 1611.01)
centos/atomic-host (virtualbox, 7.20170131)
coreos-stable (virtualbox, 1235.9.0)
debian/jessie64 (virtualbox, 8.7.0)
Note that the version of the vEOS box is embedded in the name. Now, you could not put the version in the name, but because there’s no metadata—which is why it shows (virtualbox, 0) on that line—you wouldn’t have any way of knowing which version you had. Further, what happens when you want to have multiple versions of the vEOS box?
Fortunately, there’s an easy fix (inspired by the way CoreOS distributes their Vagrant box). Just create a file with the Continue reading
The public cloud is taking its toll.
Last Friday, Tavis Ormandy from Google’s Project Zero contacted Cloudflare to report a security problem with our edge servers. He was seeing corrupted web pages being returned by some HTTP requests run through Cloudflare.
It turned out that in some unusual circumstances, which I’ll detail below, our edge servers were running past the end of a buffer and returning memory that contained private information such as HTTP cookies, authentication tokens, HTTP POST bodies, and other sensitive data. And some of that data had been cached by search engines.
For the avoidance of doubt, Cloudflare customer SSL private keys were not leaked. Cloudflare has always terminated SSL connections through an isolated instance of NGINX that was not affected by this bug.
We quickly identified the problem and turned off three minor Cloudflare features (email obfuscation, Server-side Excludes and Automatic HTTPS Rewrites) that were all using the same HTML parser chain that was causing the leakage. At that point it was no longer possible for memory to be returned in an HTTP response.
Because of the seriousness of such a bug, a cross-functional team from software engineering, infosec and operations formed in San Francisco and London to fully understand Continue reading