With scrypt and similar password-based key derivation functions, the salt is like a namespace which ensures an attacker has to start from scratch if they're trying to guess a key derived from a unique salt.
If a salt is reused for two different ciphertexts, then any guesses an attacker makes can be applied to both ciphertexts.
So it's not as bad as nonce or IV reuse, but still best practice is to create a unique random salt for every ciphertext.
conduition
npub1l6…6zvtg
2024-03-14 18:23:59
in reply to nevent1q…0lcp
Author Public Key
npub1l6uy9chxyn943cmylrmukd3uqdq8h623nt2gxfh4rruhdv64zpvsx6zvtgPublished at
2024-03-14 18:23:59Event JSON
{
"id": "42f99b2cc4d3773e0df02d4ca92be28318a203a6561f198c0418320f719e8a47",
"pubkey": "feb842e2e624cb58e364f8f7cb363c03407be9519ad48326f518f976b3551059",
"created_at": 1710440639,
"kind": 1,
"tags": [
[
"e",
"c945a8e49ff5d6610761c49803206bf84f4525bba8625e367c1498b844e9df15",
"",
"root"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
]
],
"content": "With scrypt and similar password-based key derivation functions, the salt is like a namespace which ensures an attacker has to start from scratch if they're trying to guess a key derived from a unique salt. \n\nIf a salt is reused for two different ciphertexts, then any guesses an attacker makes can be applied to both ciphertexts.\n\nSo it's not as bad as nonce or IV reuse, but still best practice is to create a unique random salt for every ciphertext. ",
"sig": "d5faac10ad7b1f350dc32f7e57ac8e5fdfdcfdf6fd8963aadb514d57c2162f504e36b9c7aaf68de06d888430848b2f7a5c2e8c96c26c69504b99cdbd398bf444"
}