From owner-freebsd-security@FreeBSD.ORG Tue Feb 5 15:07:04 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDD6016A420 for ; Tue, 5 Feb 2008 15:07:04 +0000 (UTC) (envelope-from SRS0=2UaJgY=S2=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout12.yourhostingaccount.com (mailout12.yourhostingaccount.com [65.254.253.101]) by mx1.freebsd.org (Postfix) with ESMTP id BA71613C459 for ; Tue, 5 Feb 2008 15:07:04 +0000 (UTC) (envelope-from SRS0=2UaJgY=S2=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan21.yourhostingaccount.com ([10.1.15.21] helo=mailscan21.yourhostingaccount.com) by mailout12.yourhostingaccount.com with esmtp (Exim) id 1JMOrJ-00020B-5f for freebsd-security@freebsd.org; Tue, 05 Feb 2008 09:33:13 -0500 Received: from impout03.yourhostingaccount.com ([10.1.55.3] helo=impout03.yourhostingaccount.com) by mailscan21.yourhostingaccount.com with esmtp (Exim) id 1JMOrI-0004Ak-KB for freebsd-security@freebsd.org; Tue, 05 Feb 2008 09:33:12 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9]) by impout03.yourhostingaccount.com with NO UCE id lqZC1Y0020BkWne0000000; Tue, 05 Feb 2008 09:33:12 -0500 X-EN-OrigOutIP: 10.1.18.9 X-EN-IMPSID: lqZC1Y0020BkWne0000000 Received: from c-98-206-161-17.hsd1.il.comcast.net ([98.206.161.17] helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1JMOrI-0007r4-Cu for freebsd-security@freebsd.org; Tue, 05 Feb 2008 09:33:12 -0500 Date: Tue, 5 Feb 2008 08:34:17 -0600 From: "Zane C.B." To: freebsd security Message-ID: <20080205083417.3f3a4a3b@vixen42> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 98.206.161.17 X-EN-OrigHost: c-98-206-161-17.hsd1.il.comcast.net Subject: LOCAL_CREDS and unix domain sockets X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 15:07:05 -0000 With unix domain sockets, unix(4), are LOCAL_CREDS actually supported or not? I've been trying to fetch this from within a Perl script using 'my $local_creds=$some_connection->sockopt(LOCAL_CREDS)', but all I keep getting is a undefined variable in return, as if fetching it is not supported. From owner-freebsd-security@FreeBSD.ORG Tue Feb 5 16:22:26 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E418F16A418 for ; Tue, 5 Feb 2008 16:22:26 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id B603F13C448 for ; Tue, 5 Feb 2008 16:22:26 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 73EE647C05; Tue, 5 Feb 2008 11:22:26 -0500 (EST) Date: Tue, 5 Feb 2008 16:22:26 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Zane C.B." In-Reply-To: <20080205083417.3f3a4a3b@vixen42> Message-ID: <20080205162043.U49855@fledge.watson.org> References: <20080205083417.3f3a4a3b@vixen42> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd security Subject: Re: LOCAL_CREDS and unix domain sockets X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 16:22:27 -0000 On Tue, 5 Feb 2008, Zane C.B. wrote: > With unix domain sockets, unix(4), are LOCAL_CREDS actually supported or > not? > > I've been trying to fetch this from within a Perl script using 'my > $local_creds=$some_connection->sockopt(LOCAL_CREDS)', but all I keep getting > is a undefined variable in return, as if fetching it is not supported. It depends on the version of FreeBSD. Using a C language program I can get and set LOCAL_CREDS on FreeBSD 7.0 and it looks implemented in the kernel. There are also some regression tests although I've not run them, but it appears things are together. Are you running an older FreeBSD version and/or have you rebuilt Perl since support for LOCAL_CREDS was added (April 2005)? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-security@FreeBSD.ORG Tue Feb 5 20:30:17 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73E8516A417 for ; Tue, 5 Feb 2008 20:30:17 +0000 (UTC) (envelope-from SRS0=2UaJgY=S2=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout17.yourhostingaccount.com (mailout17.yourhostingaccount.com [65.254.253.142]) by mx1.freebsd.org (Postfix) with ESMTP id 2DAF513C4E7 for ; Tue, 5 Feb 2008 20:30:16 +0000 (UTC) (envelope-from SRS0=2UaJgY=S2=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan18.yourhostingaccount.com ([10.1.15.18] helo=mailscan18.yourhostingaccount.com) by mailout17.yourhostingaccount.com with esmtp (Exim) id 1JMUQo-0000v7-TM for freebsd-security@freebsd.org; Tue, 05 Feb 2008 15:30:15 -0500 Received: from impout02.yourhostingaccount.com ([10.1.55.2] helo=impout02.yourhostingaccount.com) by mailscan18.yourhostingaccount.com with esmtp (Exim) id 1JMUQo-0004Ud-81; Tue, 05 Feb 2008 15:30:14 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10]) by impout02.yourhostingaccount.com with NO UCE id lwWE1Y0010D2B7u0000000; Tue, 05 Feb 2008 15:30:14 -0500 X-EN-OrigOutIP: 10.1.18.10 X-EN-IMPSID: lwWE1Y0010D2B7u0000000 Received: from c-98-206-161-17.hsd1.il.comcast.net ([98.206.161.17] helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1JMUQn-0004FZ-OR; Tue, 05 Feb 2008 15:30:13 -0500 Date: Tue, 5 Feb 2008 14:31:19 -0600 From: "Zane C.B." To: Fernando Schapachnik Message-ID: <20080205143119.067bd619@vixen42> In-Reply-To: <20080205152110.GE1123@bal740r0.mecon.gov.ar> References: <20080205083417.3f3a4a3b@vixen42> <20080205152110.GE1123@bal740r0.mecon.gov.ar> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: base64 X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 98.206.161.17 X-EN-OrigHost: c-98-206-161-17.hsd1.il.comcast.net Cc: freebsd security Subject: Re: LOCAL_CREDS and unix domain sockets X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 20:30:17 -0000 T24gVHVlLCA1IEZlYiAyMDA4IDEzOjIxOjEwIC0wMjAwDQpGZXJuYW5kbyBTY2hhcGFjaG5payA8 ZnNjaGFwYWNobmlrQG1lY29uLmdvdi5hcj4gd3JvdGU6DQoNCj4gRW4gdW4gbWVuc2FqZSBhbnRl cmlvciwgWmFuZSBDLkIuIGVzY3JpYmnzOg0KPiA+IFdpdGggdW5peCBkb21haW4gc29ja2V0cywg dW5peCg0KSwgYXJlIExPQ0FMX0NSRURTIGFjdHVhbGx5DQo+ID4gc3VwcG9ydGVkIG9yIG5vdD8N Cj4gPiANCj4gPiBJJ3ZlIGJlZW4gdHJ5aW5nIHRvIGZldGNoIHRoaXMgZnJvbSB3aXRoaW4gYSBQ ZXJsIHNjcmlwdA0KPiA+IHVzaW5nICdteSAkbG9jYWxfY3JlZHM9JHNvbWVfY29ubmVjdGlvbi0+ c29ja29wdChMT0NBTF9DUkVEUyknLA0KPiA+IGJ1dCBhbGwgSSBrZWVwIGdldHRpbmcgaXMgYSB1 bmRlZmluZWQgdmFyaWFibGUgaW4gcmV0dXJuLCBhcyBpZg0KPiA+IGZldGNoaW5nIGl0IGlzIG5v dCBzdXBwb3J0ZWQuDQo+IA0KPiBNYXliZSBMT0NBTF9DUkVEUyBpcyBub3QgZGVmaW5lZC4gTWF5 YmUgTE9DQUxfQ1JFRFMoKSAocGVybCANCj4gbm90YXRpb24gZm9yIGNvbnN0YW50cykgd29ya3M/ DQoNCkhtbSwgdGhhdCB0dXJucyBvdXQgdG8gYmUgdGhlIHBvaW50LiBJJ3ZlIGNoZWNrZWQgYW5k IGl0IGlzIG5vdA0KaW4gJy91c3IvbG9jYWwvbGliL3Blcmw1LzUuOC44L21hY2gvU29ja2V0LnBt Jy4NCg0KSSB0aGluayBteSB1bmRlcnN0YW5kaW5nIGlmIHdoZW4gSSBvcmlnaW5hbGx5IHBvc3Rl ZCB0aGUgZW1haWwgd2FzDQp3cm9uZyBhcyB3ZWxsLiBJIG5lZWQgdG8gc2V0IHRoZSBzb2NrZXQg b3B0aW9uIExPQ0FMX0NSRURTIGFuZCBmZXRjaA0KdGhlbSB1c2luZyByZWN2bXNnLg0KDQpDYW4g c29tZSBvbmUgcGxlYXNlIHZlcmlmeSBteSB1bmRlcnN0YW5kaW5nIG9mIHRoaXMgaXMgcmlnaHQ/ DQo= From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 03:38:16 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 092DD16A421 for ; Wed, 6 Feb 2008 03:38:16 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 63B3713C442 for ; Wed, 6 Feb 2008 03:38:15 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so704008nfb.33 for ; Tue, 05 Feb 2008 19:38:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=tibI/VpR9tYjKbN1UZVQgr/uc7DMWu8RRZ3S2dqWr2g=; b=i/nkcbqf74616UDEPEiA4ieaMIZscKMFDrAmLFnlJTd7u1BnWEnZJW7ct+dUtOjDweWDASAdgaWIv8c0b6DdsLEEIYKVCj2MtXbBFayCq8jULikEU3Hel4dodxvOyfeuMhO58a4yi7t1Edua/SaSkeSm8voIryfHX35Sjb10774= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uZ9LnTX3A19pwga5Uok8/UKHfno0OpX09D4+BQt2VSTVmlnxP2TanzDXZDwIxWiBafpBx9z1TnysJALzjsBjencgOA/wFqkm4Vmvc62yHsBQVp1hsrW1xqg0FpMFGGZ5qwBYp7nGhFbbYDOFTz2MlpolF5CqTyuefyX7zxcDoiQ= Received: by 10.78.183.8 with SMTP id g8mr16458453huf.55.1202267393056; Tue, 05 Feb 2008 19:09:53 -0800 (PST) Received: by 10.78.137.9 with HTTP; Tue, 5 Feb 2008 19:09:52 -0800 (PST) Message-ID: <205b7d90802051909s2ed8b77fo9effef8697b0ca7d@mail.gmail.com> Date: Tue, 5 Feb 2008 19:09:52 -0800 From: "Tony Nolo" To: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: failed binary version 6.2-6.3 update using freebsd-update.sh X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 03:38:16 -0000 Hello, It was suggested in ##freebsd that I post this here, rather than in -questions. So here goes. I'm following the instructions for "FreeBSD Update" at http://www.freebsd.org/releases/6.3R/announce.html. It's giving lots of odd messages, and the folks in the irc channel said that it's not normal. When asked, I checked, and I've apparently got sufficient disk space. I'm hoping someone might have suggestions/insight as to the problem. So, here's the output of the session, root@router > fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz freebsd-update-upgrade.tgz 100% of 21 kB 1192 kBps root@router > fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz.asc 100% of 187 B 45 kBps root@router > gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz gpg: Signature made Fri Nov 16 06:01:38 2007 PST using DSA key ID CA6CDFB2 gpg: Good signature from "FreeBSD Security Officer " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: C374 0FC5 69A6 FBB1 4AED B131 15D6 8804 CA6C DFB2 root@router > tar -xf freebsd-update-upgrade.tgz root@router > sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 6.2-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. WARNING: This system is running a "MyRouter" kernel, which is not a kernel configuration distributed as part of FreeBSD 6.2-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "freebsd-update.sh install". The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/catpages world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: kernel/smp Does this look reasonable (y/n)? y Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 6.2-RELEASE for merging... done. Preparing to download files... done. Fetching 287 patches.....10....20....30....40....50....60....70....80....90....100 ....110....120....130....140....150....160....170....180....190....200....210....220 ....230....240....250....260....270....280... done. Applying patches... done. Fetching 19 files... done. freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory freebsd-update.sh: cannot open files/.gz: No such file or directory Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/defaults/periodic.conf Press Enter to edit this file in joe and resolve the conflicts manually... I've googled on "cannot open files/.gz", and get only 2 hits. One's in russian, and the other has no answer. But, this apparently has been seen elsewhere. If you need any further info from me, please let me know. Tony From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 10:54:51 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80C4916A420 for ; Wed, 6 Feb 2008 10:54:51 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 41F7413C45B for ; Wed, 6 Feb 2008 10:54:51 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 9E0E64A018; Wed, 6 Feb 2008 05:54:50 -0500 (EST) Date: Wed, 6 Feb 2008 10:54:50 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Zane C.B." In-Reply-To: <20080205143119.067bd619@vixen42> Message-ID: <20080206105127.V33144@fledge.watson.org> References: <20080205083417.3f3a4a3b@vixen42> <20080205152110.GE1123@bal740r0.mecon.gov.ar> <20080205143119.067bd619@vixen42> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-972508569-1202295290=:33144" Cc: freebsd security , Fernando Schapachnik Subject: Re: LOCAL_CREDS and unix domain sockets X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 10:54:51 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-972508569-1202295290=:33144 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 5 Feb 2008, Zane C.B. wrote: > On Tue, 5 Feb 2008 13:21:10 -0200 Fernando Schapachnik=20 > wrote: > >> En un mensaje anterior, Zane C.B. escribi=F3: >>> With unix domain sockets, unix(4), are LOCAL_CREDS actually supported o= r=20 >>> not? >>> >>> I've been trying to fetch this from within a Perl script using 'my=20 >>> $local_creds=3D$some_connection->sockopt(LOCAL_CREDS)', but all I keep= =20 >>> getting is a undefined variable in return, as if fetching it is not=20 >>> supported. >> >> Maybe LOCAL_CREDS is not defined. Maybe LOCAL_CREDS() (perl notation for= =20 >> constants) works? > > Hmm, that turns out to be the point. I've checked and it is not in=20 > '/usr/local/lib/perl5/5.8.8/mach/Socket.pm'. > > I think my understanding if when I originally posted the email was wrong = as=20 > well. I need to set the socket option LOCAL_CREDS and fetch them using=20 > recvmsg. > > Can some one please verify my understanding of this is right? Yes, that's correct -- you use setsockopt() to request that an SCM_CREDS=20 control message be attached to either every message coming in on the socket= =20 (SOCK_DGRAM) or the first message arriving on accepted sockets (listen=20 SOCK_STREAM). You can then use recvmsg to get the credential information. Alternatively, LOCAL_PEERCRED allows you to query the credential at any tim= e=20 using a socket option for a stream socket (keep in mind that the credential= is=20 cached when the connection is made, and might not reflect the credential of= a=20 process sending on the socket if it's been inherited/passed). Robert N M Watson Computer Laboratory University of Cambridge --621616949-972508569-1202295290=:33144-- From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 20:54:56 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACD9816A41A for ; Wed, 6 Feb 2008 20:54:56 +0000 (UTC) (envelope-from mohacsi@niif.hu) Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by mx1.freebsd.org (Postfix) with ESMTP id 89C0413C469 for ; Wed, 6 Feb 2008 20:54:54 +0000 (UTC) (envelope-from mohacsi@niif.hu) Received: from localhost (localhost [IPv6:::1]) by mail.ki.iif.hu (Postfix) with ESMTP id 6486184AC8 for ; Wed, 6 Feb 2008 21:54:52 +0100 (CET) X-Virus-Scanned: by amavisd-new at mignon.ki.iif.hu Received: from mail.ki.iif.hu ([127.0.0.1]) by localhost (mignon.ki.iif.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id J1mmjLDhCH05 for ; Wed, 6 Feb 2008 21:54:49 +0100 (CET) Received: by mail.ki.iif.hu (Postfix, from userid 9002) id D171B84A83; Wed, 6 Feb 2008 21:54:48 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id D04C384A34 for ; Wed, 6 Feb 2008 21:54:48 +0100 (CET) Date: Wed, 6 Feb 2008 21:54:48 +0100 (CET) From: Mohacsi Janos X-X-Sender: mohacsi@mignon.ki.iif.hu To: freebsd-security@freebsd.org Message-ID: <20080206215314.Y20917@mignon.ki.iif.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: What about FreeBSD? - KAME Project "ipcomp6_input()" Denial of Service X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 20:54:56 -0000 TITLE: KAME Project "ipcomp6_input()" Denial of Service CRITICAL: Moderately critical IMPACT: DoS WHERE: >From remote DESCRIPTION: A vulnerability has been reported in the KAME Project, which can be exploited by malicious people to cause a DoS (Denial of Service). The vulnerability is caused due to an error within the "ipcomp6_input()" function in kame/sys/netinet6/ipcomp_input.c when processing IPv6 packets with an IPComp header. This can be exploited to crash a vulnerable system by sending a specially crafted IPv6 packet. SOLUTION: Fixed in the CVS repository. http://www.kame.net/dev/cvsweb2.cgi/kame/kame/sys/netinet6/ipcomp_input.c.diff?r1=1.36;r2=1.37 PROVIDED AND/OR DISCOVERED BY: US-CERT credits Shoichi Sakane. NetBSD credits the Coverity Prevent analysis tool. ORIGINAL ADVISORY: US-CERT VU#110947: http://www.kb.cert.org/vuls/id/110947 From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 21:51:43 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 645CB16A418 for ; Wed, 6 Feb 2008 21:51:43 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 1354813C455 for ; Wed, 6 Feb 2008 21:51:43 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 16C5C2082; Wed, 6 Feb 2008 22:51:33 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id F2944207F; Wed, 6 Feb 2008 22:51:32 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id CC99984483; Wed, 6 Feb 2008 22:51:32 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Mohacsi Janos References: <20080206215314.Y20917@mignon.ki.iif.hu> Date: Wed, 06 Feb 2008 22:51:32 +0100 In-Reply-To: <20080206215314.Y20917@mignon.ki.iif.hu> (Mohacsi Janos's message of "Wed\, 6 Feb 2008 21\:54\:48 +0100 \(CET\)") Message-ID: <868x1x3g9n.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-security@freebsd.org Subject: Re: What about FreeBSD? - KAME Project "ipcomp6_input()" Denial of Service X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 21:51:43 -0000 Mohacsi Janos writes: > ORIGINAL ADVISORY: > US-CERT VU#110947: > http://www.kb.cert.org/vuls/id/110947 As far as I can tell, FreeBSD's ipcomp implementation is not from KAME, but from OpenBSD, with significant local changes. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 21:54:46 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F43416A420 for ; Wed, 6 Feb 2008 21:54:46 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.181]) by mx1.freebsd.org (Postfix) with ESMTP id 9B3A013C45B for ; Wed, 6 Feb 2008 21:54:45 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so544836ika.3 for ; Wed, 06 Feb 2008 13:54:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=lGKgqakOdl5faOxQLmwDF2CsQT49yHiAuYB3Kqmk+Yw=; b=diRLEQ97ahWs662yuCHErlWIcruTH6u2LjgSYWjq6AtJVeLccq9JYtkEJnBZkomKFasGB4mSoEuFhGdPDYBuo3X3oa0kOyLM+0PEwGv/04bNROwO6S+m9b4gSPhrmxmQy08Flj/LZMpeoWHWuUH93NhcZX3wlkYybkWgOxXTSZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OGqooqQ38imejdAFrcURz0xDYJAVNEvSEbBT+EQdIXGMMMyC3hPB9bQE+CbWQVW9pJAlYTWCrQcbt139QFrFGjahJ6YXPK12eAaEoRuA2VyjVf08YoqFXYgr2Dn9k1/ZBjKnVR/qw20Cj5m+u5otJNxwA9BC27PBzJLeV6ZdW20= Received: by 10.78.170.17 with SMTP id s17mr18784304hue.35.1202334883826; Wed, 06 Feb 2008 13:54:43 -0800 (PST) Received: by 10.78.137.9 with HTTP; Wed, 6 Feb 2008 13:54:43 -0800 (PST) Message-ID: <205b7d90802061354g7de45dcbo5c4522dd392c31f6@mail.gmail.com> Date: Wed, 6 Feb 2008 13:54:43 -0800 From: "Tony Nolo" To: "Andrew Storms" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <205b7d90802051909s2ed8b77fo9effef8697b0ca7d@mail.gmail.com> Cc: freebsd-security@freebsd.org Subject: Re: failed binary version 6.2-6.3 update using freebsd-update.sh X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 21:54:46 -0000 rm /var/db/freebsd-update mkdir -p /var/db/freebsd-update sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching public key from update1.FreeBSD.org... done. Fetching metadata signature for 6.2-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. WARNING: This system is running a "MyRouter" kernel, which is not a kernel configuration distributed as part of FreeBSD 6.2-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "freebsd-update.sh install". The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/catpages world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: kernel/smp Does this look reasonable (y/n)? y Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 6.2-RELEASE for merging... done. Preparing to download files... done. Fetching 3928 patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150.. ( ... ) 3780....3790....3800....3810....3820....3830....3840....3850....3860....3870....3880....3890....3900....3910....3920.... done. Applying patches... done. Fetching 2063 files... done. freebsd-update.sh: cannot open files/.gz: No such file or directory ( ... repeat 81 times ... ) freebsd-update.sh: cannot open files/.gz: No such file or directory Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/defaults/periodic.conf Press Enter to edit this file in joe and resolve the conflicts manually... Must be something else? Tony From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 22:01:04 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48FB16A419 for ; Wed, 6 Feb 2008 22:01:04 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from galain.elvandar.org (galain.elvandar.org [217.148.169.56]) by mx1.freebsd.org (Postfix) with ESMTP id 8507B13C45B for ; Wed, 6 Feb 2008 22:01:04 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from evilcoder.xs4all.nl ([195.64.94.120] helo=Inbox) by galain.elvandar.org with esmtpa (Exim 4.67) (envelope-from ) id 1JMrOo-000IEM-2P; Wed, 06 Feb 2008 22:01:42 +0100 MIME-Version: 1.0 From: Remko Lodder Date: Wed, 6 Feb 2008 22:01:41 +0100 Importance: normal X-Priority: 3 To: Mohacsi Janos , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Message-Id: <20080206220104.8507B13C45B@mx1.freebsd.org> Cc: Subject: RE: What about FreeBSD? - KAME Project "ipcomp6_input()" Denial of Service X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 22:01:04 -0000 We are aware and working on resolving this. Thanks Remko Hat: freebsd secteam -----Original Message----- From: "Mohacsi Janos" To: freebsd-security@freebsd.org Sent: 6-2-08 21:54 Subject: What about FreeBSD? - KAME Project "ipcomp6_input()" Denial of Ser= vice=20 TITLE: KAME Project "ipcomp6_input()" Denial of Service CRITICAL: Moderately critical IMPACT: DoS WHERE: >From remote DESCRIPTION: A vulnerability has been reported in the KAME Project, which can be exploited by malicious people to cause a DoS (Denial of Service). The vulnerability is caused due to an error within the "ipcomp6_input()" function in kame/sys/netinet6/ipcomp_input.c when processing IPv6 packets with an IPComp header. This can be exploited to crash a vulnerable system by sending a specially crafted IPv6 packet. SOLUTION: Fixed in the CVS repository. http://www.kame.net/dev/cvsweb2.cgi/kame/kame/sys/netinet6/ipcomp_input.c.d= iff?r1=3D1.36;r2=3D1.37 PROVIDED AND/OR DISCOVERED BY: US-CERT credits Shoichi Sakane. NetBSD credits the Coverity Prevent analysis tool. ORIGINAL ADVISORY: US-CERT VU#110947: http://www.kb.cert.org/vuls/id/110947 _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-security@FreeBSD.ORG Wed Feb 6 22:22:56 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD01A16A417 for ; Wed, 6 Feb 2008 22:22:56 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from mail.ncircle.com (mail.ncircle.com [64.84.9.150]) by mx1.freebsd.org (Postfix) with ESMTP id 9274013C4CC for ; Wed, 6 Feb 2008 22:22:56 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from CORP-MAIL.ad.ncircle.com (corpmail-02.ncircle.com [192.168.75.91]) by mail.ncircle.com (8.13.6/8.13.6) with ESMTP id m16M4JPN098073 for ; Wed, 6 Feb 2008 14:04:20 -0800 (PST) (envelope-from astorms@ncircle.com) Received: from 192.168.75.113 ([192.168.75.113]) by CORP-MAIL.ad.ncircle.com ([192.168.75.94]) with Microsoft Exchange Server HTTP-DAV ; Wed, 6 Feb 2008 22:04:21 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Wed, 06 Feb 2008 14:04:22 -0800 From: Andrew Storms To: Tony Nolo Message-ID: Thread-Topic: failed binary version 6.2-6.3 update using freebsd-update.sh Thread-Index: AchpCuXzmDqlPo1WSWSe2GUBqQbXSwAAVRsb In-Reply-To: <205b7d90802061354g7de45dcbo5c4522dd392c31f6@mail.gmail.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: -4.211 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 64.84.9.150 Cc: "freebsd-security@freebsd.org" Subject: Re: failed binary version 6.2-6.3 update using freebsd-update.sh X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 22:22:56 -0000 Interesting. I'd suggest running with shell 'debugging' via the -x flag: sh -x freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade On 2/6/08 1:54 PM, "Tony Nolo" wrote: > Applying patches... done. > Fetching 2063 files... done. > freebsd-update.sh: cannot open files/.gz: No such file or directory > ( ... repeat 81 times ... ) > freebsd-update.sh: cannot open files/.gz: No such file or directory > Attempting to automatically merge changes in files... done. > > The following file could not be merged automatically: > /etc/defaults/periodic.conf > Press Enter to edit this file in joe and resolve the conflicts > manually... > > > Must be something else? > > Tony From owner-freebsd-security@FreeBSD.ORG Thu Feb 7 01:30:13 2008 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F0D616A417 for ; Thu, 7 Feb 2008 01:30:13 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.freebsd.org (Postfix) with ESMTP id E640713C457 for ; Thu, 7 Feb 2008 01:30:12 +0000 (UTC) (envelope-from tonynolo2@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so2726892wxd.7 for ; Wed, 06 Feb 2008 17:30:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Fuy6kCZ9EuJ/Wp6XwnFoT4ofdIpr7raOFq8keKJffR0=; b=CLBJP+usig60+akoyEKzC8kQz5fq6de7sVgdEQbcGP45WLoktZjL+/XC86eIW1WGoZHYZNkyR/MXNoZHNtnqq0s9gWzXmxOA63ny5bZPJpOcouMXYtMYHaaw0zYrYOHd5TzbkE4YR+E37cDuV2D7DZqzwmZi38bhKeLPdtvGx04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pRYOK1Y20mVg9lvJWZHDu+L4wWlmGa1CEwDKaknWhl70OaHVKmIbub4EH2T4otcDDcrEgP1GwjEqfILjBHXhBDA5VmlSjvgy0X1LH5b2rFsCdC0r2r8mcIfNIPndjm36ekEVXfdY2WaAxHG2sOO1F2s47718ncxCvY5pj0H8MhE= Received: by 10.78.81.20 with SMTP id e20mr19146693hub.60.1202347810457; Wed, 06 Feb 2008 17:30:10 -0800 (PST) Received: by 10.78.137.9 with HTTP; Wed, 6 Feb 2008 17:30:10 -0800 (PST) Message-ID: <205b7d90802061730j9fe4d4n1dc19176c675b0a3@mail.gmail.com> Date: Wed, 6 Feb 2008 17:30:10 -0800 From: "Tony Nolo" To: "Andrew Storms" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <205b7d90802061354g7de45dcbo5c4522dd392c31f6@mail.gmail.com> Cc: freebsd-security@freebsd.org Subject: Re: failed binary version 6.2-6.3 update using freebsd-update.sh X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2008 01:30:13 -0000 Hi Andrew, On Feb 6, 2008 2:04 PM, Andrew Storms wrote: > Interesting. I'd suggest running with shell 'debugging' via the -x flag: > > sh -x freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade I did as suggested; took awhile! Since the output is ~ 550K lines of text, I'll just include a snippet (below) from immediately before & after where those error start occurring; If you need more/other, please let me know. Tony ... + dirname /etc/security/audit_warn + D=/etc/security + mkdir -p merge/old//etc/security + mkdir -p merge/6.2-RELEASE//etc/security + mkdir -p merge/6.3-RELEASE//etc/security + mkdir -p merge/new//etc/security + read F + dirname /etc/services + D=/etc + mkdir -p merge/old//etc + mkdir -p merge/6.2-RELEASE//etc + mkdir -p merge/6.3-RELEASE//etc + mkdir -p merge/new//etc + read F + dirname /etc/snmpd.config + D=/etc + mkdir -p merge/old//etc + mkdir -p merge/6.2-RELEASE//etc + mkdir -p merge/6.3-RELEASE//etc + mkdir -p merge/new//etc + read F + dirname /etc/ttys + D=/etc + mkdir -p merge/old//etc + mkdir -p merge/6.2-RELEASE//etc + mkdir -p merge/6.3-RELEASE//etc + mkdir -p merge/new//etc + read F + read F + + lookcut /etc/defaults/devfs.rules| -f INDEX-PRESENT 7 -d | + V= + gunzip freebsd-update.sh: cannot open files/.gz: No such file or directory + look+ /etc/defaults/devfs.rules|fgrep tomerge-old -q |f| + + lookcut /etc/defaults/devfs.rules| -f tomerge-old 3 -d | + V=902a1ae8a226ddf6758d576051a28747c1f432a32c603df0c206c8e5ccaf7f09 + gunzip + + + cutfgreplook -f -q /etc/defaults/devfs.rules| 1,2,7 |f| INDEX-NEW -d | + read F + look+ /etc/defaults/periodic.conf|cut INDEX-PRESENT -f 7 -d | + V=081e343cd66c19de7ce5196db803b2e3a7eda8a27da712a10ae462119d27fe85 + gunzip + + fgreplook -q /etc/defaults/periodic.conf| |f| tomerge-old + look+ cut /etc/defaults/periodic.conf| -f tomerge-old 3 -d | + V=2c792bb5c6d8b33b37b6ec3d1fa40c94998c874b44a8c2216f80150a32d2d4d1 + gunzip + + + lookcutfgrep /etc/defaults/periodic.conf| -f -q INDEX-NEW 1,2,7 |f| -d | + look+ /etc/defaults/periodic.conf|cut INDEX-NEW -f 7 -d | + V=0e740ac50cf9bda07ddb717ea0d711a30046489ea3a17a7ecc0152788f290490 + gunzip + read F + + lookcut /etc/defaults/rc.conf| -f INDEX-PRESENT 7 -d | + V= + gunzip freebsd-update.sh: cannot open files/.gz: No such file or directory + look+ /etc/defaults/rc.conf|fgrep tomerge-old -q |f| + + lookcut /etc/defaults/rc.conf| -f tomerge-old 3 -d | + V=b8b3f182663c3de46d2cd7c258247dbf8a7fc66fa6086bc75eb8842b24f2f302 + gunzip + + lookcut /etc/defaults/rc.conf|+ -f INDEX-NEWfgrep 1,2,7 -q -d |f| | + read F + look+ /etc/hosts.allow|cut INDEX-PRESENT -f 7 -d | + V= + gunzip freebsd-update.sh: cannot open files/.gz: No such file or directory + + fgreplook -q /etc/hosts.allow| |f| tomerge-old + + lookcut /etc/hosts.allow| -f tomerge-old 3 -d | + V=aa843fcba8f2e7930d3f8594347e2425c6fee1cc6a6ffe9cc982f3cde7f69782 + gunzip + + + cutfgreplook -f -q /etc/hosts.allow| 1,2,7 |f| INDEX-NEW -d | + read F + look+ /etc/mail/freebsd.cf|cut INDEX-PRESENT -f 7 -d | + V=950e38e6ea2dda90b66159339e17522380302bf9548198d20c418fe153aab44d + gunzip + + lookfgrep /etc/mail/freebsd.cf| -q tomerge-old |f| + + lookcut /etc/mail/freebsd.cf| -f tomerge-old 3 -d | + V=479242e8383da9eec36cfc54ed63e2ca1b9c09797549c0c922ce816b91f4d337 + gunzip + + + lookcutfgrep /etc/mail/freebsd.cf| -f -q INDEX-NEW 1,2,7 |f| -d | + look+ /etc/mail/freebsd.cf|cut INDEX-NEW -f 7 -d | + V=3d1ebb70ba720dd1b3653eac0154fa349c753248322010c384cf2f6e0d9c4f8c + gunzip + read F + + lookcut /etc/mail/freebsd.mc| -f INDEX-PRESENT 7 -d | + V= + gunzip freebsd-update.sh: cannot open files/.gz: No such file or directory + look+ /etc/mail/freebsd.mc|fgrep tomerge-old -q |f| + look+ /etc/mail/freebsd.mc|cut tomerge-old -f 3 -d | + V=5d4897a61bb877f7d0c0b9dc690e5abecd7842824f35d6a2e3fa32144a0d9a95 + gunzip + + look+ fgrep /etc/mail/freebsd.mc|cut -q INDEX-NEW -f |f| 1,2,7 -d | + read F + + lookcut /etc/mail/freebsd.submit.cf| -f INDEX-PRESENT 7 -d | + V=4f94200e6fa8e1cf443c73f12b8d6678016cbf0eeb0be5ed755a6065710b4050 + gunzip + + lookfgrep /etc/mail/freebsd.submit.cf| -q tomerge-old |f| ...