FYI... Sean "xobs" Cross and Andrew "bunnie" Huang disclosed low-level vulnerabilities in SD cards (as far as I can tell: on par with- and related to- the more recent BadUSB-type hacks) at a 30C3, back in December 2013.
For further details, see:-
Unemployment is a benefit of a technologically advanced society (paraphrasing Robert Anton Wilson, I believe) -- the sooner we all get our heads around that, the better.
Humans have always made tools to make tasks easier (or automate them entirely).
...after recent comments from Valve re. developing on Linux (easy to port to, better performance than DirectX, ability to work with / feedback commits to driver devs, etc) — plus Gabe Newell recently calling Windows 8 a catastrophe — I would not be at all surprised if we saw a Valve-branded Linux-based games console in the near future.
But maybe that's just wishful thinking on my part?
What I mean is: unless app development is low investment, low risk and quick turnaround -- with the business intelligence to back that up (daily- or at least weekly- sales stats), coupled with prompt payments -- it's just a no-go for small/indy developers and/or small projects/apps. Word about the state of Microsoft re. third-party app developers is already getting around, so my guess is they'll just have to take it on the chin, as Metro/Win7phone apps will be slow coming because of this.
But hey, what's new?
It's all well and good Microsoft copying Apple's business model here, but until they copy Apple with regards to paying their third-party devs, iOS developers will always be happier than Windows7/mobile/WindowsStore devs.
- Here's how it works with Apple: you get to view daily stats for your sales, and you get paid for that month's sales at the end of the month. Boom!
- Here's how it works currently with Microsoft: you have no idea about sales until months and months have elapsed, and then they tell you you'll get paid some months even later than that.
...so tell me Microsoft, is this enough incentive to retain any of the 'developers developers developers' that you may attract, so that they will go on to develop more than a single product?
Microsoft are at an all time low at the moment. They're a lumbering hippo in the IT world, surviving solely through their clout and might. Lots of other companies 'get it' and are far more agile. It'll be Zunes all the way down if they're not careful.
I like C, and have used it a lot on and off over the years (and probably will still have to again, at some point) - but recently I've been totally loving programming in Google's Go language: it's just fricking awesome, for so many reasons!
I think Go is destined for Good-Things(tm) in the future
why is this story categorised as 'idle'?? it's a perfectly valid news story about artificial-intelligence/machine-learning & big-data, the kind of story that is becoming more and more common as time progresses -- this is the future!
i've added the tag 'bigdata' to the story more than once, but it keeps getting removed -- why are people so clueless?
i even logged for the first time in years, just so i could set the correct tags. meh.
I'm certainly no expert, but Sumerian is generally accepted as being the first written language.
I'd like to know how on this grand scheme languages such as Basque are reconciled? - along with a couple of other languages, the Basque language is classified as a language isolate. Although most of these have become isolates in fairly recent history (and therefore shouldn't be too hard to link to a language 'tree') Basque is a tricky one because it's been an isolate for as long as it has been recorded, and does not share its roots with other Indo-European languages.
I read the article (for once) but it didn't go anywhere near those kinds of details - which I find kinda odd: I would've thought when it comes to grand unifying theories of language that linguists would've been all over the issue of isolate languages like a rash.
The chart/diagram in the Economist article did have Basque on it - 'near' Greek and Russian.
Sure it's a damned interesting idea to be able to link all languages to a common source -- but the article makes it seem as though this one all boils down to plotting languages according to similarities, and then best-fitting a line across the chart. I hope there's a lot more to it than that -- otherwise it's not really a discovery, but merely an interesting hypothesis in my book.
(for those interested Wikipedia on Basque language history)
Ok - yeah, my point was valid, but the problem space is indeed not very large for 6-character alpha-numeric passwords.
But I stand corrected, because as the AC points out with the posted link: using a slower algorithm will indeed throw a spanner in the works for any cracker.
In the past we've implemented password hashing using Blowfish, and we set a minimum password length of 8 - which is an improvement I guess.
Why isn't Bcrypt benchmarked on the page linked to (http://www.cryptopp.com/benchmarks-amd64.html) from the how-to-safely-store-a-password page? It makes it difficult to make a true comparison.
I don't get it - surely it shouldn't matter if someone gains access to the password verification routine, the salt and the encrypted passwords... unless the password hashing/encryption is easily reversible?
They've still got to try and brute force match the encrypted data with a dictionary attack - sure, having the salt makes it easier - but if you've got the salt and the encrypted passwords it doesn't matter what encryption algorithm is used, you've still got to use a brute force dictionary attack. Most encryption algorithms aren't easily reversible - and that's the whole point.