ElCanut@jlai.lu to Programmer Humor@programming.dev · 6 days agoAsking the real questionsjlai.luimagemessage-square176fedilinkarrow-up11.15Karrow-down111
arrow-up11.13Karrow-down1imageAsking the real questionsjlai.luElCanut@jlai.lu to Programmer Humor@programming.dev · 6 days agomessage-square176fedilink
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up5·6 days agoThat’s easy, just call it Jhon\nDoe
minus-squareriodoro1@lemmy.worldlinkfedilinkarrow-up2·6 days agoJohn\0Doe will fuck with all C (and C based derivatives) software that touches it.
minus-squareperviouslyiner@lemmy.worldlinkfedilinkarrow-up2·6 days agoWith an address in 's-Hertogenbosch to help people who are lazy about escaping.
minus-squarepelya@lemmy.worldlinkfedilinkarrow-up1·6 days agoNah, it will end up simply as “John” in the database. You need “John%sDoe” to crash C software with unsafe printf() calls, and even then it’s better to use several “%s”
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up0·6 days agoC and C derivatives will be fine unless they’re fucking up encoding.
minus-squareAnUnusualRelic@lemmy.worldlinkfedilinkarrow-up1·6 days agoWhich rarely, if ever, happens. Especially with US software.
That’s easy, just call it Jhon\nDoe
John\0Doe will fuck with all C (and C based derivatives) software that touches it.
With an address in 's-Hertogenbosch to help people who are lazy about escaping.
Nah, it will end up simply as “John” in the database. You need “John%sDoe” to crash C software with unsafe printf() calls, and even then it’s better to use several “%s”
C and C derivatives will be fine unless they’re fucking up encoding.
Which rarely, if ever, happens. Especially with US software.