fscrypt.git/README.md, branch v0.3.2 Go tool for managing Linux filesystem encryption Fix a few typos 2021-12-22T05:02:55+00:00 Eric Biggers ebiggers@google.com 2021-12-22T04:59:58+00:00 ee7bd64191beb715f883a7c91f0de0779b849af4 






README: elaborate on alternatives and threat model
2021-12-22T00:17:22+00:00

Eric Biggers
ebiggers@google.com

2021-12-22T00:03:08+00:00

9653450a7b13984f8b4c97ad35eefa8f816d53b4

Fixes https://github.com/google/fscrypt/issues/318





Fixes https://github.com/google/fscrypt/issues/318







README: write "Linux native filesystem encryption"
2021-12-22T00:03:08+00:00

Eric Biggers
ebiggers@google.com

2021-12-22T00:03:08+00:00

d6638ac45f6b6da373f7f724251aef03032915ad

"Linux filesystem encryption" sounds too vague.  Write "Linux native
filesystem encryption" instead.





"Linux filesystem encryption" sounds too vague.  Write "Linux native
filesystem encryption" instead.







README: document issue with ssh ChallengeResponseAuthentication
2021-12-20T02:41:39+00:00

Eric Biggers
ebiggers@google.com

2021-12-20T02:39:26+00:00

c7e3ce28b23017cfcc11a38fee888163d4e8d715

Update https://github.com/google/fscrypt/issues/321
Update https://github.com/google/fscrypt/issues/324





Update https://github.com/google/fscrypt/issues/321
Update https://github.com/google/fscrypt/issues/324







Adjust recovery passphrase generation
2021-10-05T22:30:30+00:00

Eric Biggers
ebiggers@google.com

2021-09-14T21:12:39+00:00

7fed63a84963cbd790e86a0e59ff14724bcf33c4

As per the feedback at https://github.com/google/fscrypt/issues/115
where users didn't understand that the recovery passphrase is important,
restore the original behavior where recovery passphrase generation
happens automatically without a prompt.  This applies to the case where
'fscrypt encrypt' is using a login protector on a non-root filesystem.

However, leave the --no-recovery option so that the recovery passphrase
can still be disabled if the user really wants to.  Also, clarify the
information provided about the recovery passphrase.

Update https://github.com/google/fscrypt/issues/115





As per the feedback at https://github.com/google/fscrypt/issues/115
where users didn't understand that the recovery passphrase is important,
restore the original behavior where recovery passphrase generation
happens automatically without a prompt.  This applies to the case where
'fscrypt encrypt' is using a login protector on a non-root filesystem.

However, leave the --no-recovery option so that the recovery passphrase
can still be disabled if the user really wants to.  Also, clarify the
information provided about the recovery passphrase.

Update https://github.com/google/fscrypt/issues/115







README: mention LTS kernel versions with symlink bug fix
2021-09-22T18:00:27+00:00

Eric Biggers
ebiggers@google.com

2021-09-22T18:00:27+00:00

ee5e47f3481c7f09f4f3f4bdf360f2c8b1b59a1e

Resolves https://github.com/google/fscrypt/issues/305





Resolves https://github.com/google/fscrypt/issues/305







README: clarify how restoring /.fscrypt directory works
2021-09-14T21:33:22+00:00

Eric Biggers
ebiggers@google.com

2021-09-14T18:07:42+00:00

955d3305cd117ad83411f75c2b3227fbaea60700

Update https://github.com/google/fscrypt/issues/115





Update https://github.com/google/fscrypt/issues/115







README: add section about encrypting existing files
2021-09-14T02:33:15+00:00

Eric Biggers
ebiggers@google.com

2021-09-13T23:23:50+00:00

a0ecd4b62adc599d18f7aac10ce2d12aa9eef07a












README: consistently format section titles
2021-09-14T02:33:15+00:00

Eric Biggers
ebiggers@google.com

2021-09-13T21:45:34+00:00

661b943647ee4adbe245a346711933b30ccea0b9

Capitalize the first word only, and don't use periods.





Capitalize the first word only, and don't use periods.







README: add section about backup, restore, and recovery
2021-09-14T02:33:15+00:00

Eric Biggers
ebiggers@google.com

2021-09-13T19:40:14+00:00

1c6d0a5b4b183fb85b20301e3bf96cb7c2126733

Resolves https://github.com/google/fscrypt/issues/51
Resolves https://github.com/google/fscrypt/issues/115





Resolves https://github.com/google/fscrypt/issues/51
Resolves https://github.com/google/fscrypt/issues/115