Another great ABC story John but if I get this right my IOS devices have been at risk for the last 10 years of being hacked due to some flaw in a chip. This is not only true of apple devices but also android devices, apparently there is going to be a patch put out by Apple and the other manufacturers in the coming days to fix it. So why suddenly this huge concern and what are we supposed to do about it anyhow throw all all our devices away or just not use them ?
-- Edited by rockylizard on Saturday 6th of January 2018 02:36:50 PM
The Belmont Bear said
03:10 PM Jan 6, 2018
You can put a dozen articles saying the same thing but my comment is still the same what do you want us to do differently apparently this has been a rsk for 10 years ? Smells a bit like the Y2k bug where the computing industry made billions helping people to avoiid what was probably a non existent problem.
rockylizard said
03:15 PM Jan 6, 2018
Gday...
Cheers - John
RustyD said
03:58 PM Jan 6, 2018
The Y2K bug was real. I worked for many years on it, starting in the early 1980s when forecasting went beyond Dec 31, 1999. HR systems had already been re-written to cope with actuarial forecasts beyond 2000. Then I was full time from 1996. Dates were stored in computers in YYMMDD format for sorting. Dec 31, 1999 was 991231. The next day was 000101 so all date sorting, forecasting were going to go haywire. The fact that no one was effected by the Y2K bug was a testament to the amount of money and effort that was put into eliminating this potential disaster. Date format was changed to CCYYMMDD in existing systems (19991231 then 20000101). New systems used a date relative to something like 1/Jan/1900 with dates before being negative & dates after being positive. 28/Dec/1899 was -3 and 3/Jan1900 was +3.
Some computers stored dates in Julian format (YYMMM) where mmm is the day number in the year. Today being 18006. These dates became CCYYMMM (2018006). This is easier to count days and the new +/- days offers similar simplicity behind the scenes.
-- Edited by RustyD on Saturday 6th of January 2018 04:03:38 PM
The Belmont Bear said
04:02 PM Jan 6, 2018
John as usual you are very clever at attaching links or cartoons to back up your points of view but in this case Im still waiting for you to give us one. I have read your articles, I understand the risks but for the 3rd time (and I can only assume its all true) what are they recommending that people like me do differently ?
RustyD said
04:12 PM Jan 6, 2018
There has always been weaknesses in Microsoft (Windows) and Apple (IOS) systems / chips. As Microsoft had a massive market share compared to Apple and Apple users tended to be more computer savvy and didn't download stuff of the internet willy-nilly, hackers only concentrated on Microsoft products and applications. However with the prolific growth of Apple & Android phones & tablets, not sure if this is still the case. Just hope that the OS writers are keeping one step ahead of the hackers.
rockylizard said
04:15 PM Jan 6, 2018
The Belmont Bear wrote:
John as usual you are very clever at attaching links or cartoons to back up your points of view?????? but in this case I'm still waiting for you to give us one. I have read your????? articles, I understand the risks but for the 3rd time (and I can only assume its all true) what are they recommending that people like me do differently ?
Gday...
Fer gawd's sake ...... they are not MY articles ... they are links to information released via media by Apple concerning issues they have discovered and advising they are instigating remedial measures ... apparently in upcoming releases.
I have no opinion or knowledge or 'point of view' or advice to offer you, fer gawd's sake ..... I am but the messenger of information, verified information, that would quite probably be of interest to those who have machines that are within the remit of the advice from Apple.
I posted the links, it is up to you to read it ... absorb (or discard) the information .. and make up your own damned mind on what you want (or not want) to do with it.
cheers - - John
The Belmont Bear said
04:52 PM Jan 6, 2018
rockylizard wrote:
The Belmont Bear wrote:
John as usual you are very clever at attaching links or cartoons to back up your points of view?????? but in this case I'm still waiting for you to give us one. I have read your????? articles, I understand the risks but for the 3rd time (and I can only assume its all true) what are they recommending that people like me do differently ?
Gday...
Fer gawd's sake ...... they are not MY articles ... they are links to information released via media by Apple concerning issues they have discovered and advising they are instigating remedial measures ... apparently in upcoming releases.
I have no opinion or knowledge or 'point of view' or advice to offer you, fer gawd's sake ..... I am but the messenger of information, verified information, that would quite probably be of interest to those who have machines that are within the remit of the advice from Apple.
I posted the links, it is up to you to read it ... absorb (or discard) the information .. and make up your own damned mind on what you want (or not want) to do with it.
cheers - - John
John my first response to your original post was that it was an interesting article by the ABC (not you) but as the problem had existed for some time I couldnt see what I could do differently = this was made as a general comment on the article and was only my point of view. You responded by posting more links to articles along with some cartoon suggesting perhaps i was a little slow. Again I suggested that although I understand that this is a problem none of those links tell me what I could do differently. Your response was another even more sarcastic cartoon - you dont like my reaction then start thinking about what you are posting, you may see these cartoons as being funny or smart those you direct them against may interpret them as being insulting.
rockylizard said
05:03 PM Jan 6, 2018
The Belmont Bear wrote:
Another great ABC story John but if I get this right my IOS devices have been at risk for the last 10 years of being hacked due to some flaw in a chip. This is not only true of apple devices but also android devices, apparently there is going to be a patch put out by Apple and the other manufacturers in the coming days to fix it. So why suddenly this huge concern and what are we supposed to do about it anyhow throw all all our devices away or just not use them ?
Cheers BB
Gday...
HMMMMM ... your words above seem to be a little in contradiction to your initial response -
The Belmont Bear wrote:
Another great ABC story John
Perhaps I read those words a bit too literally ... "another great ABC story" struck me as just another sarky response regarding the ABC's reputation as being the purveyor of stories written poorly, or biased.
Judging by your twisted knickers it seems I was a trifle hasty
Cheers - John
The Belmont Bear said
06:28 PM Jan 6, 2018
Fair enough John lets call a halt to our verbal jousting, to tell you the truth although I am not a great fan of the ABC I dont actually watch it or use any of their services so Im not in the best position to judge how effectively they do their job. All I know is I have to go back to work tomorrow so I can send nearly half what I earn back to the Australian government in order to help them fund (or add to the credit card)everything that they have committed to and that includes our public broadcaster.
rockylizard said
07:21 PM Jan 6, 2018
Gday...
Praps to help you feel more altruistic - think of it this way ... all that money you are going to send back to Strayan Guv'n'ment is helping to fund the pensions of many on this forum.
Think on how your contributions are assisting many to travel this wide brown exciting land - making their grateful donations into those honesty boxes at the 'free' camps all over the place.
cheers - - John
dabbler said
09:38 PM Jan 6, 2018
RustyD has it right. The resources expended to ensure Y2K was a non-issue was quite a burden on most organizations. Add to that the effort required to ready some systems for GST made 2001 a welcome sight.
Apple devices have never really been immune from attack despite the general belief and personal devices of all types aren't immune from social engineering either. Whatever you use, devote the necessary bandwidth to keeping it up to.date in a timely fashion.
As an aside, the only software I encountered that wasn't and couldn't be patched for Y2K was an Apple messagng system and the only fix was a total replacement at outrageous Apple pricing.
dorian said
07:37 AM Jan 7, 2018
Here is official information (from links in the ABC article):
If your computer has a vulnerable processor and runs an unpatched operating system, it is not safe to work with sensitive information without the chance of leaking the information. This applies both to personal computers as well as cloud infrastructure. Luckily, there are software patches against Meltdown. Spectre is harder to exploit than Meltdown, but it is also harder to mitigate. However, it is possible to prevent specific known exploits based on Spectre through software patches.
Is there a workaround/fix?
There are patches against Meltdown for Linux ( KPTI (formerly KAISER)), Windows, and OS X. There is also work to harden software against future exploitation of Spectre, respectively to patch software after exploitation through Spectre ( LLVM patch, ARM speculation barrier header). Which systems are affected by Meltdown?
Desktop, Laptop, and Cloud computers may be affected by Meltdown. More technically, every Intel processor which implements out-of-order execution is potentially affected, which is effectively every processor since 1995 (except Intel Itanium and Intel Atom before 2013). We successfully tested Meltdown on Intel processor generations released as early as 2011. Currently, we have only verified Meltdown on Intel processors. At the moment, it is unclear whether ARM and AMD processors are also affected by Meltdown.
Which systems are affected by Spectre?
Almost every system is affected by Spectre: Desktops, Laptops, Cloud Servers, as well as Smartphones. More specifically, all modern processors capable of keeping many instructions in flight are potentially vulnerable. In particular, we have verified Spectre on Intel, AMD, and ARM processors. Which cloud providers are affected by Meltdown?
Cloud providers which use Intel CPUs and Xen PV as virtualization without having patches applied. Furthermore, cloud providers without real hardware virtualization, relying on containers that share one kernel, such as Docker, LXC, or OpenVZ are affected.
BTW "Belmont Bear", which is your preferred news source?
Gday...
Click here for article
Cheers - John
Another great ABC story John but if I get this right my IOS devices have been at risk for the last 10 years of being hacked due to some flaw in a chip. This is not only true of apple devices but also android devices, apparently there is going to be a patch put out by Apple and the other manufacturers in the coming days to fix it. So why suddenly this huge concern and what are we supposed to do about it anyhow throw all all our devices away or just not use them ?
Cheers BB
Gday...
Better read this one too then
Or maybe this one
Ya want a couple more?
Cheers - John
-- Edited by rockylizard on Saturday 6th of January 2018 02:36:50 PM
You can put a dozen articles saying the same thing but my comment is still the same what do you want us to do differently apparently this has been a rsk for 10 years ? Smells a bit like the Y2k bug where the computing industry made billions helping people to avoiid what was probably a non existent problem.
Gday...
Cheers - John
The Y2K bug was real. I worked for many years on it, starting in the early 1980s when forecasting went beyond Dec 31, 1999. HR systems had already been re-written to cope with actuarial forecasts beyond 2000. Then I was full time from 1996. Dates were stored in computers in YYMMDD format for sorting. Dec 31, 1999 was 991231. The next day was 000101 so all date sorting, forecasting were going to go haywire. The fact that no one was effected by the Y2K bug was a testament to the amount of money and effort that was put into eliminating this potential disaster. Date format was changed to CCYYMMDD in existing systems (19991231 then 20000101). New systems used a date relative to something like 1/Jan/1900 with dates before being negative & dates after being positive. 28/Dec/1899 was -3 and 3/Jan1900 was +3.
Some computers stored dates in Julian format (YYMMM) where mmm is the day number in the year. Today being 18006. These dates became CCYYMMM (2018006). This is easier to count days and the new +/- days offers similar simplicity behind the scenes.
-- Edited by RustyD on Saturday 6th of January 2018 04:03:38 PM
John as usual you are very clever at attaching links or cartoons to back up your points of view but in this case Im still waiting for you to give us one. I have read your articles, I understand the risks but for the 3rd time (and I can only assume its all true) what are they recommending that people like me do differently ?
Gday...
I have no opinion or knowledge or 'point of view' or advice to offer you, fer gawd's sake ..... I am but the messenger of information, verified information, that would quite probably be of interest to those who have machines that are within the remit of the advice from Apple.
I posted the links, it is up to you to read it ... absorb (or discard) the information .. and make up your own damned mind on what you want (or not want) to do with it.
cheers -
- John
John my first response to your original post was that it was an interesting article by the ABC (not you) but as the problem had existed for some time I couldnt see what I could do differently = this was made as a general comment on the article and was only my point of view. You responded by posting more links to articles along with some cartoon suggesting perhaps i was a little slow. Again I suggested that although I understand that this is a problem none of those links tell me what I could do differently. Your response was another even more sarcastic cartoon - you dont like my reaction then start thinking about what you are posting, you may see these cartoons as being funny or smart those you direct them against may interpret them as being insulting.
Gday...
HMMMMM ... your words above seem to be a little in contradiction to your initial response -
The Belmont Bear wrote:
Another great ABC story John
Perhaps I read those words a bit too literally ... "another great ABC story" struck me as just another sarky response regarding the ABC's reputation as being the purveyor of stories written poorly, or biased.
Judging by your twisted knickers it seems I was a trifle hasty
Cheers - John
Fair enough John lets call a halt to our verbal jousting, to tell you the truth although I am not a great fan of the ABC I dont actually watch it or use any of their services so Im not in the best position to judge how effectively they do their job. All I know is I have to go back to work tomorrow so I can send nearly half what I earn back to the Australian government in order to help them fund (or add to the credit card)everything that they have committed to and that includes our public broadcaster.
Gday...
Praps to help you feel more altruistic - think of it this way ... all that money you are going to send back to Strayan Guv'n'ment is helping to fund the pensions of many on this forum.
Think on how your contributions are assisting many to travel this wide brown exciting land - making their grateful donations into those honesty boxes at the 'free' camps all over the place.
cheers -
- John
Here is official information (from links in the ABC article):
Meltdown and Spectre:
https://meltdownattack.com
BTW "Belmont Bear", which is your preferred news source?