qaz@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · edit-224 days agoPlease pick a password starting with ad and ending with minlemmy.worldimagemessage-square127fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1imagePlease pick a password starting with ad and ending with minlemmy.worldqaz@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · edit-224 days agomessage-square127fedilinkfile-text
minus-squareBjörn Tantau@swg-empire.delinkfedilinkEnglisharrow-up0·24 days agoTake a string as bytes is bad with weird non-ASCII characters. Been there, been bitten in the ass by it. At least with e-mail clients different clients on different operating systems use different encoding by default for their passwords. With a router I could imagine different client apps following different standards.
minus-squareexpr@programming.devlinkfedilinkEnglisharrow-up0·24 days agoYou don’t have to take arbitrary bytes. UTF-8 encoded strings are just fine and easily handled by libraries.
minus-squareBjörn Tantau@swg-empire.delinkfedilinkEnglisharrow-up0·24 days ago At least with e-mail clients different clients on different operating systems use different encoding by default for their passwords.
minus-squareexpr@programming.devlinkfedilinkEnglisharrow-up0·24 days agoThe manufacturer obviously also makes the app and can control the encoding.
Take a string as bytes is bad with weird non-ASCII characters. Been there, been bitten in the ass by it.
At least with e-mail clients different clients on different operating systems use different encoding by default for their passwords.
With a router I could imagine different client apps following different standards.
You don’t have to take arbitrary bytes. UTF-8 encoded strings are just fine and easily handled by libraries.
The manufacturer obviously also makes the app and can control the encoding.