macOS MeshAgent: Complete Rebuild and Enhancement

[PeetMcK]

macOS MeshAgent: Complete Rebuild and Enhancement

Overview

This PR represents a comprehensive rebuild and enhancement of the macOS MeshAgent, implementing native macOS features, improving security, and providing a modern installation experience. The work includes KVM improvements, installation infrastructure, TCC permission handling, force agent updates with surgical plist management, configurable naming for white-label deployments, and extensive documentation.

Summary

This PR transforms the macOS MeshAgent into a first-class macOS application with:

• 🖥️ Native macOS KVM architecture with LaunchD integration
• 🔐 Comprehensive TCC permissions system with real-time detection
• 📦 Professional Installation Assistant GUI for easy deployment
• 🏢 Multi-tenancy support via ServiceID system
• 🔄 Force agent updates with surgical plist preservation
• 🏷️ White-label support via configurable naming derived from executable
• 📚 Extensive documentation (103+ module docs, command reference, architecture guides)
• 🛡️ Enhanced security with path validation and permission management

---

Commit Structure

This PR is organized into 9 chronological commit groups following the actual development timeline:

1. macOS: Implement KVM1 reversed socket architecture with LaunchD integration

• Complete rewrite of macOS KVM (remote desktop) architecture
• Reversed socket model: Agent creates socket, KVM connects through LaunchD
• Eliminates security issues with traditional approach
• Proper privilege separation and sandboxing support
• Architecture: docs/macos-KVM-Architecture.md

2. macOS: Add ServiceID system for multiple installations

• Reverse DNS-style service identification: meshagent[.serviceName][.companyName]
• Enables multiple independent MeshAgent installations on same system
• Support for multi-tenancy and service variants
• Proper LaunchDaemon/LaunchAgent namespace separation
• Documentation: docs/macOS-ServiceID-System.md

3. macOS: Unify -install and -upgrade commands with build infrastructure

• Unified installation and upgrade logic for macOS
• Professional logging infrastructure with timestamps
• macOS application bundle support with proper Info.plist embedding
• Build system improvements for universal binaries
• Recursive directory creation for installation paths
• Code-signing and notarization workflow integration

4. macOS: Add logger module and TCC permissions UI

• New logger.js module with DEBUG/INFO/WARN/ERROR levels
• Real-time TCC permission detection (Accessibility, Screen Recording, Full Disk Access)
• Interactive permissions UI with visual status indicators
• Pipe-based IPC for elevated permission checking
• Preference-aware TCC checking (--disableTccCheck support)
• Documentation: docs/macos-tcc-permissions.md

5. macOS: Add Installation Assistant UI and infrastructure improvements

• Native Cocoa Installation Assistant with install/upgrade detection
• Automatic .msh file discovery in app bundle and Downloads
• Configuration viewer with value truncation
• Admin credential prompting via Authorization Services
• Installation path validation with security checks
• Progress tracking and operation result display
• Documentation: docs/macos-install-assistant.md

6. macOS: Final polish and stability improvements

• Bug fixes:
  • Fixed normalizeInstallPath() incorrectly stripping 'meshagent' from paths
  • Fixed prepareFolders() to use recursive directory creation
  • Fixed validate_installation_path() to handle non-existent parent directories
• Complete command reference documentation
• 103+ comprehensive module documentation files
• Updated README with full documentation index
• macOS helper functions module (macOSHelpers.js)
• Security permissions management module (security-permissions.js)

7. macOS: Polish install/upgrade, app bundle, and build system

Install/Upgrade Improvements:

• Comprehensive argument validation system (whitelist-based security)
• Fixed -fullinstall path construction and LaunchAgent handling
• Enhanced service lookup for custom ServiceIDs during self-update
• Install validation prevents blank .db creation
• Installer logging with verbosity control
• Launchctl job cleanup prevents upgrade conflicts
• Replaced implicit self-upgrade detection with explicit LaunchDaemon plist scan
• Refactored plist updates with cached customizations (surgical updates)

Force Agent Updates:

• Server-triggered updates via MeshCentral -upgrade command
• Surgical plist updates preserve user customizations during force updates
• Atomic plist creation for fresh installations
• Version tracking via meshagent_ver key in LaunchDaemon/LaunchAgent plists
• Success/failure tracking via UpdateInProgress flag

App Bundle Enhancements:

• Set app bundle capability bit (0x80) for proper .app bundle detection
• Fixed critical bugs in bundle handling and upgrade process
• Complete zip creation, signing, and notarization workflow
• Runtime universal binary detection

Build System:

• MODULESYNC_MODE build variable with macos-only default
• Embedded version info exposed to JavaScript (DRY compliant)
• -buildver and -fullversion flags for version reporting
• Enhanced build output with version verification and improved formatting
• Add meshagent_ver to LaunchDaemon/LaunchAgent plists

Bug Fixes:

• AC power detection fix in pmset parsing
• LaunchAgent log file permissions (666 for user access)
• Improved Install UI version detection using meshagent binary

8. macOS: Configurable naming, ServiceID overhaul, UI enhancements, and DRY refactoring

Configurable Naming (White-Label Support):

• Replace all hardcoded "meshagent" references with dynamic names derived from executable
• Enables white-label deployments (e.g., AcmeMesh, CustomAgent)
• ServiceID and config filenames (.msh/.db) derived from executable name
• Read ServiceID from .msh configuration files
• Add --setServiceID flag to override during install/upgrade
• Resolve serviceID from LaunchDaemon plist Label as fallback
• Reuse existing plist filenames during upgrade to prevent duplicates
• Parameterize plist parser with configurable agent name

Deployment Assistant UI Overhaul:

• Add uninstall mode (standard + full uninstall) with confirmation dialogs
• Replace SF Symbols with custom-drawn Lucide/Bootstrap vector icons (no macOS 11+ dependency for icons)
• Settings card with 2×2 checkbox grid (updates, TCC, verbose logging, agent logging)
• Dynamic button text and icon tinting based on selected mode
• Pre-populate .msh and install path fields regardless of initial mode
• .msh file viewer as modal sheet with sorted key-value table

TCC Permissions UI:

• Replace SF Symbols checkmarks with custom Lucide circle-check-fill icons
• Use shared mesh_createFloatingWindow() for window creation
• Shared helpers for buttons and checkboxes

DRY Refactoring — Shared UI Helpers (mac_ui_helpers.h/m):

• mesh_createVectorIcon() — generic vector icon with configurable viewBox size
• mesh_createLucideIcon() — Lucide icon wrapper (24×24 viewBox)
• mesh_bootstrapShieldCheckIcon() / mesh_lucideShieldCheckIcon() — shield icons
• mesh_lucideCircleCheckFillIcon() — filled circle-check for success indicators
• mesh_lucideNetworkIcon(), mesh_lucideImportIcon(), mesh_lucideUploadIcon(), mesh_lucideTrashIcon()
• mesh_addRadioIcon() — attach icon to radio button
• mesh_createCheckbox(), mesh_createRoundedButton(), mesh_createPathField()

Build System:

• Parameterize with EXENAME and BUNDLE_DISPLAY_NAME make variables
• Rename icon asset to generic AppIcon.icns
• Update all build/sign/notarize scripts for configurable names

Other:

• Fix argument validation to skip JS code after -exec/-b64exec
• Remove companyName/meshServiceName from KVM path resolution
• Remove TCC-DEBUG logging and orphaned format arguments
• Update documentation for ServiceID system and commands

9. macOS: Consolidate build scripts, remove dead code, document makefile

Build Script Consolidation:

• Replace 5 sign/notarize scripts with 2 unified multi-target scripts
  (macos-sign.sh and macos-notarize.sh) that auto-detect .app bundles
  vs bare binaries
• Parallel notarization support for multiple targets (submit all, wait all)
• Delete sign-app-bundle.sh, notarize-app-bundle.sh, notarize-app-bundles.sh
• Update makefile to call consolidated scripts

Dead Code Removal:

• Delete macos-build_sign_notarize.sh (makefile is the build interface)
• Delete MeshAgent_pkg directory and --build-pkg option
• Remove unused -request-fulldiskaccess CLI flag and standalone FDA dialog
• Replace populate-FULL-polyfills.sh with minimal example in code-utils/

Build Toolchain Cleanup:

• Move generate-build-timestamp.sh and generate-info-plist.sh into macos_build/
• Unify visual output style (colors, formatting) across all macOS build scripts
• Rewrite macos_build/README.md around makefile-driven workflows

Documentation:

• Document macOS-specific build switches (SIGN, NOTARIZE, EXENAME,
  BUNDLE_DISPLAY_NAME, BUNDLE_ID, BUNDLE_ICON, SKIPSIGNNOTARY)
  in makefile header with usage examples
• Add ARCHID=10005 (universal) to standard builds list

Net result: 22 files changed, +643 / −2,926 lines

---

Key Features

🖥️ Remote Desktop (KVM)

• Reversed Socket Architecture: Agent creates Unix domain socket, KVM connects via LaunchD
• LaunchD Integration: Proper service lifecycle management
• Security: Eliminates need for KVM to bind sockets as root
• TCC Compliance: Integrates with macOS permission system

🔐 Security & Permissions

• TCC Permissions UI: Real-time detection and visual indicators for required permissions
• Path Validation: Installation paths validated against allowed locations
• Permission Management: Automated file permission setting with security policies
• Code Signing: Integrated workflow for signing and notarization
• Argument Validation: Whitelist-based security for macOS arguments

📦 Installation Experience

• GUI Installation Assistant: Native Cocoa interface for install/upgrade/uninstall
• Auto-Discovery: Automatic .msh file detection
• White-Label: Configurable naming from executable name
• Progress Tracking: Real-time feedback during operations

🏷️ White-Label Support

• Executable-Derived Naming: All UI labels, file paths, and plist identifiers derived from binary name
• --setServiceID Override: Explicit control over service naming during install/upgrade
• Build Parameterization: EXENAME, BUNDLE_DISPLAY_NAME, BUNDLE_ID, and BUNDLE_ICON make variables
• Default Fallbacks: "meshagent" used as default when executable name cannot be determined

🔄 Agent Updates & Plist Management

• Force Updates: Server-triggered agent updates via MeshCentral
• Surgical Plist Updates: Preserve user customizations during updates
• Atomic vs Surgical: Intelligent update strategy based on plist state

🏗️ Build Infrastructure

• Universal Binaries: ARM64 + x86_64 support
• App Bundle Creation: Proper .app bundle structure with Info.plist
• Module Embedding: JavaScript modules embedded at build time
• Configurable Names: EXENAME / BUNDLE_DISPLAY_NAME / BUNDLE_ID / BUNDLE_ICON build variables
• Consolidated Scripts: 2 unified sign/notarize scripts replace 5, with auto-detection and parallel support
• Self-Documenting: All macOS build switches documented in makefile header
• Version Management: Embedded version info with DRY compliance

📚 Documentation

• Command Reference: Complete CLI documentation (docs/meshagent-commands.md)
• Module Documentation: 103+ modules comprehensively documented (docs/meshagent-modules/)
• Architecture Guides:
  • macOS KVM Architecture
  • macOS TCC Permissions
  • Installation Assistant
  • ServiceID System
• Build Tools: build/tools/macos_build/README.md
• README: Updated with comprehensive documentation index (docs/README.md)

---

New Modules

modules/logger.js

Professional logging infrastructure with:

• Log levels: DEBUG, INFO, WARN, ERROR
• Timestamp formatting
• Runtime log level configuration
• Zero dependencies, cross-platform

modules/macOSHelpers.js

macOS platform helper functions:

• Bundle detection and path resolution
• ServiceID generation with reverse DNS conventions
• LaunchDaemon/LaunchAgent management
• Plist manipulation utilities

modules/security-permissions.js

Security permissions management:

• File permission policies for 9 critical file types
• Permission verification and enforcement
• Secure file creation with race condition prevention
• Installation integrity validation

modules/agent-paths.js

Agent path resolution:

• Dynamic path computation from executable name
• Cross-platform path normalization

---

Testing

Tested On

• ✅ macOS 15.x (Sequoia) - ARM64
• ✅ macOS 12.x (Monterey) - x86_64
• ✅ Universal binary functionality verified

Test Coverage

• ✅ Fresh installation with GUI
• ✅ Fresh installation via command-line
• ✅ Upgrade from existing installation
• ✅ Uninstall and full uninstall via GUI
• ✅ Multiple installations with different ServiceIDs
• ✅ White-label deployment with custom executable name
• ✅ TCC permission detection and UI
• ✅ KVM functionality with LaunchD
• ✅ Installation path validation
• ✅ Recursive directory creation
• ✅ Bundle detection and operations
• ✅ Code signing and notarization workflow
• ✅ Force update from MeshCentral server
• ✅ Surgical plist update preserves customizations
• ✅ Atomic update for fresh installations
• ✅ Version tracking and verification
• ✅ Argument validation and security
• ✅ Self-upgrade detection via LaunchDaemon plist scan
• ✅ Consolidated build scripts (multi-target sign/notarize)

Security Testing

• ✅ Path validation (injection prevention)
• ✅ Permission verification
• ✅ Race condition prevention in file creation
• ✅ Privilege escalation handling
• ✅ TCC compliance verification
• ✅ Argument validation against malicious inputs

---

Migration Guide

For Users Upgrading from Previous Versions

Installation:

1. Download new MeshAgent.app and .msh file (if new install)
2. Hold CMD key and double-click MeshAgent.app
3. Follow Installation Assistant (auto-detects upgrade)

Or via command-line:

sudo ./meshagent -install --installPath="/existing/path/"

ServiceID Migration:

• Existing installations maintain compatibility
• New installations use reverse DNS format
• Multiple installations now supported via ServiceID

Force Updates:

• Existing installations will receive surgical updates (customizations preserved)
• Fresh installations use atomic plist creation
• Version tracking helps detect update success/failure

For Developers

Build Requirements:

• Xcode Command Line Tools
• Code signing certificate (optional, for distribution)

Building:

make macos ARCHID=10005                                        # Universal binary (default naming)
make macos ARCHID=29                                           # ARM only
make macos ARCHID=10005 SIGN=1 NOTARIZE=1                     # Signed + notarized
make macos ARCHID=10005 EXENAME=acmemesh                      # White-label binary name
make macos ARCHID=10005 BUNDLE_DISPLAY_NAME="AcmeMesh"        # White-label display name
make macos ARCHID=10005 BUNDLE_ID=com.acme.mesh                # Custom bundle identifier
make macos ARCHID=10005 BUNDLE_ICON=/path/to/icon.icns         # Custom icon
make macos ARCHID=10005 SIGN=1 SKIPSIGNNOTARY=bundle           # Sign binary only

Documentation:

• See docs/README.md for complete documentation index
• Module APIs: docs/meshagent-modules/
• Command reference: docs/meshagent-commands.md
• Build tools: build/tools/macos_build/README.md

---

Compatibility

Maintains Compatibility With:

• ✅ MeshCentral server communication protocol
• ✅ Existing .msh configuration files
• ✅ Existing LaunchDaemon configurations
• ✅ Cross-platform module APIs

Platform Support:

• macOS: Full support (primary focus of this PR)
• Windows: Unaffected
• Linux: Unaffected
• BSD: Unaffected

---

Related Issues

This PR addresses multiple long-standing issues and feature requests for macOS:

• macOS KVM architecture improvements
• Installation experience enhancement
• TCC permission handling
• Multi-tenancy support
• White-label deployment support
• Force agent updates with customization preservation
• Documentation completeness

Related MeshCentral PR:

• MeshCentral #7486 - Required for new -upgrade system

---

Checklist

• Self-review completed
• Documentation updated
• Manual testing completed
• Backward compatibility verified
• Security considerations addressed
• Commit history is clean and organized
• PR description is comprehensive

---

Issues & Bug Reports

If you encounter any problems with this PR, please open an issue on my fork:

• Repository: https://github.com/PeetMcK/MeshAgent
• Branch: _100-PR-macOS-MeshAgent-Rebuild
• Issues: https://github.com/PeetMcK/MeshAgent/issues

[llambkin]

@PeetMcK

Congratulations and thankyou for your hard work on this functionality. Its been great to watch and test this as the process moves along. I can't wait for this to get pushed through to main line, and I can start deploying the agent to all our Mac clients.

[si458]

you accidently pushed ur tactial agent into the repo, please can u remove it

[PeetMcK]

you accidently pushed ur tactial agent into the repo, please can u remove it

https://github.com/Ylianst/MeshAgent/compare/3b3b2408ea618fe37a4e5772991197df3f35fc76..cbc52b8e4e93d7b6569e0d51aaf26dcea6dab4f4

Cheers.Peet

[PeetMcK]

#313
and
Ylianst/MeshCentral#7486

Both updated and I'm calling it good. If anyone runs into issues testin feel free to open an issue:

https://github.com/PeetMcK/MeshAgent/issues/
and
https://github.com/PeetMcK/MeshCentral/issues/

[kirill-567]

Hi @PeetMcK,
Thank you for your job!
I have the issue with Screen Sharing permissions when I install service using app bundle.

Write me please to kirill@flamingo.cx
We're open for the sponsorship.

cc @si458

[PeetMcK]

@kirill-567 I'd need more information here.

Basic troublshooting information:

• Please clearly describe the issue with Screen Sharing permissions.
• Please describe the environment your testing.
• Is it a fresh macOS install?
• What version of macOS?
• If not fresh, have you reset your screen recording tcc?
• What troubeshooting steps have you performed?

Signing information:

What is the output of
codesign -dr - /path/to/MeshAgent.app

% codesign -dr - ./build/output/osx-universal-64-app/MeshAgent.app
Executable=/Users/peet/GitHub/MeshAgent/build/output/osx-universal-64-app/MeshAgent.app/Contents/MacOS/meshagent
# designated => cdhash H"593be24dfcd02ef8eb73e1632d223f4bfb4814f1" or cdhash H"ae4d87bdd8441dadb6e3811a3df302166d6f2531"

codesign -dv /path/to/MeshAgent.app

% codesign -dv ./build/output/osx-universal-64-app/MeshAgent.app
Executable=/Users/peet/GitHub/MeshAgent/build/output/osx-universal-64-app/MeshAgent.app/Contents/MacOS/meshagent
Identifier=meshagent
Format=app bundle with Mach-O universal (x86_64 arm64)
CodeDirectory v=20400 size=8994 flags=0x2(adhoc) hashes=275+3 location=embedded
Signature=adhoc
Info.plist entries=14
TeamIdentifier=not set
Sealed Resources version=2 rules=13 files=1
Internal requirements count=0 size=12

[kirill-567]

@PeetMcK

Issue description (Screen Sharing / Screen Recording permissions):
We are experiencing a black screen on the remote desktop when connecting via MeshCentral. The issue is directly related to macOS Screen Recording permissions and how they are handled across installations, reinstalls, and system restarts.

Testing environment:

• Device: macOS system
• macOS version: macOS Sequoia 15.6
• MeshAgent executable: unsigned
• Tested both with and without manually removing all permissions before testing

Is this a fresh macOS install?

• No, this is not a fresh macOS installation.
  macOS version: macOS Sequoia Version 15.6

Have you reset Screen Recording (TCC) permissions?
Yes. We tested both scenarios:

• With existing Screen Recording permissions removed manually before installation
• Without removing existing permissions

Troubleshooting steps performed:

1. Installation using -install flag

• If no Screen Recording permission existed from a previous installation, the first remote desktop session works correctly.
• If Screen Recording permission already existed from a previous installation, the remote desktop shows a black screen.

2. Default mode (launching MeshAgent without arguments)

• Even after manually removing the previous Screen Recording permission and granting it again directly to the executable, the remote desktop still shows a black screen.

3. Launching from .app bundle

• We were unable to fully test remote desktop functionality.
• After self-update, the executable loses the ability to read the .msh file located next to it, which prevents proper connection to MeshCentral.

4. Most successful scenario (-install flag)

• When installed with -install and no prior Screen Recording permission exists, macOS prompts for permission on first remote connection.
• After granting permission, remote desktop works as expected.
• After a system reboot, the remote desktop again results in a black screen.

Signing:

• We suspect behavior may differ when using a properly signed executable, but this has not yet been tested.

[PeetMcK]

Issues with a black screen are not relateded to Screen Recording TCC. Black screen issues with meshagent/MeshAgent.app are cased by the -kvm1/LaunchAgent on the device. Screen Recording TCC issues virtually always present as seeing a desktop with a menubar, but no windows (this is for any macOS screen recording software).

While it might not be neccessary given the extended information, it may still prove useful to provide the requested signing information

What is the output of
codesign -dr - /path/to/MeshAgent.app
codesign -dv /path/to/MeshAgent.app

For troubleshooting the black screen lets start from a known state. First make sure to build from the most current commit ... 70ddb69 ... then do the following:

• Place your MeshAgent.app somehwere like ~/Downloads
• sudo ~/Downloads/MeshAgent.app/Conents/MacOS/meshagent -fulluninstall --installPath={YOUR_installPath} --log=3
• {YOUR_installPath} should not exist
• /Library/LaunchAgents/meshagent-agent.plist should not exist
• /Library/LaunchDaemons/meshagent.plist should not exist
• launchctl list | grep meshagent should not have output
• sudo launchctl list | grep meshagent should not have output
• pgrep meshagent should not have output

Now lets reinstall:

• Place your MeshAgent.app somehwere like ~/Downloads
• ensure you have a valide meshagent.msh in the same directory
• The next steps assume default installation directory /usr/local/mesh_services/meshagent/
• sudo ~/Downloads/MeshAgent.app/Conents/MacOS/meshagent -fullinstall --copy-msh=1 --meshAgentLogging=1 --log=3
• TCC check UI - "MeshAgent - Security & Privacy Settings" - should run here if TCC permissions are not satisfied.
• /Library/LaunchDaemons/meshagent.plist should exist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Disabled</key>
	<false/>
	<key>KeepAlive</key>
	<true/>
	<key>Label</key>
	<string>meshagent</string>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/mesh_services/meshagent/MeshAgent.app/Contents/MacOS/meshagent</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
	<key>StandardErrorPath</key>
	<string>/tmp/meshagent-daemon.log</string>
	<key>StandardOutPath</key>
	<string>/tmp/meshagent-daemon.log</string>
	<key>WorkingDirectory</key>
	<string>/usr/local/mesh_services/meshagent</string>
	<key>meshagent_ver</key>
	<string>25.12.22</string>
</dict>
</plist>

• /Library/LaunchAgents/meshagent-agent.plist should exist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Disabled</key>
	<false/>
	<key>KeepAlive</key>
	<false/>
	<key>Label</key>
	<string>meshagent-agent</string>
	<key>LimitLoadToSessionType</key>
	<array>
		<string>Aqua</string>
		<string>LoginWindow</string>
	</array>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/mesh_services/meshagent/MeshAgent.app/Contents/MacOS/meshagent</string>
		<string>-kvm1</string>
		<string>--serviceId=meshagent</string>
	</array>
	<key>QueueDirectories</key>
	<array>
		<string>/var/run/meshagent</string>
	</array>
	<key>StandardErrorPath</key>
	<string>/tmp/meshagent-agent.log</string>
	<key>StandardOutPath</key>
	<string>/tmp/meshagent-agent.log</string>
	<key>Umask</key>
	<integer>0</integer>
	<key>WorkingDirectory</key>
	<string>/usr/local/mesh_services/meshagent/</string>
	<key>meshagent_ver</key>
	<string>25.12.22</string>
</dict>
</plist>

• sudo launchctl list | grep meshagent -> [PID] 0 meshagent
• launchctl list | grep meshagent -> - 0 meshagent-agent
• pgrep meshagent -> [SAME_PID_AS_ABOVE] (if you have more than one PID, is TCC check UI still running?)

At this point you should be set.

If you're still getting a black screen, refer to your /tmp/meshagent* logs and to ./docs/macos-KVM-Architecture.md to continue troubleshooting the process.

[silversword411]

This would only be for a tactical mesh agent, not native mesh

[silversword411]

This would only be for a tactical mesh agent, not native mesh

[silversword411]

This would only be for a tactical mesh agent, not native mesh

[silversword411]

This would only be for a tactical mesh agent, not native mesh

[silversword411]

Referencing Tacticalmesh

[silversword411]

Tactical references

[silversword411]

Tactical examples

[silversword411]

Tactical examples

[silversword411]

Tactical examples

[silversword411]

Not for native mesh, only Tactical

[silversword411]

Not for native mesh, only Tactical

[silversword411]

Referencing Tactical RMM

[silversword411]

This whole file is filled with Tactical References. I think this is just as an optional service documentation reference, but should review

[silversword411]

Tactical DB references.

[silversword411]

Tactical DB references.

[silversword411]

Tactical DB references.

[silversword411]

I've only gotten to the MESHCORE_OVERVIEW.MD so far...and this is high level atm just keyword searching for tact after getting the first jist of changes.

I know you're a tactical user, but this PR has to be mesh specific, and then TRMM will need to customize the extra fixes specific to Tactical in their deployment.

[PeetMcK]

I've only gotten to the MESHCORE_OVERVIEW.MD so far...and this is high level atm just keyword searching for tact after getting the first jist of changes.

I know you're a tactical user, but this PR has to be mesh specific, and then TRMM will need to customize the extra fixes specific to Tactical in their deployment.

Thanks for pointing out the non-generic references. I've removed them. If you see anyothers, please feel fee to correct them if the PR is ever merged.

Cheers.Peet