release: v0.8.6 - Stabilized macOS 15 networking and overhauled extensive technical documentation

Author: HelloPrincePal

ARCHITECTURE.md

@@ -176,7 +176,20 @@ session_id  — UUID per phone session
 event       — attach | detach | handshake_ok | ip_assigned | relay_error | etc.
 ```
 
-Set `format = "json"` in config for machine-readable logs (useful for log aggregators).
+## macOS 15+ Networking & DNS Boundary
+
+Modern macOS versions (15.0 Tahoe and later) have introduced a strict "System Trust" model for virtual interfaces. This has several architectural implications:
+
+### 1. Supplemental vs Authoritative DNS
+DroidTether implements a **Supplemental DNS** model. 
+*   **How it works**: We register our DNS servers (usually the phone's gateway) under `State:/Network/Service/droidtether/DNS`.
+*   **The Limitation**: macOS 15 only promotes a virtual interface to "Authoritative" (System-wide) if it meets specific hardware-equivalent trust criteria. Without a signed System Extension, macOS will prioritize hardware resolvers (Wi-Fi/Ethernet) for system-level tools like `Safari` or `curl`.
+*   **The Pragmatic Choice**: We choose transparency over complex interception (like AAAA hijacking) to ensure maximum stability and zero-trust security.
+
+### 2. TCP/IP Passthrough
+DroidTether performs zero modification to the IP payload. This ensures that:
+*   **VPNs work natively**: You can run an additional VPN (WireGuard, etc.) on top of DroidTether.
+*   **End-to-End Encryption**: HTTPS and TLS traffic are untouched and unverifiable by the daemon, maintaining user privacy.
 
 ---
 

CHANGELOG.md

@@ -14,6 +14,14 @@ Format:
 
 ---
 
+## v0.8.6 — 2026-04-13 (Current)
+
+### 2026-04-13 15:20 — 🛡️ The "Total Transparency" Update: Extensive Stability
+- What: Formalized stable "Supplemental DNS" model for macOS 15 compatibility; overhauled README with extensive technical verification commands and macOS 15 workaround; restored security-posture deep-dives.
+- Why: Prioritized user-auditable documentation and rock-solid IPv4 relay over experimental system-layer hijacks. Provided a clear path for CLI/Native tools via documented DNS overrides.
+- Files: `internal/tun/utun_darwin.go`, `internal/daemon/relay.go`, `README.md`, `CHANGELOG.md`, `VERSIONS.md`
+- Breaking: no ✅
+
 ## v0.8.5 — 2026-04-12
 
 ### 2026-04-12 22:25 — 💎 The "Recovery" Fix: Unified Stability

CODE_OF_CONDUCT.md

@@ -1,110 +1,39 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
-community include:
+Examples of behavior that contributes to a positive environment for our community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
+*   Demonstrating empathy and kindness toward other people
+*   Being respectful of differing opinions, viewpoints, and experiences
+*   Giving and gracefully accepting constructive feedback
+*   Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+*   Focusing on what is best not just for us as individuals, but for the overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+*   The use of sexualized language or imagery, and unwelcome sexual attention or advances
+*   Trolling, insulting or derogatory comments, and personal or political attacks
+*   Public or private harassment
+*   Publishing others' private information, such as a physical or email address, without their explicit permission
+*   Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement via direct message to:
-- **LinkedIn**: [Prince Pal](https://www.linkedin.com/in/theprincepal/)
-- **Reddit**: [@PrincePal_](https://www.reddit.com/user/PrincePal_/)
-
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-**Community Impact**: A violation through a single incident or series
-of actions.
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time.
-
-### 3. Temporary Ban
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time.
-
-### 4. Permanent Ban
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers. All complaints will be reviewed and investigated promptly and fairly.

Formula/droidtether.rb

@@ -1,7 +1,7 @@
 class DroidTether < Formula
     desc "Android USB tethering for Apple Silicon Macs — no kext, no SIP changes"
     homepage "https://github.com/princePal/droidtether"
-    version "1.0.0"
+    version "0.8.6"
 
     # ARM binary (Apple Silicon — M1/M2/M3/M4)
     on_arm do

PRIVACY.md

@@ -1,27 +1,32 @@
-# 🛡️ Privacy Policy
+# 🛡️ DroidTether Privacy Policy
 
-**DroidTether is built with privacy and security as core principles.**
+**Effective Date**: April 13, 2026
 
-This project is a userspace network daemon that handles local network traffic between an Android device and a macOS host. 
+DroidTether is built with a **Privacy-First** philosophy. As a system-level networking utility, we understand that we are in a position of high trust. This policy outlines our commitment to your data sovereignty and security.
 
-### 1. No Data Collection
-DroidTether **does not collect, transmit, or share** any of your personal data, browser history, or network traffic with any third-party servers. All data processing happens entirely on your local machine.
+## 1. Zero-Inspection Policy
+DroidTether operates as a transparent userspace bridge between your Android phone's USB interface (RNDIS) and your Mac's virtual tunnel (`utun`). 
+*   **No Deep Packet Inspection (DPI)**: We do not read, inspect, store, or modify the contents of the individual data packets flowing through the relay.
+*   **Encapsulation Only**: Our core logic is restricted to RNDIS/Ethernet encapsulation and decapsulation required for packet transport.
 
-### 2. Local Logging
-DroidTether logs its activity to a local file at `/var/log/droidtether.log` to help with debugging and troubleshooting. These logs remain only on your computer and are never uploaded or shared. 
+## 2. No Telemetry or Analytics
+*   **No "Call Home"**: The DroidTether daemon contains no code to contact any remote server for telemetry, crash reporting, or user analytics.
+*   **No Identity Tracking**: We do not collect your name, email, IP address, device serial numbers, or any other personally identifiable information (PII).
+*   **Offline by Default**: DroidTether does not require an internet connection to function (other than the connection provided by your phone).
 
-### 3. Network Traffic Transparency
-DroidTether operates as a Layer 3 (IP) relay. It does not inspect the contents of your packets (e.g., your passwords or credit card numbers) and respects any end-to-end encryption (HTTPS, TLS, VPN) that your applications already use.
+## 3. Local Operational Logs
+For debugging and performance monitoring, DroidTether writes limited operational logs to your local filesystem at:
+`/var/log/droidtether.log`
 
-### 4. Telemetry
-DroidTether has **no telemetry, no analytics, and no "call-home" features**. It will never connect to the internet unless you (the user) are using it to route your network traffic through your phone's connection.
+These logs contain:
+*   USB connection/disconnection events.
+*   DHCP lease assignments (Local IPs only).
+*   Traffic volume statistics (Total bytes sent/received).
 
----
+**These logs never leave your machine.** You are free to inspect or delete them at any time.
 
-### 📝 Audit & Transparency
-To ensure full trust, the entire core logic is implemented in less than **2,000 lines of Go code**. This makes it easy for any security researcher or user to audit the source code in a single afternoon. We believe transparency is the foundation of security.
+## 4. Compliance & Transparency
+DroidTether is 100% open-source. Anyone can audit our packet-handling logic in `internal/daemon/relay.go` to verify that we are adhering to this policy.
 
----
-
-### Questions?
-If you have any questions about this Privacy Policy or how DroidTether handles your data, please open an issue in the [GitHub repository](https://github.com/HelloPrincePal/DroidTether).
+## 5. Contact
+If you have security or privacy concerns, please open an issue on our GitHub repository or contact the author via LinkedIn.