From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] config: remove insecure warnings Date: Tue, 6 Dec 2016 13:24:29 -0800 Message-ID: <20161206132429.5fa32cb5@xeon-e3> References: <1480889826-3891-1-git-send-email-thomas.monjalon@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pg0-f51.google.com (mail-pg0-f51.google.com [74.125.83.51]) by dpdk.org (Postfix) with ESMTP id 800D637B8 for ; Tue, 6 Dec 2016 22:24:47 +0100 (CET) Received: by mail-pg0-f51.google.com with SMTP id x23so153340239pgx.1 for ; Tue, 06 Dec 2016 13:24:47 -0800 (PST) In-Reply-To: <1480889826-3891-1-git-send-email-thomas.monjalon@6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Sun, 4 Dec 2016 23:17:06 +0100 Thomas Monjalon 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 Agreed, this is better done by fortify and other static checkers anyway.