mac2jb v0.3.1

mac2jb v0.3.1 bundles the tested unsigned USB gadget driver and streamlines its setup in both the GUI and CLI.

• GUI: use Install & load driver… to verify, install, and request loading of the bundled driver through a macOS administrator prompt.
• CLI: choose option 4, or run bash mac2jb.command --install-driver from the complete source checkout.
• Existing drivers are preserved in uniquely named backups. Installation activity and errors are logged, and sessions are blocked until the required restart has occurred and the driver is reported loaded.
• The complete source archive now includes drivers/usbgadget.kext, SHA-256 checksums, provenance, licenses, and the source-build fallback.
• SIP/Recovery instructions are clearer. SIP must be disabled for this unsigned-driver setup; mac2jb never changes SIP or startup security automatically. Complete any macOS approval/restart prompts before starting a session.

The bundled driver is the maintainer's local version 1.01 arm64e build with its personal development signature removed. The unsigned copy passed reboot/loading, USB enumeration, and typing tests, followed by maintainer testing of the GUI and CLI workflows. Other hardware and OS combinations remain unverified. The app remains ad-hoc signed and not notarized.

Thanks to SocraticBliss for feedback and guidance on simpler driver installation and clearer SIP requirements. The driver and USB gadget work are by Max Thomas / shinyquagsire23; upstream credits and licenses are retained. ns2jb attribution and notices remain included.

Download mac2jb-v0.3.1-macos-arm64.zip for the app, or mac2jb-v0.3.1-source.zip for the complete source with GUI and CLI support. Both include the unsigned driver. Follow the README's recommended bundled-driver setup; build instructions remain available as a fallback.

mac2jb v0.3.0

mac2jb v0.3.0 adds a native macOS GUI for the bootstrap and saved-NS2 workflows.

• Bundled runtime and sender tools, with USB controller selection and configurable key pacing, enumeration timeout, and command waits.
• Bootstrap progress, elapsed time, estimated completion, and an explicit Direct mode / SAVE "NS2" checkpoint.
• Separate host and USB activity views and private log files, with failure messages showing the log location.
• Workflow indicators that reflect cancellation, failure, and retry state.
• Classic smile application icon. The existing command-line workflow remains available.

Download and extract mac2jb-v0.3.0-macos-arm64.zip, then open mac2jb.app. A compatible USB gadget kernel extension must already be installed, approved, and loaded, with the required Reduced Security settings. See docs/GUI-DEMO.md in the source archive for setup details. The application is ad-hoc signed and not notarized.

The source archive includes corresponding source, licenses, and third-party notices. Private logs and extracted session data are excluded. SHA-256 checksums are supplied for both archives.

mac2jb v0.2.1

mac2jb v0.2.1 — maintenance and source packaging update

This release carries the v0.2.0 USB HID sender and ns2jb integration
with targeted maintenance and distribution hardening:

• Included Apple Public Source License 2.0 texts and dated downstream libusbd
  modification notices (already in the repository before these changes).
• Hardened local session directory, pairing file, and GUI host-log permissions.
• Removed bundled precompiled kernel extension and unused upstream USB-device
  proof-of-concept files. Build the kext from the bundled Xcode source project.
• Updated the offline setup and bootstrap-verification helper scripts.
• Added source ZIP checks that reject session captures, machine-local files,
  compiled kernel components, and missing license texts.
• Clarified third-party licensing and provenance of intentionally trimmed
  vendored sources.

Important: This project is experimental and hardware-specific. A successful
USB transfer is not evidence that the console has successfully completed the
ns2jb exploit. Installing a custom kernel extension carries real Mac security
and stability risks. Consult the README before proceeding.