LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Advisory Watch: August 29th, 2014
Linux Security Week: August 25th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Slackware: 'bind' DoS Print E-mail
User Rating:      How can I rate this item?
Posted by LinuxSecurity.com Team   
Slackware BIND version 8.2.2-P5 has a denial of service bug.

BIND version 8.2.2-P5 has a denial of service bug.  The code intended to
provide support for the transfer of compressed zone files can crash the
name server.  More BIND security information can be found at:

    http://www.isc.org/products/BIND/bind8.html

By upgrading to BIND 8.2.2-P7, users can fix this problem.  A new bind.tgz
package is available for users of Slackware Linux 7.0, 7.1, and -current.


 =======================================
 BIND 8.2.2-P7 AVAILABLE - (n1/bind.tgz)
 =======================================

  The denial of service vulnerability that affects BIND 8.2.2-P5 can
  be fixed by upgrading to the new BIND 8.2.2-P7 package.  The new
  bind.tgz is available in the -current branch:

    ftp://ftp.slackware.com/pub/slackware/slackware-current/slakware/n1/bind.tgz

  For verification purposes, we provide the following checksums:

   16-bit "sum" checksum:
   41816  1611   n1/bind.tgz

   128-bit MD5 message digest:
   acce19918ebb3cf0159f0690e5d167ae  n1/bind.tgz


  INSTALLATION INSTRUCTIONS FOR THE bind.tgz PACKAGE:
  ---------------------------------------------------
  Be sure to backup your name server configuration files (/etc/named.conf
  and the /var/named directory) for safe measure.  Then stop the name
  server:

         # ndc stop

  Now run upgradepkg on the new BIND package:

         # upgradepkg bind.tgz

  The name server can now be restarted:

         # ndc start



Remember, it's also a good idea to backup configuration files before
upgrading packages.

- Slackware Linux Security Team
   http://www.slackware.com


 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Weekend Edition
How Cops and Hackers Could Abuse California’s New Phone Kill-Switch Law
Why Russian hackers are beating us
DQ Breach? HQ Says No, But Would it Know?
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.