Cryptomator encfs archive#
Cryptomator encfs software#
Cryptomator encfs code#

Cryptomator encfs archive#

I don’t want to wait half an hour to delete a file and then another half an hour to add one because the whole archive has to be repacked each time I do something. Something that wouldn’t be so slow and clunky to use when I want to edit the contents of these folders such as opening, removing & adding files etc would be nice. It’d be nice if I could just use my file browser as normal (or another GUI) and be prompted for a password when I try to access one of these encrypted folders. I’m not actually interested in compressing these folders, I just want them encrypted but I’d also like something much more convenient for everyday use. It’s definitely not ideal for regular use. This file stored app client secrets to access cloud storages, they can't share.I’ve tried encrypting folders with 7zip using the built in ‘Ark’ tool, but even when done with the lowest compression level, editing and just generally using these archives is slow and cumbersome. The Apple Store version ccViewer is just different in 'RemoteCloud/RemoteCloud/Secret.swift'. User secret information stored in iOS keychain.

Cryptomator encfs code#

This app plan to play video and audio files trans-decrypting on the fly, I decided using encryption code written by swift referenced to original algorithm. It is one choice that using other binary as is, but is difficult compiling in iOS and combining to my module. So, Cryptomator encryption method changed, this app need to follow it but not yet ( #31).

Cryptomator encfs software#

I referenced official documents and source code and translated to swift because iOS software needs this language. This app using encryption routine translated to swift by my own. This app is open source, you can compile it for your own binary. I can't find anything quite like it, so I hope your answers reassure me that it is a good choice for my usecase Are the mechanisms used by the original teams being for storing this information being used by ccviewer or have you chosen another approach? Is your approach a common strategy used by iphone apps? These encrypted files hold stuff I am not particularly interested in sharing with cloud providers.īut to be comfortable accessing this data with ccviewer, I want to know the following things:Īre you using existing software packages (in the form of compiled codes from publicly available source from rclone, plcloud, etc) that have been embeded into ccviewer, or are you replicating the algorithms found in those packages? I would feel more comfortable knowing that the codes are directly taken from the original authors and updated when bugs are found and fixed by those teams, rather than using some method of translating those codes (by hand or automatically) to another language.Ĭan you describe the mechanisms you are using for storing (or not) the passwords, keys, bucket IDs, necessary to access the encrypted files? I would like to make sure that these pieces of information are handled securely, and I would like to make sure that they are not accessible to other apps. I am very interested in ccviewer, but I don't have enough info to decide whether to use it.īecause most cloud providers already have pretty good apps for accessing unencrypted files on an iphone, my usecase is primarily to access encrypted files (encrypted using rclone, cryptomator, encfs, etc) that I have stored on the cloud).