Comments (1)
Cryptsetup V2 uses a memory cost of 128MiB, which would be OK for any reasonable Linux system (Debian has a minimum memory of 128MiB on amd64).
Cryptsetup release note wasn't updated for last minute change before actual release.
https://gitlab.com/cryptsetup/cryptsetup/commit/3c2f92a7afc2ae4c99fa937f1b189bc1375374ad see http://www.saout.de/pipermail/dm-crypt/2017-December/005773.html
Default for Argon2i is now 1GB of memory and 2 seconds iteration time (can be changed during
compilation time or later on commandline). The memory is trimmed to 1/2 of detected
physical memory (with minimum 128MB). (Otherwise OOM killer hits cryptsetup.)
and another quote from same post:
If you read Argon2 RFC draft,
https://datatracker.ietf.org/doc/draft-irtf-cfrg-argon2/ you can see this recommendation:"Key derivation for hard-drive encryption, that takes 3 seconds on
a 2 GHz CPU using 2 cores - Argon2id with 4 lanes and 6 GiB of RAM."
Personally I think that 128MB is more sane default than 1GB or 6GB (lol), just wanted to clarify this.
from fscrypt.
Related Issues (20)
- [Feature Request] Fedora Package or SPEC file HOT 2
- Use CLI library to handle completion HOT 1
- [enhancement] Feature request + PoC: Unlock using public key in ssh-agent
- [bug] pam_fscrypt hangs on login via xrdp HOT 9
- PAM setup including pam_fprintd HOT 2
- Feature Request: Enable some way for pam_fscrypt to not lock policies on logout HOT 3
- [Feature Request] Support fido2 hmac-secret
- [Bug] xfce4-screensaver pam not unlocking mount point HOT 1
- fscrypt master key handling at kernel space adding additional secure params. HOT 2
- In fscrypt user space, after removing the key from key ring, the encrypted directories file names continues to be in clear form. HOT 2
- Support for individual files to assigned instead of directory level HOT 3
- "fscrypt metadata add-protector-to-policy" doesn't work in key files HOT 1
- Poor scriptability due to --name not being easily checkable HOT 2
- failureExitCode should return higher number than 1 if user tries to lock an already locked file
- Deleting files from folder encrypted with fscrypt HOT 4
- Partial Decrypt HOT 3
- fscrypt tests fail on non x86_64 arches (aarch64, ppc64le, s390x) HOT 7
- How to resolve "Some processes can't access unlocked encrypted files"? HOT 2
- Should we make the fscrypt metadata harder to delete? HOT 2
- multiple login nodes (multiple lustre client), how should I correctly apply the fscrypt tool to encrypt files under shared storage? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fscrypt.