Is this a story about iOS malware? Then you should require the answer to this question:
1. DOES IT REQUIRE JAILBREAK?
The only *interesting* iOS malware story is one that does not require jailbreak. I'm not aware of any; there may be some that use known or unknown exploits, but in this case the malware requires the user to have a jailbroken phone. That's not news or "stuff that matters".
Sincerely,
Slashdot Readers
When I'm driving in France, I switch my sat-nav to metric and I'm done. I have no problem switching between the two measurement systems at all. If you think you'd have a problem, I guarantee you are wrong. At the worst case, it'll take you a few weeks.
British cars have the speedometer marked in mph and km/h. It would be a few weeks and then everything would be back to normal.
My French teacher (who was English) reckoned that everybody should use a comma (like the French) for the decimal separator because it was actually the only important piece of punctuation in numbers and therefore should be more obvious than just a dot.
Well Kitkat is apparently making good inroads as it went from 13.6% in June to 24.5% [android.com] in early September
iOS 8 was at 46 percent after four days. Obviously, since Apple control all the hardware, it's much easier for them to get people to upgrade, but it's still a big problem for the Android ecosystem. Presumably, app developers are having to support fairly ancient versions of the operating system in order to reach a sizeable proportion of the market, whereas an iOS developer can reach 95% of the installed base with an iOS7+ app.
This is Swift. You just need a file called main.swift with this in it:
CreateGameThatIsSortOfLikeAngryBirdsAndMakeMeMillionsOfDollarsOvernight()
See... Swift is so good it's reduced your code size by 80% (including the missing line to return 0).
It's actually the second article in a series. The first article looks like it had some Swift in it.
No doubt there will be a new Slashdot story for each subsequent article. Because Swift.
Development novices who were hoping that Apple had created a way to build complex apps with a limited amount of actual coding might have to spend a bit more time learning the basics before embarking on the big project of their dreams.
Is anybody at all surprised except, maybe, said novices?
OS X comes with csh, bash, ksh and zsh. If you delete the link from sh to bash and replace it with a hard link to zsh, it probably secures your Mac.
You're probably not running a bash that isn't vulnerable. Neither of the first two patches completely fixed the issue. Personally, I don't think it'll be completely fixed until somebody patches bash to not interpret any of its environment variables as functions.
Which it should never have done in the first place.
So, my normal speaking voice then.
In later models, i.e. well after the 6502 was obsolete for general purpose computers, there was an 8 register that you could set to change which page was regarded as zero page. If that had been available from the start, it would have saved me a lot of time looking for locations that didn't zap the MS Basic interpreter on our Commodore PET. I seem to remember that the floating point accumulators were considered the best bet.
The 6502 had special addressing modes for accessing the bottom 256 bytes of memory. Addresses in both the 6502 and Z80 were 16 bit, thus taking two read cycles to get a whole address into the CPU so that you could then get the content at the address. However, with the 6502, "zero page" addresses could be read in one read cycle. Not only that, but pairs of zero page locations could be used for indirect addressing. They could be treated as a set of (slow) address registers.
When I first came actress the Z80 after having programmed the 6502 for a while (as a hobbyist), I was quite shocked at how all over the place its design appeared to be and I actually found it a little harder to program at first because there was more to learn in order to use the CPU effectively.
Exactly. This whole feature is ill conceived madness. For one thing it means that if I want an exported legitimate environment variable that starts with parentheses, I can't then use it in a forked bash session.
What were they thinking of?
Suppose you are a guest at my house and you want to ssh into your own computer at your house. I say no problem and I create you a user account on my computer which you then use to ssh to your computer.
Still don't think it's a problem?
Of course I could also have a key logger installed.
Wouldn't it also display
grep mysekritpassword
in a ps -ef listing?
The key elements in human thinking are not numbers but labels of fuzzy sets. -- L. Zadeh
