Remove native messaging

[koppor]

User description

Follow-up to #14855

With the re-written browser extension (https://github.com/JabRef/JabRef-Browser-Extension), no native messaging is requried any more.

Steps to test

1. Install JabRef
2. Install Browser extension from source.
3. Try if browser connection can connect to JabRef

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Enhancement

---

Description

• Remove native messaging host scripts and configuration files

• Eliminate browser extension integration from installation packages

• Simplify build configuration by removing native messaging resources

• Update installation scripts to remove native messaging setup

---

Diagram Walkthrough

flowchart LR
  A["Native Messaging<br/>Host Scripts"] -->|removed| B["Linux/macOS/<br/>Windows Hosts"]
  C["Browser Extension<br/>Config Files"] -->|removed| D["Firefox/Chrome/<br/>Chromium Configs"]
  E["Installation<br/>Scripts"] -->|updated| F["Debian/RPM/<br/>macOS/Snap"]
  G["Build<br/>Configuration"] -->|simplified| H["Gradle Build<br/>Resources"]

Loading

File Walkthrough

	Relevant files
Enhancement	20 files jabrefHost.py Remove Linux native messaging host script                                +0/-131  jabrefHost.py Remove macOS native messaging host script                                +0/-101  JabRefHost.ps1 Remove Windows PowerShell native messaging script                +0/-54    JabRefHost.bat Remove Windows batch native messaging launcher                      +0/-20    bifehkofibaamoeaopjglfkddgkijdlh.json Remove Chromium browser extension auto-install config        +0/-3      org.jabref.jabref.json Remove Chromium native messaging host configuration            +0/-10    org.jabref.jabref.json Remove Firefox native messaging host configuration              +0/-10    bifehkofibaamoeaopjglfkddgkijdlh.json Remove macOS Chromium browser extension config                      +0/-3      org.jabref.jabref.json Remove macOS Chromium native messaging config                        +0/-10    org.jabref.jabref.json Remove macOS Firefox native messaging config                          +0/-7      jabref-chrome.json Remove Windows Chrome native messaging config                        +0/-10    jabref-firefox.json Remove Windows Firefox native messaging config                      +0/-10    connect-plug-etc-chromium-native-messaging-jabref Remove Snap Chromium native messaging hook                              +0/-9      connect-plug-etc-opt-chrome-native-messaging-jabref Remove Snap Chrome native messaging hook                                  +0/-9      connect-plug-etc-opt-edge-native-messaging-jabref Remove Snap Edge native messaging hook                                      +0/-9      connect-plug-hostfs-mozilla-native-messaging-jabref Remove Snap Firefox native messaging hook                                +0/-9      disconnect-plug-etc-chromium-native-messaging-jabref Remove Snap Chromium disconnect hook                                          +0/-7      disconnect-plug-etc-opt-chrome-native-messaging-jabref Remove Snap Chrome disconnect hook                                              +0/-7      disconnect-plug-etc-opt-edge-native-messaging-jabref Remove Snap Edge disconnect hook                                                  +0/-7      disconnect-plug-hostfs-mozilla-native-messaging-jabref Remove Snap Firefox disconnect hook                                            +0/-7
Configuration changes	6 files build.gradle.kts Remove native messaging resources from build packaging      +0/-13    jabref.spec Remove native messaging installation from RPM spec              +2/-16    postinst Remove native messaging setup from Debian postinstall        +3/-8      postrm Remove native messaging cleanup from Debian uninstall        +0/-9      postinstall Remove native messaging setup from macOS installer              +2/-11    snapcraft.yaml Remove native messaging plugs and browser-proxy app            +0/-21

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Ensure cleanup of old files Retain the cleanup logic in jabgui/buildres/linux/postrm for native messaging host files to ensure a clean upgrade path for users and prevent orphaned files. jabgui/buildres/linux/postrm [20-25] case "$1" in purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) + # Remove the native-messaging hosts script only if relative to the deb package + for NATIVE_MESSAGING_JSON in "/usr/lib/mozilla/native-messaging-hosts/org.jabref.jabref.json"\ + "/etc/chromium/native-messaging-hosts/org.jabref.jabref.json"\ + "/etc/opt/chrome/native-messaging-hosts/org.jabref.jabref.json"\ + "/etc/opt/edge/native-messaging-hosts/org.jabref.jabref.json"; do + if [ -e $NATIVE_MESSAGING_JSON ] && grep --quiet '"path": "/opt' $NATIVE_MESSAGING_JSON; then + rm -f $NATIVE_MESSAGING_JSON + fi + done # Remove the auto-install triggers of the browser addon for chrom/chromium rm -f /opt/google/chrome/extensions/bifehkofibaamoeaopjglfkddgkijdlh.json rm -f /usr/share/google-chrome/extensions/bifehkofibaamoeaopjglfkddgkijdlh.json ;; [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that removing the cleanup logic from the postrm script will leave orphaned files on users' systems when upgrading, which is poor package management practice.	Medium
Update

[Siedlerchr]

We should really wait that we have the new extension published first

[github-actions]

Your pull request conflicts with the target branch.

Please merge with your code. For a step-by-step guide to resolve merge conflicts, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.

[koppor]

Will probably a longer discussion - JabRef/JabRef-Browser-Extension-fresh#18

The maintainer of the 2025 extensions is not convinced of HTTP being the more proper interface. Main reason: Starting of JabRef and then doing an HTTP call is sometimes unreliable.

[github-actions]

The build of this PR is available at https://builds.jabref.org/pull/14884/merge.

[Siedlerchr]

I postponed this to beta until we have cusotm url protocol handling in