Jump to content

slaughters_1

Members
 View Profile  See their activity

  • Content Count

    213

  • Joined

  • Last visited

Posts posted by slaughters_1

  8. Posted · Report reply

    Red Hat Network has determined that the following advisory is applicable to
    one or more of the systems you have registered:

    Complete information about this errata can be found at the following location:
    https://rhn.redhat.com/rhn/errata/details/Details.do?eid=8359

    Security Advisory - RHSA-2009:0331-14
    ------------------------------------------------------------------------------
    Summary:
    Important: kernel security and bug fix update

    Updated kernel packages that resolve several security issues and fix
    various bugs are now available for Red Hat Enterprise Linux 4.

    This update has been rated as having important security impact by the Red
    Hat Security Response Team.

    Description:
    The kernel packages contain the Linux kernel, the core of any Linux
    operating system.

    This update addresses the following security issues:

    * a buffer overflow was found in the Linux kernel Partial Reliable Stream
    Control Transmission Protocol (PR-SCTP) implementation. This could,
    potentially, lead to a denial of service if a Forward-TSN chunk is received
    with a large stream ID. (CVE-2009-0065, Important)

    * a memory leak was found in keyctl handling. A local, unprivileged user
    could use this flaw to deplete kernel memory, eventually leading to a
    denial of service. (CVE-2009-0031, Important)

    * a deficiency was found in the Remote BIOS Update (RBU) driver for Dell
    systems. This could allow a local, unprivileged user to cause a denial of
    service by reading zero bytes from the image_type or packet_size file in
    "/sys/devices/platform/dell_rbu/". (CVE-2009-0322, Important)

    * a deficiency was found in the libATA implementation. This could,
    potentially, lead to a denial of service. Note: by default, "/dev/sg*"
    devices are accessible only to the root user. (CVE-2008-5700, Low)

    This update also fixes the following bugs:

    * when the hypervisor changed a page table entry (pte) mapping from
    read-only to writable via a make_writable hypercall, accessing the changed
    page immediately following the change caused a spurious page fault. When
    trying to install a para-virtualized Red Hat Enterprise Linux 4 guest on a
    Red Hat Enterprise Linux 5.3 dom0 host, this fault crashed the installer
    with a kernel backtrace. With this update, the "spurious" page fault is
    handled properly. (BZ#483748)

    * net_rx_action could detect its cpu poll_list as non-empty, but have that
    same list reduced to empty by the poll_napi path. This resulted in garbage
    data being returned when net_rx_action calls list_entry, which subsequently
    resulted in several possible crash conditions. The race condition in the
    network code which caused this has been fixed. (BZ#475970, BZ#479681 &
    BZ#480741)

    * a misplaced memory barrier at unlock_buffer() could lead to a concurrent
    h_refcounter update which produced a reference counter leak and, later, a
    double free in ext3_xattr_release_block(). Consequent to the double free,
    ext3 reported an error

    ext3_free_blocks_sb: bit already cleared for block [block number]

    and mounted itself as read-only. With this update, the memory barrier is
    now placed before the buffer head lock bit, forcing the write order and
    preventing the double free. (BZ#476533)

    * when the iptables module was unloaded, it was assumed the correct entry
    for removal had been found if "wrapper->ops->pf" matched the value passed
    in by "reg->pf". If several ops ranges were registered against the same
    protocol family, however, (which was likely if you had both ip_conntrack
    and ip_contrack_* loaded) this assumption could lead to NULL list pointers
    and cause a kernel panic. With this update, "wrapper->ops" is matched to
    pointer values "reg", which ensures the correct entry is removed and
    results in no NULL list pointers. (BZ#477147)

    * when the pidmap page (used for tracking process ids, pids) incremented to
    an even page (ie the second, fourth, sixth, etc. pidmap page), the
    alloc_pidmap() routine skipped the page. This resulted in "holes" in the
    allocated pids. For example, after pid 32767, you would expect 32768 to be
    allocated. If the page skipping behavior presented, however, the pid
    allocated after 32767 was 65536. With this update, alloc_pidmap() no longer
    skips alternate pidmap pages and allocated pid holes no longer occur. This
    fix also corrects an error which allowed pid_max to be set higher than the
    pid_max limit has been corrected. (BZ#479182)

    All Red Hat Enterprise Linux 4 users should upgrade to these updated
    packages, which contain backported patches to resolve these issues. The
    system must be rebooted for this update to take effect.

    References:
    http://www.redhat.com/security/updates/classification/#important
    ------------------------------------------------------------------------------

    -------------
    Taking Action
    -------------
    You may address the issues outlined in this advisory in two ways:

    - select your server name by clicking on its name from the list
    available at the following location, and then schedule an
    errata update for it:
    https://rhn.redhat.com/rhn/systems/SystemList.do

    - run the Update Agent on each affected server.


    ---------------------------------
    Changing Notification Preferences
    ---------------------------------
    To enable/disable your Errata Alert preferences globally please log in to RHN
    and navigate from "Your RHN" / "Your Account" to the "Preferences" tab.

    URL: https://rhn.redhat.com/rhn/account/UserPreferences.do

    You can also enable/disable notification on a per system basis by selecting an
    individual system from the "Systems List". From the individual system view
    click the "Details" tab.


    ---------------------
    Affected Systems List
    ---------------------
    This Errata Advisory may apply to the systems listed below. If you know that
    this errata does not apply to a system listed, it might be possible that the
    package profile for that server is out of date. In that case you should refresh
    the system's package profile by running *one* of the following commands as root
    on that system:

    * 'up2date -p' (on Enterprise Linux systems prior to RHEL5)
    * 'rhn-profile-sync' (on Enterprise Linux 5 or later)

    There is 1 affected system registered in 'Your RHN' (only systems for
    which you have explicitly enabled Errata Alerts are shown).

  11. Posted · Report reply

    Debian





    From Wikipedia, the free encyclopedia

    Debian (pronounced /ˈdɛbiən/) GNU/Linux is one of the most popular and influential[3] computer operating systems composed of free and open source software. Debian is known for strict adherence to the Unix and free software philosophies as well as using collaborative software development and testing processes.[4] Debian can be used as a desktop as well as server operating system.

    The Debian Project is governed by the Debian Constitution and the Social Contract which set out the governance structure of the project as well as explicitly stating that the goal of the project is the development of a free operating system.[5][6] Debian is developed by over one thousand volunteers from around the world and supported by donations through SPI,[7] a non-profit umbrella organization for various free software projects.[8]

    Thus, the Debian Project is an independent decentralized organization; it is not backed by a company like other Linux distributions such as Ubuntu, openSUSE, Fedora, and Mandriva. The cost of developing Debian 4.0 etch, assuming paid programmers from a single organization and based on source lines of code, has been estimated to be close to US$13,000,000,000.[9]

    Many distributions are based on Debian, including Ubuntu, MEPIS, Dreamlinux, Damn Small Linux, Xandros, Knoppix, Linspire, sidux, Kanotix, Parsix and LinEx, among others.[10]

    Debian is also known for an abundance of options. The current stable release includes over twenty five thousand software packages for twelve[11] computer architectures. These architectures range from the Intel/AMD 32-bit/64-bit architectures commonly found in personal computers to the ARM architecture commonly found in embedded systems and the IBM eServer zSeries mainframes.[12] Prominent features of Debian are the APT package management system, repositories with large numbers of packages, strict policies regarding packages, and the high quality of releases.[10] These practices allow easy upgrades between releases as well as automated installation and removal of packages.

    The Debian standard install makes use of the GNOME desktop environment. It includes popular programs such as OpenOffice.org, Iceweasel (a rebranding of Firefox), Evolution mail, CD/DVD writing programs, music and video players, image viewers and editors, and PDF viewers. There are pre-built CD images for KDE, Xfce and LXDE as well.[13] The remaining discs, which span five DVDs or over thirty CDs, contain all packages currently available and are not necessary for a standard install. Another install method is via a net install CD which is much smaller than a normal install CD/DVD. It contains only the bare essentials needed to start the installer and downloads the packages selected during installation via APT.[14] These CD/DVD images can be freely obtained by web download, BitTorrent, jigdo or buying them from online retailers.[15]

    source : http://en.wikipedia.org/wiki/Debian

  12. Posted · Report reply

    BSD = Berkeley Software Distribution

    From Wikipedia, the free encyclopedia

    "BSD" redirects here. For other uses, see BSD (disambiguation).

    Berkeley Software Distribution (BSD, sometimes called Berkeley Unix) is the Unix operating system derivative developed and distributed by the Computer Systems Research Group of the University of California, Berkeley, from 1977 to 1995.

    Historically, BSD has been considered a branch of UNIX — "BSD UNIX", because it shared the initial codebase and design with the original AT&T UNIX operating system. In the 1980s, BSD was widely adopted by vendors of workstation-class systems in the form of proprietary UNIX variants such as DEC ULTRIX and Sun Microsystems SunOS. This can be attributed to the ease with which it could be licensed, and the familiarity it found among the founders of many technology companies of this era.

    Though these commercial BSD derivatives were largely superseded by the UNIX System V Release 4 and OSF/1 systems in the 1990s (both of which incorporated BSD code), later BSD releases provided a basis for several open source development projects which continue to this day.

    Today, the term of "BSD" is often non-specifically used to refer to any of these BSD descendants, e.g. FreeBSD, NetBSD or OpenBSD, which together form a branch of the family of Unix-like operating systems.

    link : BSD Wiki

  14. Posted · Report reply

    Apa itu load balancer ?


    In computer networking, load balancing is a technique to spread work between two or more computers, network links, CPUs, hard drives, or other resources, in order to get optimal resource utilization, maximize throughput, and minimize response time. Using multiple components with load balancing, instead of a single component, may increase reliability through redundancy. The balancing service is usually provided by a dedicated program or hardware device (such as a multilayer switch).

    It is commonly used to mediate internal communications in computer clusters, especially high-availability clusters.


    source : [url=http://en.wikipedia.org/wiki/Load_balancing_(computing)]wiki[/url]

    flash tutorial bagaimana load balancer berfungsi.

    http://www.f5.com/flash/product-demo/

    boleh google lebih lagi pasal load balancing..

    http://www.google.com.my/search?hl=en&q=load+balancing&btnG=Google+Search&meta=

    bagaimana load balancer berfungsi dari site cisco..

    http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094820.shtml

    linux load balancing info

    http://en.wikipedia.org/wiki/Linux_Virtual_Server

    contoh diagram load balancing.



    ada persoalan boleh tanya disini.

  15. Posted · Report reply

    Linux Virtual Server
    From Wikipedia, the free encyclopedia



    Linux Virtual Server (LVS) is an advanced load balancing solution for Linux systems. It is an open source project started by Wensong Zhang in May 1998. The mission of the project is to build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.

    The major work of the LVS project is now to develop advanced IP load balancing software (IPVS), application-level load balancing software (KTCPVS), and cluster management components.

    * IPVS: is an advanced IP load balancing software implemented inside the Linux kernel. The IP Virtual Server code was already included into the standard Linux kernel 2.4 and 2.6.
    * KTCPVS: implements application-level load balancing inside the Linux kernel, currently under development.

    Users can use the LVS solutions to build highly scalable and highly available network services, such as web, email, media services and VoIP services, and integrate scalable network services into large-scale reliable e-commerce or e-government applications.

    The LVS solutions have already been deployed in many real applications throughout the world, including Wikipedia.

    source : http://en.wikipedia.org/wiki/Linux_Virtual_Server
×
×
  • Create New...