Package Details: cryptomator-bin 1.14.2-1

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
Provides: cryptomator
Replaces: cryptomator
Submitter: ajgraves
Maintainer: ajgraves (overheadhunter, SailReal, as.skymatic)
Last Packager: as.skymatic
Votes: 31
Popularity: 0.98
First Submitted: 2021-05-02 19:50 (UTC)
Last Updated: 2024-11-19 11:42 (UTC)

Pinned Comments

ajgraves commented on 2021-05-02 20:00 (UTC)

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

« First ‹ Previous 1 2 3 Next › Last »

purejava commented on 2022-03-02 06:43 (UTC)

@SailReal Thanks for testing. It's GNOME on Arch linux (VM). I could not reproduce it either. I re-tested on a different VM (GNOME on Arch linux as well) today and it worked fine. Sorry for the noise.

SailReal commented on 2022-03-01 23:00 (UTC)

@purejava what distro and DE do you use? On Manjaro using GNOME it works for me using cryptomator and cryptomator-bin

purejava commented on 2022-02-28 06:42 (UTC)

cryptomator-bin does not read contents of the pluginDir: ~/.local/share/Cryptomator/plugins and hence not uses the keepassxc-cryptomator plugin when startet via the .desktop entry. It does use the pluginDir when startet via the CLI.

SailReal commented on 2021-10-19 21:59 (UTC)

@f0xa69 cryptomator-bin provides implicitly only cryptomator-bin but now cryptomator too, thanks for the hint :)

f0xa69 commented on 2021-10-19 21:33 (UTC)

Could you add a provides=('cryptomator') line to the PKGBUILD, so i can use this pkg together with the new keepassxc-cryptomator plugin? That'd be awesome, thx!

Dwa30v commented on 2021-09-09 16:18 (UTC)

@ajgraves, thanks a lot for the help. Appreciated!

ajgraves commented on 2021-09-09 14:55 (UTC)

@Dwa30v, you need to import the key first. Do gpg --recv-keys 615D449FE6E6A235 which will import the PGP key for releases@cryptomator.org, then re-try your update.

Dwa30v commented on 2021-09-09 06:25 (UTC) 

==> Verifying source file signatures with gpg...
    cryptomator-1.5.17-1-x86_64.AppImage ... FAILED (unknown public key 615D449FE6E6A235)
==> ERROR: One or more PGP signatures could not be verified!
Error: Failed to build cryptomator-bin

ajgraves commented on 2021-07-09 21:09 (UTC)

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 (UTC)

@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.

« First ‹ Previous 1 2 3 Next › Last »