From owner-freebsd-bugs Sat Aug 2 04:42:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA20392 for bugs-outgoing; Sat, 2 Aug 1997 04:42:06 -0700 (PDT) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA20378 for ; Sat, 2 Aug 1997 04:41:55 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.5/8.8.5) id OAA07494; Sat, 2 Aug 1997 14:40:38 +0300 (EET DST) From: Ruslan Ermilov Message-Id: <199708021140.OAA07494@relay.ucb.crimea.ua> Subject: CERT Advisory CA-97.17 - Vulnerability in suidperl (sperl) question... To: jkh@time.cdrom.com Date: Sat, 2 Aug 1997 14:40:38 +0300 (EET DST) Cc: freebsd-bugs@freebsd.org X-My-Interests: Unix,Oracle,Networking X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Jordan and other readers! As I know from my up-to-date CVS tree, FreeBSD Project didn't anything to solve the problem described in CERT Advisory CA-97.17 - Vulnerability in suidperl. I think you should at least make /usr/bin/suidperl not setuid in the -stable and -current. What is the reason why you can't upgrade perl version or make suidperl not setuid? Thanks in advance, -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247 647 Simferopol, Crimea