Tachy0n is a permanent, unpatchable jailbreak for all bootroms from checkm8-vulnerable devices (A5-A11 on iOS 14.x). Leveraging a hardware vulnerability, it modifies the Secure Enclave Processor (SEP) firmware, enabling persistent code execution even after updates or restores. This effectively removes Apple's ability to revoke the jailbreak through software updates. While powerful, Tachy0n is primarily a research project and a proof-of-concept, currently lacking the user-friendly tools of a typical jailbreak. It aims to lay the groundwork for future jailbreaks and serve as a secure platform for experimentation and research on Apple's security systems.
To secure President Obama's BlackBerry, the NSA developed a custom, highly-secured device nicknamed the Sectera Edge. It featured strong encryption, limited functionality (like no camera), and a heavily modified operating system to prevent malware and hacking. Only a small number of pre-screened contacts could communicate with the President through this device, and all communications were routed through secure government servers. Essentially, it was a stripped-down BlackBerry designed solely for secure communication, sacrificing features for unparalleled protection.
Hacker News users discussed the logistical and security challenges of securing a President's mobile device. Several commenters highlighted the inherent conflict between security and usability, questioning the actual functionality of Obama's secured BlackBerry. Some expressed skepticism about the claimed level of security, suggesting that a truly secure device would be severely limited in its capabilities. Others pointed out the irony of securing a device primarily used for communication with people likely using less secure devices, making the overall communication chain vulnerable. The discussion also touched on the use of hardware security modules and the difficulty in verifying the implementation of such security measures. A few users commented on the age of the article and how technology has changed since its publication.
GrapheneOS, a privacy and security-focused mobile operating system, has released an experimental build for the Pixel 9a (codename "bluejay"). This release marks initial support for the device, but is considered experimental and may have some instability. Users are cautioned that this build is not yet suitable for daily use due to the potential for bugs and incomplete features. While core functionality like calls, messaging, and camera access should work, further testing and development are ongoing before it reaches a stable, recommended state. The announcement encourages users to report any issues they encounter to help improve the build.
Hacker News users discussed the experimental Pixel 9a GrapheneOS release, expressing excitement but also caution. Several praised GrapheneOS's security focus and the expansion of supported devices. Some questioned the practicality of using a less mainstream OS and potential compatibility issues with apps. The discussion also touched on the challenges of maintaining a hardened OS and the trade-offs between security and convenience. A few users shared their positive experiences with GrapheneOS on other Pixel devices, while others raised concerns about the "experimental" tag and potential bugs. Overall, the sentiment was positive but tempered with pragmatic considerations.
The post "Everyone knows all the apps on your phone" argues that the extensive data collection practices of mobile advertising networks effectively reveal which apps individuals use, even without explicit permission. Through deterministic and probabilistic methods linking device IDs, IP addresses, and other signals, these networks can create detailed profiles of app usage across devices. This information is then packaged and sold to advertisers, data brokers, and even governments, allowing them to infer sensitive information about users, from their political affiliations and health concerns to their financial status and personal relationships. The post emphasizes the illusion of privacy in the mobile ecosystem, suggesting that the current opt-out model is inadequate and calls for a more robust approach to data protection.
Hacker News users discussed the privacy implications of app usage data being readily available to mobile carriers and how this data can be used for targeted advertising and even more nefarious purposes. Some commenters highlighted the ease with which this data can be accessed, not just by corporations but also by individuals with basic technical skills. The discussion also touched upon the ineffectiveness of current privacy regulations and the lack of real control users have over their data. A few users pointed out the potential for this data to reveal sensitive information like health conditions or financial status based on app usage patterns. Several commenters expressed a sense of resignation and apathy, suggesting the fight for data privacy is already lost, while others advocated for stronger regulations and user control over data sharing.
Verichains' analysis reveals that several Vietnamese banking apps improperly use private iOS APIs, potentially jeopardizing user security and app stability. These apps employ undocumented functions to gather device information, bypass sandbox restrictions, and manipulate UI elements, likely in pursuit of enhanced functionality or anti-fraud measures. However, reliance on these private APIs violates Apple's developer guidelines and creates risks, as these APIs can change without notice, leading to app crashes or malfunctions. Furthermore, this practice exposes users to potential security vulnerabilities that malicious actors could exploit. The report details specific examples of private API usage within these banking apps and emphasizes the need for developers to adhere to official guidelines for a safer and more reliable user experience.
Several Hacker News commenters discuss the implications of the Verichains blog post, focusing on the potential security risks of using private APIs. Some express surprise at the prevalence of this practice, while others point out that using private APIs is a common, though risky, way to achieve certain functionalities not readily available through public APIs. The discussion touches on the difficulty of Apple enforcing its private API rules, particularly in regions like Vietnam where regulatory oversight might be less stringent. Commenters also debate the ethics and pragmatism of this practice, acknowledging the pressure developers face to deliver features quickly while also highlighting the potential for instability and security vulnerabilities. The thread includes speculation about whether the use of private APIs is intentional or due to a lack of awareness among developers.
Mobile Verification Toolkit (MVT) helps investigators analyze mobile devices (Android and iOS) for evidence of compromise. It examines device backups, file system images, and targeted collections, looking for artifacts related to malware, spyware, and unauthorized access. MVT checks for indicators like jailbreaking/rooting, suspicious installed apps, configuration profiles, unusual network activity, and signs of known exploits. The toolkit provides detailed reports highlighting potential issues and aids forensic examiners in identifying and understanding security breaches on mobile platforms.
HN users discuss the practicality and legality of MVT (Mobile Verification Toolkit), a tool for forensic analysis of mobile devices. Some express concerns about the complexity of interpreting the results and the potential for false positives, emphasizing the need for expertise. Others debate the legality of using such tools, especially in employment contexts, with some suggesting potential violations of privacy laws depending on the jurisdiction and the nature of the data collected. A few commenters point out that the tools are valuable but must be used responsibly and ethically, recommending comparing results against a known good baseline and considering user privacy implications. The utility for average users is questioned, with the consensus being that it's more suited for professionals in law enforcement or corporate security. Finally, alternative tools and resources are mentioned, including existing forensic suites and open-source projects.
This guide emphasizes minimizing digital traces for protesters through practical smartphone security advice. It recommends using a secondary, "burner" phone dedicated to protests, ideally a basic model without internet connectivity. If using a primary smartphone, strong passcodes/biometrics, full-disk encryption, and up-to-date software are crucial. Minimizing data collection involves disabling location services, microphone access for unnecessary apps, and using privacy-respecting alternatives to default apps like Signal for messaging and a privacy-focused browser. During protests, enabling airplane mode or using Faraday bags is advised. The guide also covers digital threat models, stressing the importance of awareness and preparedness for potential surveillance and data breaches.
Hacker News users discussed the practicality and necessity of the guide's recommendations for protesters. Some questioned the threat model, arguing that most protesters wouldn't be targeted by sophisticated adversaries. Others pointed out that basic digital hygiene practices are beneficial for everyone, regardless of protest involvement. Several commenters offered additional tips, like using a burner phone or focusing on physical security. The effectiveness of GrapheneOS was debated, with some praising its security while others questioned its usability for average users. A few comments highlighted the importance of compartmentalization and using separate devices for different activities.
iOS 18 introduces homomorphic encryption for some Siri features, allowing on-device processing of encrypted audio requests without decrypting them first. This enhances privacy by preventing Apple from accessing the raw audio data. Specifically, it uses a fully homomorphic encryption scheme to transform audio into a numerical representation amenable to encrypted computations. These computations generate an encrypted Siri response, which is then sent to Apple servers for decryption and delivery back to the user. While promising improved privacy, the post raises concerns about potential performance impacts and the specific details of the implementation, which Apple hasn't fully disclosed.
Hacker News users discussed the practical implications and limitations of homomorphic encryption in iOS 18. Several commenters expressed skepticism about Apple's actual implementation and its effectiveness, questioning whether it's fully homomorphic encryption or a more limited form. Performance overhead and restricted use cases were also highlighted as potential drawbacks. Some pointed out that the touted benefits, like encrypted search and image classification, might be achievable with existing techniques, raising doubts about the necessity of homomorphic encryption for these tasks. A few users noted the potential security benefits, particularly regarding protecting user data from cloud providers, but the overall sentiment leaned towards cautious optimism pending further details and independent analysis. Some commenters linked to additional resources explaining the complexities and current state of homomorphic encryption research.
Summary of Comments ( 36 )
https://news.ycombinator.com/item?id=44083388
Hacker News users discuss the Tachy0n jailbreak, expressing skepticism about its "last 0day" claim, noting that future iOS versions will likely patch the exploit. Some debate the practicality of the jailbreak given its limited scope to older devices and the availability of checkm8 for similar models. Others commend the technical achievement and the author's clear explanation of the exploit. Concerns about the potential for misuse of the exploit are also raised, alongside discussions about the ethics of disclosing such vulnerabilities. Several commenters point out the limitations of patching bootROM exploits, suggesting this won't be the truly "last" 0day. There's also interest in the potential for using the exploit for purposes other than jailbreaking, like device repair. Finally, a few users share personal anecdotes about jailbreaking and express nostalgia for the practice's heyday.
The Hacker News post titled "Tachy0n: The Last 0day Jailbreak" generated a significant amount of discussion, with many commenters expressing a mix of nostalgia, technical curiosity, and concern.
Several commenters reminisced about the "golden age" of jailbreaking, recalling the excitement and sense of community that surrounded it. They discussed the various tools and exploits used in the past, comparing them to Tachy0n and highlighting the evolution of jailbreaking techniques. Some expressed sadness that this might be one of the last opportunities for this kind of exploit due to increasing security measures implemented by Apple.
A recurring theme in the comments was the technical discussion of the exploit itself. Commenters inquired about the specifics of the vulnerability, how it was discovered, and the implications for future iOS security. Some debated the ethics of jailbreaking and the potential security risks associated with it. There was also discussion around the difficulty of finding and utilizing such vulnerabilities in modern iOS versions.
Some users expressed concern about the potential misuse of the exploit. They worried that the availability of such tools could lead to increased malware and security breaches. Others countered this argument, stating that jailbreaking primarily empowers users to customize their devices and bypass restrictions imposed by Apple.
A few comments focused on the practical aspects of jailbreaking. Users asked questions about compatibility with different iOS versions and devices, the process of installing the jailbreak, and the availability of tweaks and modifications. Some shared their personal experiences with jailbreaking and offered advice to newcomers.
Several commenters also discussed the cat-and-mouse game between Apple and the jailbreaking community, noting that Apple often patches vulnerabilities quickly after they are discovered. This led to discussions about the future of jailbreaking and the likelihood of similar exploits being found in the future.
Finally, there was some discussion about the name "Tachy0n" itself, with users speculating about its meaning and significance in relation to the exploit.
Overall, the comments on the Hacker News post reflect the complex and multifaceted nature of the jailbreaking community, highlighting the technical skills, ethical considerations, and nostalgic sentiment associated with this practice.