From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=J4uoZjelFbrMpnn5nPTveM/wbZL2pnX1VlOHbN4mgfE=; b=vDvqHrA6ztzgoysP490Q+c8gnMnvY1D9z+NGPuWVxdYlmTSJSdDXpGDxVs97eg+ACQ V1FyVT5q1hkvO7/SFqlC95j1zthoTBJPJaMmcMIn1aZpav+msJpjJYTeKhYyo3L8hZkS J0h5G5/4cW5EBEWEhPFhkyA4jvIVvdBGMT6Ndi6G8hz5grwowt416QKmZVT3MnYICe9L ufjiqri/Bdr3yucVCZVbYJ+RY9575KziKQPJ3InV+MpWDxu2v4oCbMR9V/RVHCMdgHK+ z8qapiOKhuPnPaX9AbOuHnB1RYv8YAVyv9oH6Ph4Y2+WB8MXx/CR6hUKyokTp/OXq5Gd 8qJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=J4uoZjelFbrMpnn5nPTveM/wbZL2pnX1VlOHbN4mgfE=; b=CObli/QgNhQaUJK4z4lOAnl9Q+po3sgi+GcXL72yFRvtvh4zviJltO7eV3EJt6TevG 8Iws+hjrJBe3SzSMLJoYX66Ypdx/PLfYbpAEER9ruSeDZzqEBhUexYRWstfkOFL3YX0G cWOlm10Ig+r+A3iKya1/9h03HAT/Ldv/1e9DtLTfTD6GHkmxjvHne7zFhrTAK9H80S2K qh2diaDGwrlrOhkyk/wOz71TJQt93JiodfEpQY6+J621ciu0mX6amTfCt60x67cMYk3n hv+VgiH3db3OZq8J8KFiGdJmvVG6mz/etv6NprdT7Lxq1cpj3Xf3RbhuW57d1z9UUpIM EFwQ== X-Gm-Message-State: AKaTC0310mfC96Yt+QomERPaMl2IhBLRUD5QJ3r3LLqC01lFuIkFHFx2UKkbKIqzmPz1ig== X-Received: by 10.98.141.74 with SMTP id z71mr64803761pfd.53.1481059486722; Tue, 06 Dec 2016 13:24:46 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id p13sm37027135pgf.47.2016.12.06.13.24.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 06 Dec 2016 13:24:43 -0800 (PST) Date: Tue, 6 Dec 2016 13:24:29 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: dev@dpdk.org Message-ID: <20161206132429.5fa32cb5@xeon-e3> In-Reply-To: <1480889826-3891-1-git-send-email-thomas.monjalon@6wind.com> 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 Subject: Re: [dpdk-dev] [PATCH] config: remove insecure warnings X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 21:24:47 -0000 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.