Pro@programming.dev to Programming@programming.devEnglish · 1 day agoCursed knowledge we have learned as a result of building Immich that we wish we never knew.immich.appexternal-linkmessage-square41fedilinkarrow-up1113arrow-down13
arrow-up1110arrow-down1external-linkCursed knowledge we have learned as a result of building Immich that we wish we never knew.immich.appPro@programming.dev to Programming@programming.devEnglish · 1 day agomessage-square41fedilink
minus-squareMaestro@fedia.iolinkfedilinkarrow-up9·1 day agoYes. Current best practice is to use pass phrases. They can get long. Also, salt length is added to the password length as well, depending on implementation.
minus-squarePhen@lemmy.eco.brlinkfedilinkarrow-up3·1 day agoImagine getting a multi byte character at the right position to get it split so that one byte gets in and the other doesn’t.
minus-squareMaestro@fedia.iolinkfedilinkarrow-up4·24 hours agoIt doesn’t matter. That will happen for both the stored hash and the entered password, so it still matches.
minus-squarePhen@lemmy.eco.brlinkfedilinkarrow-up1·14 hours agoAs long as it runs the same code, yes. But things may change, clients may pre-emptively split the string or stuff like that.
Yes. Current best practice is to use pass phrases. They can get long. Also, salt length is added to the password length as well, depending on implementation.
Imagine getting a multi byte character at the right position to get it split so that one byte gets in and the other doesn’t.
It doesn’t matter. That will happen for both the stored hash and the entered password, so it still matches.
As long as it runs the same code, yes. But things may change, clients may pre-emptively split the string or stuff like that.