ElCanut@jlai.lu to Programmer Humor@programming.dev · 1 day agoAsking the real questionsjlai.luimagemessage-square187fedilinkarrow-up1961arrow-down16
arrow-up1955arrow-down1imageAsking the real questionsjlai.luElCanut@jlai.lu to Programmer Humor@programming.dev · 1 day agomessage-square187fedilink
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up106·1 day agoThat’s easy, just call it Jhon\nDoe
minus-squareriodoro1@lemmy.worldlinkfedilinkarrow-up74arrow-down1·1 day agoJohn\0Doe will fuck with all C (and C based derivatives) software that touches it.
minus-squareperviouslyiner@lemmy.worldlinkfedilinkarrow-up7·24 hours agoWith an address in 's-Hertogenbosch to help people who are lazy about escaping.
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up20·1 day agoC and C derivatives will be fine unless they’re fucking up encoding.
minus-squareAnUnusualRelic@lemmy.worldlinkfedilinkarrow-up16·23 hours agoWhich rarely, if ever, happens. Especially with US software.
minus-squarepelya@lemmy.worldlinkfedilinkarrow-up68·24 hours 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”