| Crates.io | bloss-native |
| lib.rs | bloss-native |
| version | 0.2.0 |
| created_at | 2023-03-21 14:41:05.734745+00 |
| updated_at | 2023-03-29 15:39:43.051388+00 |
| description | Native messaging host for OpenPGP smart card signing |
| homepage | |
| repository | https://github.com/harrisluo/bloss |
| max_upload_size | |
| id | 816241 |
| size | 35,227 |
Bloss (Web Library for Openpgp Smartcard Signing) enables Chrome extensions to produce digital signatures for arbitrary messages using locally connected OpenPGP smart cards.
bloss-native is the native messaging host that serves as the middleware
between the browser code and smart cards. It communicates with the smart
cards using CCID connections (which are inaccessible by browser code) and
communicates with browser code by passing JSON messages through standard
input/output streams, as per the chrome native messaging API.
The provided install.sh works for macOS and Linux systems.
./install.sh <your Chrome extension ID>
It will download and install bloss-native from crates.io and register it as a
Chrome native messaging host. Your extension will be listed as an allowed
origin in the host's manifest.
Alternatively, you can do the same thing manually by following the steps below.
bloss-native executableRun the following to download and install from crates.io:
cargo install bloss-native
This will install the bloss-native executable in your preconfigured Cargo
installation root (details).
If you don't have one configured, the default installation location is
$HOME/.cargo/bin/bloss-native.
bloss-native as native messaging hostCopy the provided com.harrisluo.bloss_native.json manifest into the native
messaging hosts directory. See the
Chrome docs
to find out where this is for your browser and operating system.
In the manifest, replace HOST_NAME with the absolute path to the newly
installed bloss-native executable. Replace EXTENSION_ID with the ID of
the Chrome extension that will use the native messaging host.
Browser extensions communicate with bloss-native using the Chrome native
messaging protocol (details).
Messages are JSON-encoded.
{"command":"ListCards"}Return the list of OpenPGP smart cards connected to the local machine.
{"command":{"SignMessage":{"aid":"<AID>","message":[<message>],"pin":[<pin>]}}}Sign a message with the signing key of the OpenPGP smart card specified by the
application identifier <AID>. The message is a JSON-encoded list of integers
in the range [0, 255] (the bytes of the message). For PIN-protected cards, the
PIN must be provided as a list of integers in the range [0, 255] (the ASCII
encoding of the PIN string).