cryfs VS age

I know that cryfs[1] is resilient to at least the first of these, and possibly the second as well. I don't know if cryfs allows to modify the base directory while the filesystem is online, if it does then it might already be a better solution for syncthing, if you only care about Linux.

On the flip side syncthing could incorporate cryfs's base directory format instead of their home-grown one.

[1] https://www.cryfs.org/

When I tried cryfs mounting via file system, cryfs told me there was no vault at my vault directory. It says specifically, "Could not find base directory. Do you want to create it?"

you have a couple options. if you’re using ext4, fscrypt might be your best bet. if not, a FUSE-based encryption option is probably your only option. ecryptfs, gocryptfs and encfs are good, but i personally prefer cryfs. it doesn’t have an archwiki page, but can be installed from the repos and instructions for use can be found on its webpage

Cryfs encryption for future Cloud Storage = https://www.cryfs.org/

It sounds like cryfs might be helpful for this. It stores an encrypted directory in the cloud but mounts the decrypted contents locally on your hard drive so you can work with them. I'm still looking into it myself but it appears to have been designed to let people use cloud storage without ever revealing the contents to the provider.

See https://github.com/cryfs/cryfs/issues/335

CryFS - Intended to replace eCryptfs and fscrypt (which you can also look at if CryFS doesn't work for you) and add improvements. Unlike LUKS and veracrypt, you don't have to allocate the space in advance; as you add more data it just has more files containing the encrypted data. It is also intended to work with cloud sync things like Dropbox. So I expect you should also be able to store it in an NFS or samba share and then mount it so the encryption happens locally and the server never sees the unencrypted data. If you use KDE, the "vaults" program provides a good UI. Details at https://www.cryfs.org/

Instead of large containers, perhaps use something like CryFS so the uploads are not as large? See https://www.cryfs.org/

Exemplo: https://www.cryfs.org/

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).