From: inkswinc@gmail.com
To: cinap_lenrek@felloff.net, 9front@9front.org
Subject: Re: [9front] nupas auth: incompatibility and error messaging
Date: Wed, 22 Mar 2017 17:10:54 +0000 [thread overview]
Message-ID: <e3a731ad1bfdf50ec45becc6c80acd85@cirno.sam-d.org> (raw)
In-Reply-To: 744dfa9c54bf8193702470c2385fe6d9@felloff.net
On Wed, 22 Mar 2017 10:17:14 +0100, cinap_lenrek@felloff.net wrote:
> to be clear, this is like:
>
> buf = ... usercontrolled string ...
>
> print(buf); vs print("%s", buf);
>
> the former allows you to crash the program.
>
> --
> cinap
Ah, thanks. I'd always seen the latter style, but it never clicked
for me why it was done that way. Makes a lot of sense now... time
to grep through my programs and see all the other places I've made
this mistake.
- sam-d
next reply other threads:[~2017-03-22 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:10 inkswinc [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-22 17:09 inkswinc
2017-03-22 9:17 cinap_lenrek
2017-03-22 9:15 cinap_lenrek
2017-03-22 3:16 inkswinc
2017-03-22 0:02 inkswinc
2017-03-22 2:53 ` [9front] " Benjamin Purcell
2017-03-22 2:58 ` Benjamin Purcell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3a731ad1bfdf50ec45becc6c80acd85@cirno.sam-d.org \
--to=inkswinc@gmail.com \
--cc=9front@9front.org \
--cc=cinap_lenrek@felloff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).