Package Details: cryptomator-bin 1.5.15-2

Git Clone URL: https://aur.archlinux.org/cryptomator-bin.git (read-only, click to copy)
Package Base: cryptomator-bin
Description: Multiplatform transparent client-side encryption of your files in the cloud.
Upstream URL: https://cryptomator.org/
Keywords: AppImage binary cryptography encryption
Licenses: GPL3
Conflicts: cryptomator
Replaces: cryptomator
Submitter: ajgraves
Maintainer: ajgraves (overheadhunter, SailReal)
Last Packager: SailReal
Votes: 7
Popularity: 2.89
First Submitted: 2021-05-02 19:50
Last Updated: 2021-07-17 13:47

Pinned Comments

ajgraves commented on 2021-05-02 20:00

Hello everyone! This is a new package, created from cryptomator which is being updated to build from source. This package will always install the latest binary (AppImage) as built from upstream. If you'd rather build the app from source, please use the cryptomator package instead.

Latest Comments

ajgraves commented on 2021-07-09 21:09

The latest release on Linux is 1.5.15, which is the version of this package. For the person who flagged it out of date because 1.5.16 exists, if you look at that package it was a hotfix for Windows only, and as such, no 1.5.16 was released for the Linux platform.

SailReal commented on 2021-07-04 10:51

@reprograph if your pgp keyring is configured correctly, keys should be importable automatically while installing something using a package manager:

yay -S cryptomator-bin
...
:: PGP keys need importing:
 -> 58117AFA1F85B3EEC154677D615D449FE6E6A235, required by: cryptomator-bin
==> Import? [Y/n] y
:: Importing keys with gpg...
gpg: key 615D449FE6E6A235: public key "Cryptobot <releases@cryptomator.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1

I lately had the same problem, that keys couldn't be resolved. What happens if you enter gpg --search-keys 58117AFA1F85B3EEC154677D615D449FE6E6A235 into the console? If the response is something like gpg: keyserver receive failed: No name there is something wrong with your gpg keyring. I looked over a tone of posts and I can not say why but resetting my keyserver in /home/$USER/.gnupg/gpg.conf to the same server (in my case hkps://keys.openpgp.org) fixed this problem.

reprograph commented on 2021-07-04 04:40

With the PGP signature verification that was added recently, I had to curl -sS https://gist.githubusercontent.com/cryptobot/211111cf092037490275f39d408f461a/raw/d416c6f0d35506116436cbe2f872baa217f3f72a/E6E6A235.asc | gpg --import - to install this.

ajgraves commented on 2021-05-02 20:00

Hello everyone! This is a new package, created from cryptomator which is being updated to build from source. This package will always install the latest binary (AppImage) as built from upstream. If you'd rather build the app from source, please use the cryptomator package instead.