[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ProgSoc] debian potato and Bind9



On Monday 26 June 2006 2:57 pm, Michael Brown wrote:
 ] Only problem is, the machine on which I need to install bind used to point
 ] to an internal debian mirror that the last mob that were here took away with
 ] them.

 So many solutions ...

 The last mob should be consulted, in the first instance.

 Can you run both machines in parallel, with the extant potato
 box continuing to do whatever it is that it does, and the old
 firewall becoming 'the DNS box', and the firewall being put in
 place (also in parallel)?  If you're looking for a stop-gap measure
 to only last a couple of months, this seems the easiest way.

 ] The machine I want to install bind on is running debian potato. I've tried
 ] pointing the apt source list at a few sites now with no love.

 Be sure to describe errors in the vaguest possible way.  Don't ever
 cut and paste error messages, as that removes ambiguity.

 ] There might also be an issue with the firewall possibly blocking my
 ] attempts.

 Hmm .. it's more likely because potato has been well and truly
 obsoleted.  Security updates would have stopped coming out
 around the middle of 2003.  This means that you may well be
 exposed to any number of bind vulnerabilities that have cropped
 up since that time.

 Nice.

 Now, you don't want to 'just download bind as a deb file' -- because
 you're [probably] not going to be able to find a backport that'll fit.

 What you probably need to do is upgrade the machine to something
 a bit more recent.  This is painfully simple to do (mod sources.list,
 apt-get update, apt-get dist-upgrade).  It is infinitely easier than:

 ] I tried to install it from source but there is no compiler on the
 ] system and without apt working it's kinda hard to install one.

 I'd be pretty concerned about the fact that your company's
 DNS box hasn't been (can't have been) patched for 3 years.

 Jedd.


-
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to progsoc-request@xxxxxxxxxxxxxxxxxxx
If you are having trouble, ask owner-progsoc@xxxxxxxxxxxxxxxxxx for help.