Jump to content
nsane.forums

Search the Community

Showing results for tags 'iphone'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Found 7 results

  1. On Wednesday, an anonymous person published the proprietary source code of a core and fundamental component of the iPhone’s operating system. A user named “ZioShiba” posted the closed source code for iBoot—the part of iOS responsible for ensuring a trusted boot of the operating system—to GitHub, the internet’s largest repository of open source code. Jonathan Levin, an iPhone researcher, called it the “biggest leak” in the history of the iPhone. The iBoot code is for iOS 9 and the code is two-years old. But even today, it could help iOS security researchers and the jailbreak community find new bugs and vulnerabilities in a key part of the iPhone’s locked-down ecosystem. The leak of the iBoot source code is not a security risk for most—if any—users, as Apple said in a statement. But it’s an embarrassment for a company that prides itself in secrecy and aggressively goes after leaks and leakers. How does something like this happen? A low-level Apple employee with friends in the jailbreaking community took code from Apple while working at the company’s Cupertino headquarters in 2016, according to two people who originally received the code from the employee. Motherboard has corroborated these accounts with text messages and screenshots from the time of the original leak and has also spoken to a third source familiar with the story. Motherboard has granted these sources anonymity given the likelihood of Apple going after them for obtaining and distributing proprietary, copyrighted software. The original Apple employee did not respond to our request for comment and said through his friend that he did not currently want to talk about it because he signed a non-disclosure agreement with Apple. According to these sources, the person who stole the code didn’t have an axe to grind with Apple. Instead, while working at Apple, friends of the employee encouraged the worker to leak internal Apple code. Those friends were in the jailbreaking community and wanted the source code for their security research. The person took the iBoot source code—and additional code that has yet to be widely leaked—and shared it with a small group of five people. “He pulled everything, all sorts of Apple internal tools and whatnot,” a friend of the intern told me. Motherboard saw screenshots of additional source code and file names that were not included in the GitHub leak and were dated from around the time of this first leak. According to two people who were in that original group, they hadn’t planned on the code ever leaving that circle of friends; a third friend who didn’t want the code but saw it on a friend’s computer also confirmed this account. Eventually, however, the code was shared more widely and the original group of people lost control of its dissemination. "I was really paranoid about it getting leaked immediately by one of us," one of the original people to receive the code told me. "Having the iBoot source code and not being inside Apple...that's unheard of.” “I personally never wanted that code to see the light of day. Not out of greed but because of fear of the legal firestorm that would ensue,” they said. “The Apple internal community is really full of curious kids and teens. I knew one day that if those kids got it they’d be dumb enough to push it to GitHub.” According to the source, if the code had been spread around too much, it could have helped less well-intentioned people create exploits and malicious jailbreaks to attack iPhone users. "It can be weaponized,” they said. “There’s something to be said for the freedom of information, many view this leak to be good. [But] information isn’t free when it inherently violates personal security.” “We did our damnedest best to try to make sure that it got leaked [only after the code] got old,” they added. Around a year after the code was stolen and circulated among the small group of friends, someone inside that group gave it “to someone else who shouldn’t have had it,” one of our sources said. At that point, the story gets murky. No one I spoke to is exactly sure who leaked it outside of the first tight-knit group of friends. And no one knew exactly what happened next. But everyone I spoke to agrees that at some point they lost control of the code and it slowly spread further and further. Motherboard confirmed that this particular source code began circulating more widely in 2017 with a fourth and fifth source who are familiar with the jailbreaking and iPhone research communities. Then in the fall of 2017, people far-removed from that initial group of friends started sharing screenshots of the code in a Discord group of jailbreakers as a way to brag and tease other members of the group, according to one of the people I spoke to. “When I heard about that Discord group, I burned all the copies of iBoot that I had,” they said. “I don't need it anymore, and if this is going public I don't want to be part of leaking it. If it gets out there it gets out there but it is not coming from me.” At that point, however, it was too late. Soon after, someone with a throwaway Reddit account named “apple_internals” posted a link to a Mega archive with the iBoot source code on r/jailbreak. A screenshot of the little noticed Reddit post where the iBoot source code was first shared with the whole internet. Still, very few noticed because the post got automatically removed by a moderator bot. But then Wednesday, it was posted again to GitHub. Both of our sources say they believe that someone not associated with the original leak ultimately posted it on GitHub: “What leaked yesterday isn't even the full leak really. It’s not the original leak—it’s a copy,” one of them said. At that point, it went viral, first inside the jailbreak community, then within the larger iOS security research community. Within hours, infosec Twitter was talking about it, and then we (and the rest of the tech press) wrote about it. Apple declined to answer questions on whether the company knew about the leak before Wednesday, and whether they are investigating. “By design the security of our products doesn’t depend on the secrecy of our source code. There are many layers of hardware and software protections built into our products,” the company said in an emailed statement. On Wednesday, an Apple employee told me they knew of the leak before it was posted on GitHub, but didn’t say when the company learned the code was stolen. “None of this was ever supposed to leave a handful of people, what’s happened is quite disastrous,” one of the people who originally received the code told me. “It’s obviously ended up being a clusterfuck, but the original intentions were non malicious.” Clarification: One line in this post has been changed for clarity because the original phrasing was ambiguous. Apple did not encourage the employee to leak source code; the employee's friends did. source
  2. iPhone Suffers Massive Explosion in Hair Salon, Just Next to Customers Yet another Apple devices catches fire suddenly It’s really a bad day for Apple. After a customer revealed that his AirPods caught fire while listening to music, here’s another report pointing to an iPhone that burst into flames with a huge blast in a hair salon. Details aren’t available right now, but a video published by the Daily Mail shows what appears to be a hair salon in Vietnam, with one woman having her cut and two members of the staff just next to her. CCTV cameras have caught the moment of the explosion, though the video doesn’t clearly show the device, but only the flames generated by the blast. And while these are indeed sketchy details, one of the hair salon employees records the aftermath of the incident, revealing that the phone allegedly causing the massive blast was actually an iPhone. Now word from Apple By the looks of things, it’s an iPhone 6s, but again, without any specifics known at this point, it’s hard to take this video for granted for the time being. And yet, this isn’t the first iPhone that catches fire, though there could be lots of factors causing the battery to overheat and to eventually burst into flames. In many cases, third-party chargers or cables can lead to such damage, and this is one of the reasons phone makers in general, and Apple in particular, recommends using only genuine and certified accessories. Apple hasn’t commented on this new incident, but there’s no doubt the company will at least try to investigate. The worst is that Cupertino is likely to remain tight-lipped on what exactly happened, so we’ll never know if the blast was caused by a broken accessory or a device issue. In the meantime, you better keep an eye on your smartphones whenever they’re charging, though recent incidents have shown that such blasts are possible even when not plugged in if hardware issues are involved. Source
  3. We all know that smartphone batteries can catch fire or explode in rare circumstances – something the folks at Samsung found out all too readily with the Galaxy Note 7 last year. Apple is no stranger to battery issues itself either, but a new report out of China by Taiwan News suggests that one of its iPhones exploded for a rather strange reason indeed. According to the report, a man went into a third-party retailer in order to have the battery on his iPhone replaced. Apparently, he had some doubts over the authenticity of the battery itself, with the only way of confirming it apparently being to bite into it. The end result? Well, let’s just say he is unlikely to go biting into batteries any time soon. Thankfully, nobody was injured during these somewhat surreal events, although when the man bit into the battery, it did explode in what can only be described as fairly big ball of flames. Perhaps the most amazing thing about all this is that the whole episode was captured on the store’s security cameras, meaning we can witness it in full color. We, of course, would not recommend doing this, even if you have a suspicion that the battery you are being given is not 100% genuine. If anything, if the battery is a knock-off then it’s even more likely that it will not take too kindly to being bitten, increasing the risk of an explosion. Our recommendation would be to head to an Apple Store or an Apple authorized retailer to get the battery checked out if you have any doubts at all. Check the video out and witness just what can happen when an iPhone’s battery is maltreated; it’s quite a sight to behold! (Via: Taiwan News | Video via: 9to5Mac [YouTube]) Redmondpie.com
  4. Of the many new features in Apple’s iOS 11—which hit your iPhone a few weeks ago—a tool called Core ML stands out. It gives developers an easy way to implement pre-trained machine learning algorithms, so apps can instantly tailor their offerings to a specific person’s preferences. With this advance comes a lot of personal data crunching, though, and some security researchers worry that Core ML could cough up more information than you might expect—to apps that you’d rather not have it. Core ML boosts tasks like image and facial recognition, natural language processing, and object detection, and supports a lot of buzzy machine learning tools like neural networks and decision trees. And as with all iOS apps, those using Core ML ask user permission to access data streams like your microphone or calendar. But researchers note that Core ML could introduce some new edge cases, where an app that offers a legitimate service could also quietly use Core ML to draw conclusions about a user for ulterior purposes. "The key issue with using Core ML in an app from a privacy perspective is that it makes the App Store screening process even harder than for regular, non-ML apps," says Suman Jana, a security and privacy researcher at Columbia University, who studies machine learning framework analysis and vetting. "Most of the machine learning models are not human-interpretable, and are hard to test for different corner cases. For example, it's hard to tell during App Store screening whether a Core ML model can accidentally or willingly leak or steal sensitive data." The Core ML platform offers supervised learning algorithms, pre-trained to be able to identify, or "see," certain features in new data. Core ML algorithms prep by working through a ton of examples (usually millions of data points) to build up a framework. They then use this context to go through, say, your Photo Stream and actually "look at" the photos to find those that include dogs or surfboards or pictures of your driver's license you took three years ago for a job application. It can be almost anything. 'It's hard to tell during App Store screening whether a Core ML model can accidentally or willingly leak or steal sensitive data.' Suman Jana, Columbia University For an example of where that could go wrong, thing of a photo filter or editing app that you might grant access to your albums. With that access secured, an app with bad intentions could provide its stated service, while also using Core ML to ascertain what products appear in your photos, or what activities you seem to enjoy, and then go on to use that information for targeted advertising. This type of deception would violate Apple's App Store Review Guidelines. But it may take some evolution before Apple and other companies can fully vet the ways an app intends to utilize machine learning. And Apple's App Store, though generally secure, does already occasionally approve malicious apps by mistake. Attackers with permission to access a user's photos could have found a way to sort through them before, but machine learning tools like Core ML—or Google's similar TensorFlow Mobile—could make it quick and easy to surface sensitive data instead of requiring laborious human sorting. Depending on what users grant an app access to, this could make all sorts of gray behavior possible for marketers, spammers, and phishers. The more mobile machine learning tools exist for developers, the more screening challenges there could be for both the iOS App Store and Google Play. Core ML does have a lot of privacy and security features built in. Crucially, its data processing occurs locally on a user's device. This way, if an app does surface hidden trends in your activity, and heartbeat data from Apple's Health tool, it doesn't need to secure all that private information in transit to a cloud processor and then back to your device. That approach also cuts down on the need for apps to store your sensitive data on their servers. You can use a facial recognition tool, for instance, that analyzes your photos, or a messaging tool that converts things you write into emojis, without that data ever leaving your iPhone. Local processing also benefits developers, because it means that their app will function normally even if a device loses internet access. iOS apps are only just starting to incorporate Core ML, so the practical implications of the tool remain largely unknown. A new app called Nude, launched on Friday, uses Core ML to promote user privacy by scanning your albums for nude photos and automatically moving them from the general iOS Camera Roll to a more secure digital vault on your phone. Another app scanning for sexy photos might not be so respectful. A more direct example of how Core ML could facilitate malicious snooping is a project that takes the example of the iOS "Hidden Photos" album (the inconspicuous place photos go when iOS users "hide" them from the regular Camera Roll). Those images aren't hidden from apps with photo access permissions. So the project converted an open-source neural network that finds and ranks illicit photos to run on Core ML, and used it to comb through test examples of the Hidden Photos album to quickly rate how salacious the images in it were. In a comparable real-world scenario, a malicious dev could use Core ML to find your nudes. Researchers are quick to note that while Core ML introduces important nuances—particularly to the app-vetting process—it doesn't necessarily represent a fundamentally new threat. "I suppose CoreML could be abused, but as it stands apps can already get full photo access," says Will Strafach, an iOS security researcher and the president of Sudo Security Group. "So if they wanted to grab and upload your full photo library, that is already possible if permission is granted." The easier or more automated the trawling process becomes, though, the more enticing it may look. Every new technology presents potential gray sides; the question now with Core ML is what sneaky uses bad actors will find for it along with the good. Article
  5. Aiseesoft FoneEraser Free License - v1.0.22 Aiseesoft FoneEraser with this tool you can erase all iPhone content and settings permanently and thoroughly. Description Aiseesoft FoneEraser the most powerful utility to delete all the iPhone content and settings permanently and safely. Offers optional three levels to clear, you can delete to protect your privacy, all data on iPhone / iPad / iPod. In addition, you can remove all files and settings on multiple devices simultaneously to save your time. Screenshot Giveaway Page Instructions Visit giveaway page Complete name and email (top right hand corner of page) -use disposable email Key and download link will be forwarded to you via email Promo page is in German - use Google Translate if necessary download link
  6. The overpriced, and mostly unnecessary iPhone X is what happens when the elite stop caring about appearances and start producing products expressly for the rich. Therefore, it only makes sense that, if you're going to have a fuck-you iPhone, you might as well have the fuck-you iPhone case as well. Meet the iPhone X Elite 24k Gold Edition. Yes, it's covered in actual gold, not just the color. Offered by London-based Goldgenie, the actual product is an Apple iPhone X (no affiliation with Apple) that is custom-plated in gold, rose gold, or platinum metal. The customized iPhone is presented in cherry oak finished box — just an additional touch of faux premium in case you ever have doubts about your financial sanity in the middle of the night and need a little reassurance in the form of product framing. But you want to know how much it costs, so let's just get to it: about $3,700, all in, for the 256GB model (£2,797). And if, for some reason, you have the ego necessary to justify buying this, but decide to save a few bucks, you can get the 64GB version for just around $3,570 (about £2697). Scoff all you want, but a gold-plated iPhone X makes a certain kind of narcissistic sense. After all, the most notable differences between the iPhone 8 and the iPhone X are Face ID and the ability to send Animoji texts using you face. Reality Check: If you don't care about taking selfies, you might as well get an iPhone 8. So while you quietly judge those willing to pay roughly $1,200 for a smartphone whose main feature is rewarding you for pointing your face at it, somewhere, the unapologetically tacky are already trying to figure out if they prefer their selfie iPhone in gold, or the less gaudy platinum. Fuck you, peasant. Clic View article complete and Source
  7. Apple suffers 'major iPhone X leak' Developers are still scouring the leaked code for fresh discoveries Details of new iPhones and other forthcoming Apple devices have been revealed via an apparent leak. Two news sites were given access to an as-yet-unreleased version of the iOS operation system. The code refers to an iPhone X in addition to two new iPhone 8 handsets. It also details facial recognition tech that acts both as an ID system and maps users' expressions onto emojis. One tech writer said it was the biggest leak of its kind to hit the firm. Apple is holding a launch event at its new headquarters on Tuesday. The California-based company takes great efforts to keep its technologies secret until its showcase events, and chief executive Tim Cook spoke in 2012 of the need to "double down" on concealment measures. Some details about the new devices had, however, already been revealed in August, when Apple published some test code for its HomePod speakers. But while that was thought to have been a mistake, it has been claimed that the latest leak was an intentional act of sabotage. "As best I've been able to ascertain, these builds were available to download by anyone, but they were obscured by long, unguessable URLs [web addresses]," wrote John Gruber, a blogger known for his coverage of Apple. "Someone within Apple leaked the list of URLs to 9to5Mac and MacRumors. I'm nearly certain this wasn't a mistake, but rather a deliberate malicious act by a rogue Apple employee." Neither Mr Gruber nor the two Apple-related news sites have disclosed their sources. However, the BBC has independently confirmed that an anonymous source provided the publications with links to iOS 11's gold master (GM) code that downloaded the software from Apple's own computer servers. GM is a term commonly used by software firms to indicate that they believe a version of a product is ready for release. "More surprises were spoiled by this leak than any leak in Apple history," Mr Gruber added. Apple could not be reached for comment. Several developers are still scouring the leak for new features, but discoveries so far include: - a reference to iPhone X, which acts as fresh evidence that Apple intends to unveil a high-end model alongside more modest updates to its handset line -images of a new Apple Watch and AirPod headphones -a set-up process for Face ID - an alternative to the Touch ID system fingerprint system - that says it can be used to unlock handsets and make online purchases from Apple, among other uses -the introduction of Animoji - animated emoji characters that mirror a user's captured facial expressions More at Source
×