portapps / cryptomator-portable Goto Github PK

Cryptomator 1.5.7 is out for a few days, but portable still 1.5.6.
I presume the builds are manual.

Is it common or easy for the portable packaging to be automated?

Behaviour

Steps to reproduce this issue

1. No “FUSE” virtual drive option found in v 1.6.8. Only WEBDAV which cannot be accessed on all computers.

Expected behaviour

Tell me what should happen

• when opening portable app, there should be FUSE option in virtual drive accessing options.

Actual behaviour

Tell me what happens instead

Configuration

App release / arch (ex. 1.0.0-2 win64) :

Operating system (ex. Windows 10 Pro 64 bits) :
Windows 10 Home 32 bits

Winver screenshot :

Open a command prompt and type winver then take / save the screenshot of the window and drag the image file in this issue. For example: http://bit.ly/2vA5sxR

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

Join the log file log\[appname]-portable.log to this issue.

Hi guys,

thanks for the amazing work.

I just faced an repeatable issue:
When Cryptomator starts on system start up on Windows 10 Enterprise, it does not load the settings.
After exiting Cryptomator and starting it once again, all setting were loaded.

Greetings

Version 1.6.15 is available and portapps only goes to 1.6.10.

I downloaded this portable version of cryptomator. I create a location for the vault, and also verified my password. I try to open it, it errors for multiple issues. Going to the source and using their installer. This portable edition needs a lot of work.

I've also created a PR: #34

Behaviour

Portable version looks for settings in ~/AppData/Roaming/Cryptomator/settings.json and because there is none it loads blank configuration.

Steps to reproduce this issue

1. Install v1.5.11-4 over previous version 1.5.8-3
2. Execute portable Cryptomator.

Expected behaviour

It should loads previously configured vaults.

Actual behaviour

The list of vaults is empty.

Configuration

Portable version 1.5.11-4 64 bits
Windows 10 Pro 64 bits

Logs

cryptomator-portable.log

Behaviour

Files more than a certain size (suspected to be 50MB) cannot be read.

Steps to reproduce this issue

1. Save a file more than, say, 50MB to a vault.
2. Cannot open it thereafter.

Expected behaviour

Tell me what should happen

It should be able to be opened just like in the installed version.

Actual behaviour

Tell me what happens instead

Cannot open.

Configuration

App release / arch (ex. 1.0.0-2 win64) :
1.5.11-5

Operating system (ex. Windows 10 Pro 64 bits) :
Windows 10 Home 64 bits

Winver screenshot :

Open a command prompt and type winver then take / save the screenshot of the window and drag the image file in this issue. For example: http://bit.ly/2vA5sxR

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

Join the log file log\[appname]-portable.log to this issue.

the latest cryptomator-portable (1.5.16-7) can not handle new Vault Format 8 from Cryptomator for Windows Version 1.61

here a small part from the log:

org.cryptomator.cryptolib.api.UnsupportedVaultFormatException: Tried to open vault of version 999, but can only handle version 7

When I try to mount an existing safe opening the vault.cryptomator file on a portable SSD, the file cannot be accessed. I tried to change file permission, but it doesn't work.
The same happens for the masterkey.cryptomator file.
Any workaround or solution to fix this?
Thanks!

Behaviour

I want to set/overwrite the following JavaOptions Parameter in Cryptomator.

[JavaOptions]
-Dcryptomator.logDir=%temp%/cryptomator
-Dcryptomator.settingsPath=../abc/settings.json
-Dcryptomator.ipcPortPath=../xsd/ipcPort.bin
-Dcryptomator.keychainPath=T:/keychain.json
-Dprism.order=sw

How it is to configure in cryptomator-portable that it will be set correct in the file Cryptomator.cfg?

Steps to reproduce this issue

1. I configure the file Cryptomator.cfg from Cryptomator as I want.
2. Start cryptomator-portable

Expected behaviour

My changes should be persist or must be configured on another side

Actual behaviour

My changes in the Cryptomator.cfg file are lost.

Configuration

Version 1.5.6-1 win64

Operating system (ex. Windows 10 Pro 64 bits) : Windows 10 Pro x64

Winver screenshot : Version 2004 (Build 19041.388)

Behaviour

Steps to reproduce this issue

1. Copy Cryptomator portable folder into a OneDrive synchronized folder
2. Launch Cryptomator portable application

Expected behaviour

OneDrive should sync Cryptomator portable folder without issues.

Actual behaviour

After a few minutes, OneDrive has a sync issue due to Cryptomator portable :
cryptomator0.log
This file is in use
This item is open in another program. Close the item to continue syncing it.

Configuration

App release / arch (ex. 1.0.0-2 win64) : Cryptomator Portable

Operating system (ex. Windows 10 Pro 64 bits) : Windows 11 Pro 64bit fully up to date

Note: I have fully read Crytomator website and portapps.io and I have tried:
common:
disable_log: true

as described here: https://portapps.io/doc/configuration/
but it does not change anything to the problem because this is not actually disabling logs.

Note bis: It is an important issue because If a portable version cannot be used in OneDrive, what is the point of having a portable application.

Hello,

I face the issue that cryptomator portable app doesn't start in Windows 8.1 Pro Version 6.3 (build 9600).
Error message: "Command failed"

According to the log it seems there is a problem with java.

cryptomator-portable.log