Skip to content

Exporting and importing a plugin file

Available with Kino 0.9.74

Available from Kino 0.9.74. No apiVersion change: any plugin can be exported, and a Kino that predates this simply does not open the file.

A repository can disappear. So people can keep a plugin they use, Kino exports any installed plugin as one file: Plugins ▸ Instalados ▸ Gestionar ▸ "Exportar plugin" on a phone shares a <id>-<version>.kinoplugin file. Opening that file with Kino on a phone ("Abrir con Kino", or Plugins ▸ Agregar ▸ "Importar plugin desde un archivo") shows the same consent sheet as an install from GitHub and installs it as a local plugin: it has no repository, it never updates by itself, and it stays on that device (plugin sync does not carry code, so the person shares the file again to put it on another device).

What the file holds

It is a backup of the code, not of the person's data. The file is a ZIP holding exactly kino-plugin.json (byte for byte as installed, signature included), your entry script, your icon and panel.iconFile, and a kino-export.json that names every other entry with its sha256 and the GitHub address it was installed from (originalAddress, or null). Never the person's settings, passwords, sealed or open secrets, cookies, storage or approvals. Nuvio scrapers, Stremio addons and CloudStream plugins are generated by Kino and are not exported.

The signature is kept

Your signature binds your owner/repo[/path], and the file carries that address, so an exported signed plugin still verifies on import and shows "Firmado por" with your key's fingerprint. What Kino pins is your key: a file signed by that same key updates (or, confirmed, downgrades) the plugin whatever address it was installed from; a file signed by another key, an unsigned file over your signed plugin, or a signed file over an unsigned install of that id are refused. If your repository is gone and you republish under a new one, sign again there with the same key (the signature names the new owner/repo): a person who kept your plugin as a local file can install the new address over it, because the key matches, and from then on it updates from there again.

Sealed secrets do not travel

Sealed secrets open only against the repository they were sealed for; an imported plugin that declares secrets installs, the sheet says its sealed keys will not work, and kino.secret answers as for an undeclared name.

Modifying and re-sharing

Edit the files, recompute every sha256 in kino-export.json (Kino refuses a file whose content does not match it) and drop the signature block, which no longer verifies over changed code: the result is an unsigned local plugin. Kino refuses names outside that list, .., absolute paths, symlinks, duplicates, files past the installer's caps (script 1 MB, manifest 16 KB, whole file 8 MB) and an apiVersion this Kino does not support. The id of a recommended plugin is taken only by a file signed with that plugin's author key.