Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    C

    Corellium Blog

    corellium.com · Company blog · on HN since 2019

    Corellium, a company that virtualizes ARM devices such as iOS, writes about security research, Linux on Apple M1, and its legal disputes.

    Visit blogHN submissions
    SecurityMobile & Apple
    What HN says

    HN commenters bring it up as an iOS emulation tool for security research that Apple sued over and which survived.

    Stats for nerds
    24HN people shared it
    8linked in comments
    410story points
    Nov 2024last shared
    2019people per year2024

    Top posts on HN

    1. 1
      How We Ported Linux to the M1
      6 people · 362 points · first shared 2021 · 74 comments on HN
    2. 2
      Hardware security mechanisms protecting physical memory on mobile devices
      1 person · 22 points · first shared 2020 · 1 comments on HN
    3. 3
      Cellebrite to Acquire Corellium
      2 people · 18 points · first shared 2025 · 1 comments on HN
    4. 4
      Corellium will pay for security researchers to check Apple CSAM claims
      2 people · 4 points · first shared 2021 · Discussion on HN
    5. 5
      Exploiting iOS Local Storage with Corellium
      1 person · 2 points · first shared 2022 · Discussion on HN
    6. 6
      Would it be legally safe to work with correlium?
      11 people · 1 points · first shared 2019 · 2 comments on HN
    7. 7
      Corellium Ported Linux to the Apple M1
      1 person · 1 points · first shared 2021 · Discussion on HN
    8. 8
      Ios mobile reverse engineering
      1 person · first shared 2024
    9. 9
      About
      1 person · first shared 2024

    What HN people wrote when they linked it

    • walterbellMay 2024

      > when you cannot trust the OS

      The list above is not about distrusting the vendor or OS, it's about leveraging the vendor's officially published statements of behavior (e.g. HTTPS network traffic identified by PKI certificates tied to vendor's legal identity), used in contracts with enterprise customers that have competent lawyers, for the benefit of smaller customers.

      MDM policy can be configured to narrow the vendor's documented claims of software+hardware behavior. Narrowed claims are cheaper to verify empirically. If evidence can be found that MDM policy is not being enforced, then the pool of affected parties grows from powerless individuals to a class action (Apple has paid millions in the past) and/or large enterprises who use MDM to protect confidential enterprise data.

      > How do you ensure that the OS does not by itself connect to a random open WLAN

      In the case of Wi-Fi, MDM and Apple Configurator can configure device policy to connect only to approved SSIDs + a null list of approved SSIDs. To validate enforcement of this WiFi policy, the device can be placed in a small faraday box (commercial < $1000, DIY < $100) that blocks external RF, with an SDR that records all internal RF traffic for analysis. For a device with a null list of approved SSIDs, there should be zero Wi-Fi traffic from the baseband radio.

      Another option for MDM policy enforcement validation is to use a virtual iOS/macOS instance, where a hypervisor can perform live behavioral analysis of OS…

    • amosbattoJan 2022

      > Looking up the Librem 5 devicetree in the upstream kernel, it seems it was submitted on Aug 21 2020. Aspen shipped in September 2019, so it took them about a year from shipping to upstreaming bring-up, and that's not considering internal prototypes and that the SoC was announced in mid 2018, so they had plenty of time to work on things internally. I submitted upstream bring-up for the M1 Mac Mini with the device tree on Feb 4 2021, just 4 months after it was announced in Nov 2020.

      Before anything else, let me say thank you for your work on the M1, because it is essential that we have Linux support for processors even when the device maker is opposed. Considering how many millions of people have bought Apple's M1 devices, Asahi's work is critical because it provides a path for people to discover a freer system when they get disgusted with Apple's bad practices and the restrictions of its "walled garden."

      Having said that, I don't think that your criticism of Purism's kernel work is very fair. Purism made its first commit to mainline Linux for the Librem 5 in July 2018 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae6fe7a387e97e2ea8cc275fff5ef55568c4daf3). Purism submitted the device tree for the Librem 5 DevKit to mainline Linux on June 17, 2019 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb4ea0857c83d006b9c514929f1af547bc3319c6), which was 7 months after it started shipping the DevKits in mid-December…

    • pmarreckMar 2021

      > The M1 felt like yet another step towards making the Mac more closed

      There's a certain amount of hubris in this, in that (at least until AMD came along), pretty much every single Intel chip has only made Intel money, while ARM is broadly-licensed and is ripe for a surge. All Apple did was create an ARM-compatible chip, which is how someone already got Linux running on it: https://corellium.com/blog/linux-m1

      Here's ARM themselves on their licensing model: https://www.arm.com/why-arm/how-licensing-works

      Now, which one is more "closed", really? Near-absolute Intel hegemony that only benefits Intel, or ARM, which seems to benefit anyone who wants to tackle creating an ARM chip?

      Honestly (disclosing my bias here), I hope IA64 dies in a fire in 5-10 years. It's had enough time in the limelight, Intel has rested on its laurels of late (arguably holding back progress), and its technical flaws run quite deep (another reason why the M1 seems impressive; ARM is simply a better-designed architecture from the ground up)

    • commonerAug 2021

      This doesn't look like "fake news" to me.

      Timeline:

      Monday, August 16: Corellium launches its "Open Security Initiative" to fund "research projects designed to validate any security and privacy claims for any mobile software vendor". The announcement prominently lists Apple's privacy and security claims about its CSAM scanning as one of the topics that would be eligible for funding under this initiative. (https://www.corellium.com/blog/open-security-initiative)

      Tuesday, August 17: Apple appeals the copyright case that it lost against Corellium. Reuters reports that the appeal was a "surprise" after the recent settlement. (https://www.reuters.com/legal/transactional/apple-files-appeal-notice-copyright-lawsuit-against-cybersecurity-firm-2021-08-17/)

    • sergeykishJan 2021

      Interfacets, it is mentioned in the article

      > Apple designed their own interrupt controller, the Apple Interrupt Controller (AIC), not compatible with either of the major ARM GIC standards. And not only that: the timer interrupts - normally connected to a regular per-CPU interrupt on ARM - are instead routed to the FIQ, an abstruse architectural feature, seen more frequently in the old 32-bit ARM days. Naturally, Linux kernel did not support delivering any interrupts via the FIQ path, so we had to add that.

      and many others

      https://corellium.com/blog/linux-m1

      It is on top of HN now https://news.ycombinator.com/item?id=25859907

    • smoldesuMay 2023

      > it was never hacked and made to run on other ARM platforms.

      Barring Corellium[0], of course.

      My first instinct is that any company with the resources to make such a thing could tell it wouldn't last long. Petty copyright violations go over pretty smoothly in China all the time, but any attempts to go international would get them sued out of the market. It would also stand to sabotage Apple's investments in Chinese success, which is a no-go for any domestic business. It wouldn't surprise me if the PRC shut down some iOS hacker hopefuls to maintain their contract and keep things civil.

      [0] https://www.corellium.com/

    Related

    Siguzasiguza.github.io21 people

    IOHIDeous OS X Local Kernel Vulnerability

    Siguza
    Personal · last shared 2023
    Saar Amarsaaramar.github.io18 people

    Introduction to Firebloom (iBoot)

    Saar Amar
    Personal · last shared 2026
    Corelancorelan.be23 people

    Interesting analysis of a malicious PDF.

    Corelan
    Publication · last shared 2021
    CoreOS Blogcoreos.com316 people

    CoreOS is building a container runtime, Rocket

    CoreOS Blog
    Company · last shared 2020
    Mender Blogmender.io17 people

    United Kingdom to introduce security labelling on connected devices

    Mender Blog
    Company · last shared 2022
    Collabora Blogcollabora.com129 people

    Matt Godbolt sold me on Rust by showing me C++

    Collabora Blog
    Company · last shared 2026
    The Morning Paperblog.acolyer.org606 people

    Local-first software: you own your data, in spite of the cloud

    The Morning Paper
    Personal · last shared 2026
    Graham Christensengrahamc.com57 people

    Erase your darlings: immutable infrastructure for mutable systems

    Graham Christensen
    Personal · last shared 2026