Just bumping this question of mine. I tried a "freebsd-update fetch" just
now, but I still have no updates! And my system is still on
6.2-RELEASE-p4. Is that normal or should I be concerned?
$ freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching metadata sig
Jeffrey Goldberg wrote:
But since I'm masochistic, I figure that I should inflict problems
on myself like remembering to update the serial numbers myself. (Big
shouting reminder comments at both ends of the zone files seem to do
the trick)
emacs zone-mode will do it automatically for y
On Wed, 1 Aug 2007, Josh Carroll wrote:
You need wait no longer...the security advisory just went out with a patch:
http://security.freebsd.org/advisories/FreeBSD-SA-07:07.bind.asc
I'm on FreeBSD 6.2-RELEASE-p4. If I do a freebsd-update shouldn't I get
this? Or will there be a delay coz bin
This has probably been asked before,
Heh, no, never. :)
That's a relief. :)
but if BIND is available in ports then why is it also available in
contrib?
Couple of reasons, of relatively equal importance depending on who you
speak to. BSD systems have "always" (I haven't verified this, but
Rakhesh Sasidharan wrote:
> This has probably been asked before,
Heh, no, never. :)
> but if BIND is available in ports then why is it also available in
> contrib?
Couple of reasons, of relatively equal importance depending on who you
speak to. BSD systems have "always" (I haven't verified this
Hi!
Was going through this slightly old thread and wanted to clear somethings
up for myself.
If you want to stay as close as possible to 6.2-RELEASE but also
include the fixes that the security officer deems important enough to
release widely, use the tag RELENG_6_2 (usually in your supfil
Jeffrey Goldberg wrote:
> Yes, I do mean a (low volume) authoritative name server for a small
> handful of low traffic vanity domains. My intention is to set it up as
> a master which will transfer zone information to a professional DNS
> hosting service (dnspark.net whom I'm very happy with).
T
On Aug 1, 2007, at 3:47 PM, Doug Barton wrote:
I can't speak for the security team, but I'm pretty sure that this
change is forthcoming.
As someone has already noted in this thread, the wait is over.
When it comes to BIND stuff in particular, I always update the ports
first, so anyone with a
You need wait no longer...the security advisory just went out with a patch:
http://security.freebsd.org/advisories/FreeBSD-SA-07:07.bind.asc
Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Jeffrey Goldberg wrote:
> On Aug 1, 2007, at 2:13 PM, Doug Barton wrote:
>
>> If you want to stay as close as possible to 6.2-RELEASE but also
>> include the fixes that the security officer deems important enough to
>> release widely, use the tag RELENG_6_2 (usually in your supfile for
>> cvsup or
Jeffrey Goldberg wrote:
> Are there other things in /usr/src/contrib that follow this pattern?
/usr/ports/mail/sendmail
/usr/src/usr.sbin/sendmail
Its very common to install
/usr/ports/security/cyrus-sasl2-saslauthd
add
# SASL (cyrus-sasl v2) sendmail build flags...
SENDMAIL_CFLAGS=-I/usr/local/in
Jeffrey Goldberg wrote:
> Anyway, I was disappointed that the BIND fix didn't make it into
> RELENG_6_2.
Give us a little time. Unless an issue is exceptionally urgent, it
usually takes us about a week to confirm that we're affected, to get
a patch from upstream or create our own, to make sure th
On Aug 1, 2007, at 2:13 PM, Doug Barton wrote:
If you want to stay as close as possible to 6.2-RELEASE but also
include the fixes that the security officer deems important enough to
release widely, use the tag RELENG_6_2 (usually in your supfile for
cvsup or csup). If you want the latest code fo
Jeffrey Goldberg wrote:
> It appears that BIND has only been fixed in -STABLE and -CURRENT, but
> not in -RELEASE. Does anyone know if there are plans to get this
> patched in 6.2?
>
> For me it makes little difference since I am not (yet) running named in
> a publicly accessible way. But my me
On Jul 31, 2007, at 10:05 PM, A.G. Russell IV wrote:
On Thu, Jul 26, 2007 at 10:48:10AM +0200, Zbigniew Szalbot wrote:
On 7/25/07, Doug Barton <[EMAIL PROTECTED]> wrote:
RELENG_6 was updated shortly after the release of 9.3.4. I'll be
updating RELENG_[56] with the new 9.3.4-P1 version after I
if you will look at /usr/src/contrib/bind9/version
your contents will look something like this:
# This file must follow /bin/sh rules. It is imported directly via
# configure.
#
MAJORVER=9
MINORVER=3
PATCHVER=3
RELEASETYPE=
RELEASEVER=
Meaning mine, which was updated a few minutes ago, is still
Hello,
On Thu, 26 Jul 2007 11:36:27 +0300, "Abdullah Ibn Hamad Al-Marri"
<[EMAIL PROTECTED]> wrote:
> On 7/25/07, Doug Barton <[EMAIL PROTECTED]> wrote:
>
>> RELENG_6 was updated shortly after the release of 9.3.4. I'll be
>> updating RELENG_[56] with the new 9.3.4-P1 version after I'm done
>> r
On 7/25/07, Doug Barton <[EMAIL PROTECTED]> wrote:
RELENG_6 was updated shortly after the release of 9.3.4. I'll be
updating RELENG_[56] with the new 9.3.4-P1 version after I'm done
regression testing it, which should be some time tonight. Same for
updating HEAD with 9.4.1-P1.
The ports for bin
Simon L. Nielsen wrote:
> [freebsd-security@ CC'ed to avoid answering the same there again
> shorly :) - if following up, please drop either freebsd-questions or
> freebsd-securiy to avoid "spamming" both lists]
>
> On 2007.07.24 18:15:43 -0500, Jeffrey Goldberg wrote:
>
>> As I'm sure many peopl
[freebsd-security@ CC'ed to avoid answering the same there again
shorly :) - if following up, please drop either freebsd-questions or
freebsd-securiy to avoid "spamming" both lists]
On 2007.07.24 18:15:43 -0500, Jeffrey Goldberg wrote:
> As I'm sure many people know there is a newly discovered BI
[I'm cc'ing this to [EMAIL PROTECTED], but they are probably
already aware of things. I don't require a response from them, but
if they do, a posting to the questions are announcement lists would
be great. I don't need a personal response.]
As I'm sure many people know there is a newly di
21 matches
Mail list logo
