Bug#911189: src:gpgme1.0: please ship gpgme-json with native messaging hooks for chromium and firefox
Building gpgme by hand and and installing gpgme-json manually every time after gpgme updates is getting rather tedious. The MR by Sascha Wilde at https://salsa.debian.org/debian/gpgme/-/merge_requests/2 works perfectly here. This bug is three years old and the patch more than a year, could someone please have a look at merging it? Best, Teemu
Bug#911189: src:gpgme1.0: please ship gpgme-json with native messaging hooks for chromium and firefox
Has there been any progress on this? Ubuntu currently ships an equivalent package, although it doesn't contain the firefox manifest (presumably because of the config file issue mentioned by Sascha above). From my understanding, a per-extension manifest file is intended to be shipped as part of the webext-* package for the extension, and not with the native helper. Compare with webext-browserpass: ``` $ dpkg -L webext-browserpass | grep native-messaging /etc/chromium/native-messaging-hosts /etc/chromium/native-messaging-hosts/com.github.browserpass.native.json /usr/lib/mozilla/native-messaging-hosts /usr/lib/mozilla/native-messaging-hosts/com.github.browserpass.native.json ``` Confusion may have arisen because most webextensions (such as browserpass) ship the extension and the native helper app in the same package, making it unclear where the manifest belongs when the native helper is in a separate package (as gpgme must if it is to be shared between applications). This would imply that the correct place for the manifests is in a notional `webext-mailvelope` package, where they SHOULD NOT be marked as config. Packaging mailvelope properly would greatly improve the user experience (see e.g. https://github.com/mailvelope/mailvelope/issues/628 , https://github.com/mailvelope/mailvelope/issues/699 ). -- Andrew Gallagher OpenPGP_signature Description: OpenPGP digital signature
Bug#911189: src:gpgme1.0: please ship gpgme-json with native messaging hooks for chromium and firefox
Package: libgpgme11 Version: 1.12.0-4~bpo9+1 Followup-For: Bug #911189 Dear Maintainer, the Firefox and Chrome extension Mailvelope needs gpgme-json. The extension provides GPG encryption/decryption via webmail. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/3 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE:de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgpgme11 depends on: ii gnupg 2.2.12-1~bpo9+1 ii gpg2.2.12-1~bpo9+1 ii libassuan0 2.5.2-1~bpo9+1 ii libc6 2.24-11+deb9u3 ii libgpg-error0 1.26-2 Versions of packages libgpgme11 recommends: ii dirmngr 2.2.12-1~bpo9+1 ii gpg-agent 2.2.12-1~bpo9+1 ii gpg-wks-client 2.2.12-1~bpo9+1 ii gpgsm 2.2.12-1~bpo9+1 libgpgme11 suggests no packages. -- no debconf information
Bug#911189: src:gpgme1.0: please ship gpgme-json with native messaging hooks for chromium and firefox
Package: src:gpgme1.0 Version: 1.12.0-1 Severity: wishlist as of gpgme 1.12.0-1, GPGME ships a javascript binding that works with so-called "Native Messaging" in both chrome and firefox. we should ship this as a separate binary package, along with the appropriate extension manifests. for more details, see lang/js/README in the GPGME sources, and the following web references: Firefox: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests Chrome: https://developer.chrome.com/extensions/nativeMessaging I plan to work on this, but if anyone wants to send patches before i get to it, i'd be happy to get them too :) at the moment, i assume that we just would disallow access to any extensions, until some extension shows up that wants to use it. We probably also need to build gpgme.js, which will require working with node. i don't know how we'll get the test suites to run cleanly yet either. --dkg -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
