from the you-will-have-good-luck-if-you-forward-this-message-to-ten-of-your-friends dept.
There's a new bug floating around called "chaiOS" that appears to be a basic GitHub link. However, when you text it to a person via the iMessage app (whether on iOS or MacOS), it will crash the app and possibly cause the device to freeze and restart. In other words: Be aware that this exists, but don't send it to anyone.
It was Twitter user Abraham Masri who first uncovered the bug. The people over at 9to5Mac tested it out, and it certainly messed up their devices. They reported crashes and severe lags as a result of the bugs that persisted until the thread containing the link was deleted from the iMessage app. If you did send or receive it, and your device is a mess, there's also a fix in the replies to Masri's original tweet. We've reached out to Apple to confirm that their team is aware of the bug, and to see if there are any fixes in the works.
Source: EnGadget
(Score: 0) by Anonymous Coward on Friday January 19 2018, @07:58AM
C'mon, where's the fun in that? iOS or MacOS, right? They probably deserve it, espeically if they are people whose contact info I have! Ha ha ha ha ha! Eat freeze, Apple fools!
(Score: 0) by Anonymous Coward on Friday January 19 2018, @08:08AM (3 children)
Why would certain words crash the app?
(Score: 2) by maxwell demon on Friday January 19 2018, @08:15AM (1 child)
That "word" is a link. Special processing for links (e.g. to allow you to follow it by just clicking/tapping on it) is quite common. Although it certainly shouldn't crash you app or freeze your device.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 0) by Anonymous Coward on Friday January 19 2018, @08:30AM
I guess message preview pane is still the devils since ye old Outlook 97 days, at least according to an older bug https://9to5mac.com/community/the-latest-iphone-security-vulnerability-imessages-bug/. [9to5mac.com]
(Score: 3, Insightful) by All Your Lawn Are Belong To Us on Friday January 19 2018, @03:11PM
maxwell demon answered the technical side, but the ecosystem answer is different:
Because:
A) Basic networking design still does not have security-by-design baked into it, and:
B) People want things to happen like pre-fetch of content or extended information about things like weblinks, which is inherently INsecure.
C) NB: One should never trust a connection where any actor can send you a message or content, but everyone wants convenience that requires trust to be randomly extended to all.
Or in other words, it's an extension of people not applying basic critical thinking to computers: The users, the designers, and most especially the people making money off of it.
This sig for rent.
(Score: 2) by WizardFusion on Friday January 19 2018, @10:23AM (5 children)
For the lazy, the link is
https://t.co/Ln93XN51Kq [t.co]
That's right, head over to https://t.co/Ln93XN51Kq/ [t.co] and check it out.
Once more, it's https://t.co/Ln93XN51Kq/ [t.co]
(Score: 2) by coolgopher on Friday January 19 2018, @11:54AM (3 children)
Are you sure? I only got a 404 page...
(Score: 2) by WizardFusion on Friday January 19 2018, @12:41PM (2 children)
It was, twitter have taken it down :(
(Score: 1, Informative) by Anonymous Coward on Friday January 19 2018, @12:57PM (1 child)
Fuck twatter. Fortunately we can recover the link https://web.archive.org/web/20180117063656/https://iabem97.github.io/chaiOS/ [archive.org]
No guarantees but fingers crossed. Apparently the thing is meta property="og:title" content=some funny stuff which goes on for a bit.
(Score: 1) by mmh on Friday January 19 2018, @05:51PM
Interestingly, in Pale Moon 26.5 on Fedora, it causes the browser is use 100% CPU for very long periods of time. Grabbing it with curl, it's just a 12MB file.
(Score: 1, Informative) by Anonymous Coward on Friday January 19 2018, @06:33PM
This is a "working" link:
https://web.archive.org/web/20180117063656/https://iabem97.github.io/chaiOS/ [archive.org]
The document contains a meta property="og:title" content=$FOO
with FOO a 4 MB string with a bunch of non-ASCII chars.
Might be a buffer overflow.