X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-bw0-f43.google.com (mail-bw0-f43.google.com [209.85.214.43]) by lists.alpinelinux.org (Postfix) with ESMTP id 925021EBFF4 for ; Sun, 12 Dec 2010 01:05:37 +0000 (UTC) Received: by bwz14 with SMTP id 14so7880912bwz.16 for ; Sat, 11 Dec 2010 17:05:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=LICKrhNdLZbo7Tm9bXRnQPflydsVFm5mYghQRaDLbUw=; b=gXBNbg6/wpm/dk244PE/k3fG3Ipt9RxZEn3wgXN5OJ+1Nfzcpppx5kLJCFGfSw3+vS XYY8DnoO2aGUnhHbrbqonmSAL4kvPLdDl2StdgtZKcN1GlQl5U1S0eydSm3bZ1yix3O2 EjYLj4m5hg1sBRySKnXheWWQ3SiOk8jORp5lk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=BxFz9LfcYj82OTiFNoJvpLF4a8MPavZNKhSkeACYJqXxwieh8ml2KGifx7D+IrUnkx fVnF/IxFvpIjJimvy0Ahy1Puha0TiCA9kSIuM+FRfPsbeNC0PrWyYqWF1TDPjQY11Yrb ybKTOZALjFXML+Hj6kW4zN7rInDA6aqHNsAjE= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.204.84.93 with SMTP id i29mr2242698bkl.150.1292115935992; Sat, 11 Dec 2010 17:05:35 -0800 (PST) Received: by 10.204.66.82 with HTTP; Sat, 11 Dec 2010 17:05:35 -0800 (PST) Date: Sat, 11 Dec 2010 20:05:35 -0500 Message-ID: Subject: [alpine-devel] Traceroute - should root setuid be enabled? From: Jeff Bilyk To: Alpine Development Content-Type: text/plain; charset=ISO-8859-1 Hi All, Just wondering if there is a situation where we would not want traceroute setuid. Recently ping was enabled, but I've just run into a few circumstances (best example being smokeping network latency monitor) where having traceroute setuid is quite useful. -- Jeff --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---