From owner-freebsd-questions Tue Jan 15 21: 3:56 2002 Delivered-To: freebsd-questions@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 184F637B419; Tue, 15 Jan 2002 21:03:47 -0800 (PST) Received: from dialup-209.245.128.158.dial1.sanjose1.level3.net ([209.245.128.158] helo=blossom.cjclark.org) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16QiEY-00037r-00; Tue, 15 Jan 2002 21:03:38 -0800 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id g0G534P33468; Tue, 15 Jan 2002 21:03:04 -0800 (PST) (envelope-from cjc) Date: Tue, 15 Jan 2002 21:03:03 -0800 From: "Crist J . Clark" To: FreeBSD@jovi.net Cc: freebsd-questions@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG, bug-followup@FreeBSD.ORG Subject: Re: kern/33904: secure mode bug Message-ID: <20020115210303.E31328@blossom.cjclark.org> References: <200201152003.g0FK3gb04767@grant.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200201152003.g0FK3gb04767@grant.org>; from FreeBSD@jovi.net on Tue, Jan 15, 2002 at 03:03:42PM -0500 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 03:03:42PM -0500, FreeBSD@jovi.net wrote: > It would help to document or fix date/ntpdate/ntpd/... ntpdate(8) and ntpd(8) are contributed software. As far as I can tell, FreeBSD uses "virgin" imports. There is no local customization of the code. Maintaining local modifications to code maintained by outside vendors is expensive and therefore needs a lot of justification. > to warn of this "clock clamp" trouble You do get a log message generated at . That tends to be something people notice. > or better yet > fix settimeofday to return EPERM instead of trying > to second-guess the intent of the programmer. That might be a valid option. Would you be willing to patch settime() (in sys/kern/kern_time.c)? Would you be willing to test patches to see if they don't break things even worse? > If not, settimeofday documentation must clarify this silent lossage > of setting a time other than what the calling program specified. This is true. The statements in settimeofday(2) about "secure mode" are actually incorrect. I'll commit a fix shortly. -- "It's always funny until someone gets hurt. Then it's hilarious." Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message