Arch Linux User Repository

The upgrade to 1.7.5 brought a lot of security fixes. Please upgrade! The custom directory in /etc/etherpad-lite was replaced by no-skin, introducing a new skin system. The credentials.json file was added and can be used to setup credentials as well.

I updated to 1.6.2.

Please note: From now on, etherpad-lite is relying on systemd-tmpfiles and systemd-sysusers and the setting of a dynamic StateDirectory according to its service file. The scripts delivered by upstream are no longer run.

These new features make the package more secure, but the new way of installing it also renders its content static (i.e. the installation of plugins is currently not possible, as the installation folder is now owned by root).

Before the included npm package had the possibility to install all over the install directory, leading to folders and files not taken care of or cleaned up by pacman.

Although the new state is somewhat unfortunate, I hope you can appreciate it nonetheless from a viewpoint of this now being a "clean(er) install".

I referred to upstream about the changes to maybe inspire a change in the way plugins should be installed to a dedicated (settable) directory.

The way etherpad-lite is installed now is still far from being perfect.

Thank you @dvzrv for both answers. I tried to look for a "self-contained" Etherpad-lite (via nw.js or electron) to adapt this webapp for a desktop use (with a .desktop file and an icon and all) and to which we could maybe add modules, but to no avail. I'll keep doing it this way or go the manual install route if I really need the plugins.

@neitsab: Yes, using this package, etherpad-lite can not install plugins (because the unregulated access to the file system is a high security risk). As long as upstream doesn't find a way to specify a custom location for plugins, this will remain that way.

Furthermore, this PKGBUILD tracks stable releases. If you require a more recent version for yourself, you can either modify the PKGBUILD or create a new one (e.g. for a -git package).

Edit: sorry, hadn't read the pinned comment from 2017 :D

So for now using this package, it is completely impossible to install plugins? Nobody has found a workaround?

I like the cleanliness of the install but it drastically reduces the interest of the software.

Unrelated question: noticed the official homepage offers the latest 18.8 beta version to download... Should this package follow that or remain on GitHub releases?

Thanks!

The upgrade to 1.7.5 brought a lot of security fixes. Please upgrade! The custom directory in /etc/etherpad-lite was replaced by no-skin, introducing a new skin system. The credentials.json file was added and can be used to setup credentials as well.

@dvzrv thanks a lot for giving my old package new love! :)

@immae: Honestly, I would refrain from ever running npm as root.

That being said, I think, that the cleanest way would probably be to define a separate folder for the "user installed" packages, to not pollute the static set of packaged node packages, that come with the application. This directory for the user installed packages would need to be writable by the user running etherpad-lite (this should also never be root), ideally somewhere under /var/lib/etherpad-lite. Sadly, this has not yet been implemented upstream (which is barely keeping up with updating the security hole infested plugins, etherpad-lite is built from).

I’ll answer my own question, maybe it can help other people with the same problem. So actually, etherpad tries to initialize each module, creating a .ep_initialized in each of them. This call hangs forever, thus making the whole thing hang too (for reference: src/static/js/pluginfw/plugins.js method callInit).

It turns out that most modules don’t have an initialization hook (I have 20 and none of them has it), so just touch-ing the .ep_initialized file of each module will unlock the process.

This permits at least to load a bunch of modules installed manually. It doesn’t solve every case, but it may help.

Hello @dvzrv, Thanks for your packaging. The idea of making the /usr/share folder static is nice. However I tried to install plugins manually, doing npm install as root from the /usr/share/etherpad-lite, but the start of etherpad then stales waiting for something forever (and never listening).

Did you manage to do this kind of manual installation? You seem to suggest so in the github issue, but maybe I missed something. Modules installation seem to say it should work to just run this npm install (e.g. https://www.npmjs.com/package/ep_infopanel )

@schimicata: my bad, forgot to run updpkgsums. It's now fixed.

upgrave from v1.6.3 to v1.6.5 fails with:

==> Validating source files with sha512sums...

etherpad-lite-1.6.5.tar.gz ... Passed
jquery-1.9.1.js ... Passed
etherpad-lite-sysusers.conf ... Passed
etherpad-lite-tmpfiles.conf ... Passed
etherpad-lite.service ... FAILED

==> ERROR: One or more files did not pass the validity check!

:: failed to verify etherpad-lite integrity