From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: remove insecure warnings
Date: Tue, 6 Dec 2016 13:24:29 -0800 [thread overview]
Message-ID: <20161206132429.5fa32cb5@xeon-e3> (raw)
In-Reply-To: <1480889826-3891-1-git-send-email-thomas.monjalon@6wind.com>
On Sun, 4 Dec 2016 23:17:06 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> There was an option CONFIG_RTE_INSECURE_FUNCTION_WARNING (disabled by
> default), which prevents from using some libc functions:
> sprintf, snprintf, vsnprintf, strcpy, strncpy, strcat, strncat, sscanf,
> strtok, strsep and strlen.
>
> It's all about using them at the right place with the right precautions.
> However, it is neither really possible nor a good advice to disable them.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Agreed, this is better done by fortify and other static checkers anyway.
prev parent reply other threads:[~2016-12-06 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 22:17 Thomas Monjalon
2016-12-05 10:27 ` Bruce Richardson
2016-12-07 17:34 ` Thomas Monjalon
2016-12-06 21:24 ` Stephen Hemminger [this message]
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=20161206132429.5fa32cb5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).