Or you fly into Oakland and drive in because the flight from PDX-Oakland + Hertz costs less than the flight from PDX-SFO alone. SJC is ok except it's only open between 3 and 4pm on alternating Thursdays in May. I'll fly to SJC if I can get on the corporate jet, but not otherwise.
$5000 might be reasonable for a bit of work copying some data to some disks, but it is not nearly enough to cover being known as an evil traitor everyone in the world. His reputation is now destroyed and is essentially unemployable in any company or organization that cares about its own image.
Indeed. Properly salted, the brute force cost would be O(2^80). With rainbow tables, assuming your target is in your table dictionary, the cost is much much less.
Both in combination for the crypto - running crypto in JS under the control of a remote entity with no logical trust boundary or means for secure key establishment.
The crypto on it's own - Because nobody every gets it right. Storage security is not a trivial problem. Thinking AES is the solution to your problem is evidence that you don't understand the problem.
I'm an immigrant and I'm techy. It says so in my handle.
I get along fine with English. I do find most Americans have an accent of one sort or another so I suppose you mean we should stick to native English speakers like myself who are British.
The UK tech companies found it hard to export to the US
Why?
IBM
Selling to mainland Europe required translations
Is that a big deal? Especially if you went for a few major languages, like German, first. I would think that European manufacturers would have been more used to the need for translations than American companies.
P.S. Wish I had mod points to bump up your post.
It isn't a big deal. The dissolution of proprietary architectures is a natural process. It even occured back then.
A billion years ago, when I was studying for my Computer Science degree at Manchester University, the design of the Mark 1 and its test machine was certainly on the curriculum. I remember an exam where I had to describe the evolution of ALUs from Mark I to Cray I. Kids these days just get a bunch of Java and Hadoop.
I don't where 'Baby' came from, I never heard it referred to as that by the staff who worked on it. I graduated in 1990. I don't think I heard it referred to as 'Baby' until I was living in the 'States post 2000.
Adding a large amount of binary content to a source control system is all sorts of stupid. Get out of the dark ages and use a Maven repository like Nexus to store that crap, then integrate those artifacts into your build process via Ivy/Maven/Gradle/etc.
What makes you think all versionable content is source code?
The 802.11 phy rates were always specified at a range of speeds to accommodate the varying wireless environment and varying capabilities of the AP and STA.
It is the amateur attempts to describes the 'speed' of the device in terms of the absolute maximum without explaining how the specification actually specifies things that is wrong and misleading.
>I think he means that you don't have to share the available bandwidth with your neighbours.
But you do. Your neighbors might not get to use your AP and internet connection, but they certainly occupy bandwidth on the wireless channel when they run their own equipment on the same channel.
Right but it was the first and only transistor at the time, so it was competitive.
However a 100Kbit, quite fast memory that is expensive because it's made on a low volume manufacturing line, without the benefit of the billions of dollars spent developing silicon based manufacturing equipment is hardly going to be competitive in the market and won't be able to generate the cash necessary to build up a manufacturing infrastructure that can compete with cheaper, higher volume memories that are a 1000 times more dense.
There is a constant stream of 'flash killing' non volatile memories that never made it in the market. This will be one of them.
Some companies have called me to ask if they can use the crypto code on my website. I said yes because it's just a bit of code. People make too big a deal about bits of code. Working systems are hard. Bits of code are trivial.
You will find that the datasheets I posted elsewhere in this thread show flash at a semiconductor technology level to be 2-10 times slower than modern DRAM. That is not 'orders of magnitude'.
Slashdot Mirror
Or you fly into Oakland and drive in because the flight from PDX-Oakland + Hertz costs less than the flight from PDX-SFO alone. SJC is ok except it's only open between 3 and 4pm on alternating Thursdays in May. I'll fly to SJC if I can get on the corporate jet, but not otherwise.
>And introverts don't necessarily love the bustle of the city.
Have you been to silicon valley? There's plenty of bustle, just with worse traffic and no good restaurants.
$5000 might be reasonable for a bit of work copying some data to some disks, but it is not nearly enough to cover being known as an evil traitor everyone in the world. His reputation is now destroyed and is essentially unemployable in any company or organization that cares about its own image.
Indeed. Properly salted, the brute force cost would be O(2^80). With rainbow tables, assuming your target is in your table dictionary, the cost is much much less.
>SecurityWeek has confirmed that it is relatively trivial to brute-force the hash to obtain the seven-character password.
HP is on a low sodium diet, they didn't add salt.
Both in combination for the crypto - running crypto in JS under the control of a remote entity with no logical trust boundary or means for secure key establishment.
The crypto on it's own - Because nobody every gets it right. Storage security is not a trivial problem. Thinking AES is the solution to your problem is evidence that you don't understand the problem.
I could go on but I won't.
Bannana cream? How the hell do you get milk fat out of a bannana? Bannanas don't have nipples!
>We use HTML5/JS in conjunction with Apache Cordova ...
>But everything we put into localstorage is encrypted using an AES library.
Oh FFS! This is wrong on so many levels. I don't know where to start.
Way aye man, 'taint true innnit?
I'm an immigrant and I'm techy. It says so in my handle.
I get along fine with English. I do find most Americans have an accent of one sort or another so I suppose you mean we should stick to native English speakers like myself who are British.
The UK tech companies found it hard to export to the US
Why?
IBM
Selling to mainland Europe required translations
Is that a big deal? Especially if you went for a few major languages, like German, first. I would think that European manufacturers would have been more used to the need for translations than American companies.
P.S. Wish I had mod points to bump up your post.
It isn't a big deal. The dissolution of proprietary architectures is a natural process. It even occured back then.
A billion years ago, when I was studying for my Computer Science degree at Manchester University, the design of the Mark 1 and its test machine was certainly on the curriculum. I remember an exam where I had to describe the evolution of ALUs from Mark I to Cray I. Kids these days just get a bunch of Java and Hadoop.
I don't where 'Baby' came from, I never heard it referred to as that by the staff who worked on it. I graduated in 1990. I don't think I heard it referred to as 'Baby' until I was living in the 'States post 2000.
>That's just working around the limitations of your tool.
It's also working around the limitation of my brain.
Adding a large amount of binary content to a source control system is all sorts of stupid. Get out of the dark ages and use a Maven repository like Nexus to store that crap, then integrate those artifacts into your build process via Ivy/Maven/Gradle/etc.
What makes you think all versionable content is source code?
I choose not to dig up the memories of using Clearcase. It was the most unreliable, crashy, godawful VCS I've ever used.
The solution is not to have a complex tree. Then fixing tree conflicts is easy.
The 802.11 phy rates were always specified at a range of speeds to accommodate the varying wireless environment and varying capabilities of the AP and STA.
It is the amateur attempts to describes the 'speed' of the device in terms of the absolute maximum without explaining how the specification actually specifies things that is wrong and misleading.
Actually I've strung an Ethernet cable to the neighbor's house to help them out when their internet was borked.
Ok.. for the wires, no. Not with switched ethernet.
>I think he means that you don't have to share the available bandwidth with your neighbours.
But you do. Your neighbors might not get to use your AP and internet connection, but they certainly occupy bandwidth on the wireless channel when they run their own equipment on the same channel.
>Use ethernet. Cables don't have these kinds of problems.
Yes they do. 802.3 has packet and medium access overhead. Just not as much as 802.11
The school curriculum should be amended so that every school child graduates school knowing that physcial layer rate > MAC layer throughput.
Right but it was the first and only transistor at the time, so it was competitive.
However a 100Kbit, quite fast memory that is expensive because it's made on a low volume manufacturing line, without the benefit of the billions of dollars spent developing silicon based manufacturing equipment is hardly going to be competitive in the market and won't be able to generate the cash necessary to build up a manufacturing infrastructure that can compete with cheaper, higher volume memories that are a 1000 times more dense.
There is a constant stream of 'flash killing' non volatile memories that never made it in the market. This will be one of them.
Some companies have called me to ask if they can use the crypto code on my website. I said yes because it's just a bit of code.
People make too big a deal about bits of code. Working systems are hard. Bits of code are trivial.
> Flash is orders of magnitude slower than DRAM
You will find that the datasheets I posted elsewhere in this thread show flash at a semiconductor technology level to be 2-10 times slower than modern DRAM. That is not 'orders of magnitude'.