Replies: 1 comment
-
|
Disabling hkdf is a potential security issue. Why would you want this?
It's still supported for backwards compatibility. Example:
https://github.com/rfjakob/gocryptfs/blob/master/tests/example_filesystems/v0.9/gocryptfs.conf
…On Tue, 18 Mar 2025, 15:46 Lars Quentin, ***@***.***> wrote:
Hi,
I just wondered how it is even possible to disable hkdf. I saw that there
are routines for a single-key mode, but
- cli defaults to true
- there does not exist a --nohkdf
My current hacky experiments rely on hkdf being enabled, so I am just
curious about when my tests will break.
—
Reply to this email directly, view it on GitHub
<#902>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACGA72RUTYB5X4VC2Q6SWD2VAWTTAVCNFSM6AAAAABZILTBWKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGA4TQNZWGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I just wondered how it is even possible to disable hkdf. I saw that there are routines for a single-key mode, but
--nohkdfMy current hacky experiments rely on hkdf being enabled, so I am just curious about when my tests will break.
PS: And does it make sense to add a
-nohkdfflag like the other-noX? If so I can ofc do it hereBeta Was this translation helpful? Give feedback.
All reactions