Date: Thu, 18 Dec 2014 10:23:43 -0600 From: chris <chris@bsdjunk.com> To: Zoran Kolic <zkolic@sbb.rs> Cc: freebsd-security@freebsd.org, cpet@sdf.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:30.unbound Message-ID: <14a5e364840.d7cf188633233.7838236330435139778@bsdjunk.com> In-Reply-To: <20141218161306.GA21957@knossos> References: <mailman.87.1418904002.80773.freebsd-security@freebsd.org> <20141218161306.GA21957@knossos>
next in thread | previous in thread | raw e-mail | index | archive | help
This is weird as I now get a thing that "Directory's required to be removed ..." and that directory is "/" will this be fixed as this is kinda scary seeing "Directory couldn't be removed "rmdir /////" or something it showed.
---- On Thu, 18 Dec 2014 10:13:07 -0600 zkolic@sbb.rs wrote ---- > The first part of that statement is false. The dns/unbound port was
> fixed for CVE-2014-8602 on 9 December. Thus a valid work around is to
> disable local_unbound and use ports/dns/unbound.
To ask explicitelly: this does not affect 9.3?
I see no unbound nor local_unbound on stock install.
Best regards
Zoran
_______________________________________________
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 Thu Dec 18 16:40:21 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 8A293AA5
for <freebsd-security@freebsd.org>; Thu, 18 Dec 2014 16:40:21 +0000 (UTC)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
[209.85.212.170])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(Client CN "smtp.gmail.com",
Issuer "Google Internet Authority G2" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 1E84A166B
for <freebsd-security@freebsd.org>; Thu, 18 Dec 2014 16:40:20 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id bs8so2169369wib.5
for <freebsd-security@freebsd.org>; Thu, 18 Dec 2014 08:40:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=+EHgC/9aFOxx/UZD8co0tBK/h5qnE5H1U3lYEBGeUC4=;
b=RwzMqnhBicgGE9fjVr+B50mLAle2/n8fTdA33LzxNMx65DCbVCM5E5E7hQQUeveh7s
2gjl4keCVOz8MwMfRtsTyDhRCo/HBvPGFyGyFvaCqTb59y4BY8G8BKSM9foimGLVF+dh
UCWsJpJeQNh7cGrQbOaB6QOHr0RqffPE1cybg3by/4ZjEj/E5HJrsTM/XYoRG0gJIeQB
iYOS/4mWkGCGI749duQmCzZHkgBe6/K2kMc4rsUoB0KkSomBhTATqaenc8tvD0WQEW6r
1p/CLmva6AIC3cmfP6LCrO97K6AyYsxLt0I21VeJG1o2oB0YPRnRJ4jhN2LZRdnmH+cJ
NmPA==
X-Gm-Message-State: ALoCoQnElODyG4YUDgQUJLT5YQ84y5E2n62jxXO7BAiwkFU5/n0P+tJXccS9q0wtkxHhgLQsVvEQ
X-Received: by 10.180.103.6 with SMTP id fs6mr25530914wib.11.1418920812434;
Thu, 18 Dec 2014 08:40:12 -0800 (PST)
Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk.
[82.69.141.170])
by mx.google.com with ESMTPSA id r3sm25372262wic.10.2014.12.18.08.40.11
for <freebsd-security@freebsd.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 18 Dec 2014 08:40:11 -0800 (PST)
Message-ID: <5493034B.7020102@multiplay.co.uk>
Date: Thu, 18 Dec 2014 16:39:39 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:30.unbound
References: <mailman.87.1418904002.80773.freebsd-security@freebsd.org>
<20141218161306.GA21957@knossos>
In-Reply-To: <20141218161306.GA21957@knossos>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>,
<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>;
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 16:40:21 -0000
Nope unbound was the replacement for bind in 10.x+
On 18/12/2014 16:13, Zoran Kolic wrote:
>> The first part of that statement is false. The dns/unbound port was
>> fixed for CVE-2014-8602 on 9 December. Thus a valid work around is to
>> disable local_unbound and use ports/dns/unbound.
> To ask explicitelly: this does not affect 9.3?
> I see no unbound nor local_unbound on stock install.
> Best regards
>
> Zoran
>
> _______________________________________________
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14a5e364840.d7cf188633233.7838236330435139778>