Re: Mountain Climbing 101
"...obesity problem?"
Not me. Certainly a few pounds over 'ideal'; but miles from 'obese'. Cheers.
4286 publicly visible posts • joined 28 Jun 2013
"...Ben Nevis... ...4,411 feet..." Nearly die.
Hey. You're doing it wrong.
Pikes Peak, CO, USA, 14,110 feet (!). Drive up. Park. Buy some doughnuts. Browse around. Drive back down. Turn around, before the exiting the toll booth. Drive back up, because it's fun. Etc.
Mount Washington, NH, USA, 6,288 feet. Drive up. Park. Have some snacks. Browse around. Drive back down to the smell of burning brakes (steep!).
Whiteface Mountain, NY. USA, 4,865 feet. Drive up. Park. Take the ELEVATOR (!) to the summit. Browse around, buy some gifts at the gift shop. Have lunch.
"A plane might be a better option..."
The crossover point, considering door-to-door, is actually about a 6-hour drive.
There have been quite a few tests, demonstrations, races, etc. to document this finding.
YMMV, and there's a distribution of variation on this rough figure. Smaller airports at each end might be faster than huge huge airports. Taxi cab saves time compared to rental. Many variables.
And of course, if you're using an electric car, forget it. Unless there are optimally-located fast chargers along the route. Charging time makes six into five.
There was a news item a year or two ago about some bloke that ruined his Model S battery pack. Something about racing to catch a flight, and leaving it parked for weeks with the battery state too low. Those details don't matter.The interesting tidbit was that the price of replacing the battery pack was US$46,000.
Considering that the battery pack is going to go bad at some point (a certainty, not just a risk); this seems to be a huge counterbalancing factor to the advantages. Even if the price of the pack drops, it's still going to be 'The Most Expensive Car Maintenance Line Item' in history.
Will there be a huge fleet of perfectly good used 9 year old Teslas, with failed batteries, worth, when fixed, slightly less than the cost of repair? All other used parts will available cheap.
Will this limited lifespan, terminated early by the cost of the battery, result in the final analysis revealing that the total lifecycle footprint per km being higher than expected?
At this point, some will jump in to point out that the battery pack is going to last far longer than a decade. Really? Perhaps Tesla should market this technology, because I've never seen a Li-ion cell that was much good after eight or nine years, tops. And I'm not leaving my laptops outside in the extreme climate.
Unless Musk figures out how to get the cost of replacing a 'lifed' item way down into the 4-figures range ($46k -> $9k), then this is all going to blow up in about a decade.
Maybe he's planning to go to Mars before then, because there's going to be a price on his head back here on Earth...
If you watch Jay Leno's Garage ('net) you'll see him taking out his 100 year old electric car for a spin. He tells about how electric and steam cars lost market share because gasoline was just better.
It's all down to batteries. They're getting closer, but need another couple generations of improvements. Double the overall performance of batteries, and it'll be over. Once e-cars are actually better, then everybody will choose them. No need for the 'religious' nonsense.
Don't ignore the total cost of ownership of the battery pack. When it's worn out, the huge bill to replace it will make 8 years of petrol/gasoline look cheap. Over US$40k for the Model S according to the news item of the poor slob that ruined one.
cornz1 has a point.
If you live in a highly-polluted city, then don't blame the modern petrol/gasoline burning cars. Their exhaust can easily be cleaner than ambient. Which kinda proves they're not to blame; they're helping, leave 'em running overnight.
Hardly anyone seems to be aware that the auto industry, with mandates from enlightened governments, has made vast progress since the 1970s. It's really unfair. The media shares the blame. Their reporters talk about 'cars' causing air pollution, and then they show a close up of a heavy diesel exhaust, probably an old DetroitDiesel 2-stroke diesel powered bus. It's very misleading, leading to demands for the wrong policies.
PS "The first challenge is in programming the thing..."
It's a neural net. Most of us have some experience programming such things...
It'll take about 20 years. Or 25 years if it happens to adopt the Goth lifestyle along the way.
Hopefully it'll keep its room tidy and not back talk too much.
Last I read, it's not even crystal clear to everyone's satisfaction that the D-wave computers are actually working as they should. Some say yes, others have doubts.
But yes, you're right. Eventually there will be what you're describing. Decades away of course.
I'd expect that eventually, 'only' a decade or so, they'll implement a conventional device where every vulnerability and every side channel is covered. There might be some remaining subtle flaws, but nobody can find them. Effectively perfect. We're orders of magnitude away from that, at the present time. So it's at least 10-15 years away.
Cynic_999 "...60 years...."
You're falling into the same mental trap. 60 years is a time scale that indicates that you're thinking about keys, key length, brute forcing, etc.
The actual time scale is as follows: from introduction, weeks or months until someone is interested or motivated; then just days or weeks until they find the weakness or attack; then minutes or hours to crack their way into any device in their possession.
@John H Woods
I once wrote "It would be extraordinary that the iPhone 5C just happens to represent the first uncrackable encryption system. So many have claimed that, all have failed so far."
You responded (quoting me) in a manner that indicated your faith in the security, "So far AES256 has resisted attacks fairly well." In the context, it appears that you had faith in the purported security of the device.
I was confident that the iPhone in question could be and would be cracked.
Many posted points that indicated that they believed it was quite secure.
As it turns out, I was right. Others were wrong.
Me being right is hardly worth noting. That others can be so oblivious to the endlessly repeating cycles of history (security claims, later being shown false) is the issue.
As a species, we're losing the ability to invoke healthy skepticism. Perhaps we really are descended from telephone sanitizers and hairdressers (ref. D. Adams).
Cheers.
'The History of Cryptography in CCC?'
The CCC presentations are what would be called 'Modern History'. They're often making the history, famously cracking the 'uncrackable'. Several that I've watched included a review of older history for context. Plenty of excellent books on my bookshelf, several feet on this topic (not all read yet).
The repeating patterns in this area are crystal clear:
10: Claims of 'Strong' security.
20: Later shown to be utterly false, daft, naïve, hubris.
30: Vulnerabilities. Side Channels. Clever hardware cracking.
40: NOT brute force of huge keyspace.
50: GOTO 10
This endless loop has played out endless times.
It's happened again just now with this FBI 5C instance. Noobies thought it was secure.
It's just started again at Line 10 with the next generation of iPhones. Noobies post, "Yeah, but the iPhone 6 really is uncrackable." Here we go again... Sigh...
SD3: "This was an iPhone 5c and running iOS 8. We wait for someone to do the same hack on iOS9 running on an 6S."
That's pretty lame... 1st gen - cracked. 3G - cracked. 3GS - cracked. 4 - cracked. 4S - cracked. 5 - cracked. 5C - cracked. ... Are you seeing a trend?
As for iOS, look at the list of vulnerabilities being fixed with iOS 9.3. About a dozen. You think that's the last such update? When people keep finding a dozen needles in the haystack every time they walk past, then you can bet that the haystack is laced with ten thousand more needles. Not even including the new ones that they're pouring in the top (new features, fresh vulnerabilities).
Any rational analysis clearly hints that we're at least a decade or more away from anyone actually implementing an actually uncrackable device. It's naïvite and/or hubris to believe otherwise.
"...a good secure enclave will self-destruct when it is opened."
That's why they practice on a dozen disposable examples to learn about the booby traps, and learn how to avoid or bypass them. Only after it's down to a repeatable exercise would they put the process into 'production'.
Your use of the word 'opened' leads to muddled thinking. The chip doesn't have a door. How does it know that it's been opened? Don't forget, the power is off. There's a half-dozen techniques, but perhaps only one or two new inventions (at most).
@Adam 1
Side Channel attacks don't have to be "SNAFUs". Sometimes they are such blatant design implementation errors (e.g. failing to keep code branches equal clock cycles), but as those are slowly eliminated from newer implementations, there still remains an endless well of subtle design implementation characteristics which can be exploited.
The point here is that even clever and careful designers cannot make an uncrackable device. It'll be decades before the 'Handbook of Side Channel Prevention' is even thought to be complete.
Much of your post is still too focused on key length ("...GDP ...Sun ...hard ...power consumption..."), which COMPLETELY misses the entire point. Nothing in this entire story has anything to do with brute forcing anything. It's a huge mistake to focus on that too-obvious red herring.
AC "Seeing videos isn't the same as understanding what goes on in them, though."
The CCC.de Media presentations are made for the purpose of communicating what's going on. They're highly intelligible, except the ones in German...
The advice is directed to those interested, especially anyone that can't yet drag their thought processes away from the key-length; as someone up a bit has done again ("...GDP....Sun...").
"I see Apple suing over this."
Who? Their staff, their designers?
Crypto designers carry too much hubris. The hubris seems to survive even lessons like this one.
Eventually there will exist an ACTUALLY uncrackable device. I expect we're still decades away from that point. Perhaps if the crypto designers were to adjust their confidence/competence ratio below unity, they might learn faster and cut the horizon to only 10-15 years.
JB77 "...develop and employ stronger encryption."
They didn't 'brute force' anything. They went AROUND the encryption.
Building a taller wall makes no difference when there are other ways in.
Next time maybe it'll take eight weeks, instead of five weeks.
This should be a lesson to all, but apparently some are catching on...
BtC "Every government on the planet now knows that iPhones can be hacked, every cracker knows iPhones can be broken into..."
Only the utterly naïve didn't see this coming...
Seriously, did you really think that the iPhone 5C was the very first uncrackable device in history?
Or have you been ignoring The History of Cryptography?
"...imply there's an exploitable flaw in your devices..."
There's ALWAYS an exploitable flaw in your device.
ALWAYS.
It'll be decades before the first 'perfectly secure' device *actually* exists.
False claims will continue, but you'd have to be pretty naïve to actually believe it.
noyourenotyourewonderful "...need to get that fuel into the engine at 0g..."
It's common to activate some wee thrusters to push the rocket forward, causing the fuel(s) to settle to the 'bottom' of the tanks.
In other words, the 0g ('Floaty McFuelFace') problem is easily sorted.
Prof. Nix "...no more spectrum available..."
Smaller 'cells' is the entire point of cellular.
More and more cell towers, but shorter and shorter.
It's happening in my neighbourhood. They're dropped the antennas about halfway down the original 250+ foot mast, and they keep installing more and more increasingly short towers.
edit: I see your name mentioned in the release. :-)
Question.
"Hence scaling that up to 128 paths demands serious signal processing, carried out by four FPGAs in the Bristol demonstration."
Four total, or four per antenna? Four total isn't much.
Thanks.
AC" "...'social justice' warriors as coming from the left, but they are nothing of the sort. They are right wing authoritarians..."
The political spectrum makes much more sense once you zoom out and can see that it's curved into a circle.
The extremist nutters coming from the extreme left and the extremist nutters coming from the extreme right merge and are perfectly indistinguishable on the far side of the circle. They ragingly overlap in the same frothing puddle of angry spittle. Not even a tiny quanta of difference between them.
Through this larger view, revealing the additional axis of moderation-to-extremism, an improved worldview emerges. It's a much more informative model.
Such software is inevitably built in accordance with the 'full meal deal' (zero 'tailoring' shortcuts), 'one line of code per coder-drone-day', DO-178 process.
So the software CANNOT be 'dodgy', because that's fundamentally impossible.
The software *is* perfect. ...It's the 'Requirements' that were badly written.
E.g. They probably forgot to mention that they'd like the software to actually work.
Stupid Requirements Writers! Puh!
Not to worry. Following the same process, they have it fixed up in only 20 or 25 years...
"Don't ever try to write your own! You will fail, completely, dramatically, and embarrassingly."
That rule applies to far more people and organizations than is widely believed. Orders of magnitude more. Further up the crypto hierarchy than can fit into naive minds.
E.g. Right now, somebody is working the long weekend to crack open a certain 'uncrackable' iPhone.
It's hopeless.
Better read Asimov's 'The Dead Past', because that's exactly where we're headed.
New = secure
Middle age = not secure, but hard to crack
Old age = don't rely on it
Author touched on this towards the end of section 3.
Failures are most often due to subtle flaws, not speed up of brute forcing.
All cryptos seem to fail eventually, and not once has it taken 10^77 years.
MH "...the reason PC sales have slumped is because since around 2009 PCs have reached the performance targets that most people are happy with. Reliability has also improved and therefore most people live with what they’ve got."
Yep. Bad capacitors 1999 - 2007. (https://en.wikipedia.org/wiki/Capacitor_plague)
Computers since 2008 would typically be more reliable (not including HP laptops).
Qty: 1
PN: UFED Touch by Cellebrite.
Status: Urgent
NOTE: Order under Acme Enterprises shell company (DON'T MENTION APPLE!!)
Once they've locked down the next iPhone / iOS, then gosh, Cellebrite is going to have to revise their software to rely on the next vulnerability. That's going to take all week...
'Lost all faith...' has pointed out a key topic. (More upvotes for Laf please.)
Headline = "Could a flash drive’s firmware be hiding undetectable malware?"
Not the flash memory, but the firmware hidden in the ARM processor that's acting as the USB controller.
It's hopeless.
Handcuff suspect to a chair, aim light into face. Demand, "Are you clean?" Suspect answers, "Yes, I'm squeaky clean." Turn around and yell, "He's okay. He told me that he's clean."
That's exactly how IT Security works these days.
Even A. Turing knew that this wasn't going to end well.
On one channel is a 'How It's Made' (factory tour) episode where the bottle making factory is cranking out six brand new beer bottles a second. BLAM BLAM BLAM - glowing bottles flying out in batches of six every second. Thirty dozen beer bottles a minute.
Flick.
On the other channel is a rather-breathless narrator discussing how "...3D Printing is the future of mass manufacturing; within just a few years everything will be made this way...", as the print head slowly goes back, pause, and forth, pause, back, pause, and forth, pause, back, pause, and forth, laying out 100um layer after layer of a crummy plastic bowl.
Flick: six beer bottles a second
Flick: one plastic bowl every 14 hours
Flick: six beer bottles a second
Flick: print head moves left, pause...
Flick: six beer bottles a second
Flick: print head moves right, pause...
.: The narrator is an airhead. It'll need about 18 Moore cycles (doublings of performance) to bridge the gap. Even at only two years per cycle, this promise is at least several decades away.
(Of course, it has its niche applications. No argument.)