IETF Yokohama Days 4 & 5
Posted on Packet Pushers here. This is my last post in the series; next week, back to regular blogging.
The post IETF Yokohama Days 4 & 5 appeared first on 'net work.
Posted on Packet Pushers here. This is my last post in the series; next week, back to regular blogging.
The post IETF Yokohama Days 4 & 5 appeared first on 'net work.
Funny enough, much of the food you will find in Yokohama is Chinese, rather than Japanese — another odd fact you probably didn’t need to know. I’m going to cover day 4 and 5 here, as I’m leaving tomorrow morning to head back to the “real world.” Wednesday is a “slow day” in terms of […]
The post IETF Yokohama: Days 4 & 5 appeared first on Packet Pushers.
This week's feature interview is with Troy Hunt of HaveIBeenPwned.com. And he's noticing something pretty weird. It's common for people to deface websites for bragging rights, and yeah, it's not new that data dumps are the new bragging fodder. But it seems like these days attackers are seeing Troy's site as the definitive place to get cred. Now they'll steal a bunch of data and Troy is their first stop.
Life is strange on the internets. That's this week's feature interview.
Pradeep Sindhu sees networks reducing down to just routers and fiber.
A hot streak gets cut short by China, of all things.
SD-WAN has achieved liftoff, according to ONUG's polling.
Godwin's law and its corollaries would not apply to discussions covering known mainstays of Nazi Germany such as genocide, eugenics, or racial superiority, nor to a discussion of other totalitarian regimes or ideologies, if that was the explicit topic of conversation, because a Nazi comparison in those circumstances may be appropriate, in effect committing the fallacist's fallacy, or inferring that an argument containing a fallacy must necessarily come to incorrect conclusions.An example is a discussion whether waving the Confederate flags was "hate speech" or "fighting words", and hence undeserving of First Amendment protections.
Download your free copy of the Virtual Edge Report today!
The former Cisco CTO drops a few hints at the Intel Capital Global Summit.
I've been bitten by this one. It happens when you quite naturally use the file system as a quick and dirty database. A directory is a lot like a table and a file name looks a lot like a key. You can store many-to-one relationships via subdirectories. And the path to a file makes a handy quick lookup key.
The problem is a file system isn't a database. That realization doesn't hit until you reach a threshold where there are actually lots of files. Everything works perfectly until then.
When the threshold is hit iterating a directory becomes very slow because most file system directory data structures are not optimized for the lots of small files case. And even opening a file becomes slow.
According to Steve Gibson on Security Now (@16:10) LastPass ran into this problem. LastPass stored every item in their vault in an individual file. This allowed standard file syncing technology to be used to update only the changed files. Updating a password changes just one file so only that file is synced.
Steve thinks this is a design mistake, but this approach makes perfect sense. It's simple and robust, which is good design given, what I assume, Continue reading