ElCanut@jlai.lu to Programmer Humor@programming.dev · 2 months agoAsking the real questionsjlai.luimagemessage-square219fedilinkarrow-up11.15Karrow-down111
arrow-up11.14Karrow-down1imageAsking the real questionsjlai.luElCanut@jlai.lu to Programmer Humor@programming.dev · 2 months agomessage-square219fedilink
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up113·2 months agoThat’s easy, just call it Jhon\nDoe
minus-squareriodoro1@lemmy.worldlinkfedilinkarrow-up77arrow-down1·2 months agoJohn\0Doe will fuck with all C (and C based derivatives) software that touches it.
minus-squareperviouslyiner@lemmy.worldlinkfedilinkarrow-up9·2 months agoWith an address in 's-Hertogenbosch to help people who are lazy about escaping.
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up20·2 months agoC and C derivatives will be fine unless they’re fucking up encoding.
minus-squareAnUnusualRelic@lemmy.worldlinkfedilinkarrow-up17·2 months agoWhich rarely, if ever, happens. Especially with US software.
minus-squarepelya@lemmy.worldlinkfedilinkarrow-up71·2 months 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”
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.
C and C derivatives will be fine unless they’re fucking up encoding.
Which rarely, if ever, happens. Especially with US software.
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”