Pro@programming.dev to Programming@programming.devEnglish · 4 days agoCursed knowledge we have learned as a result of building Immich that we wish we never knew.immich.appexternal-linkmessage-square56fedilinkarrow-up1145arrow-down14
arrow-up1141arrow-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 · 4 days agomessage-square56fedilink
minus-squarePhen@lemmy.eco.brlinkfedilinkarrow-up3·4 days 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-up5·4 days 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·4 days agoAs long as it runs the same code, yes. But things may change, clients may pre-emptively split the string or stuff like that.
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.