=========================================
Thu,  20 Nov 2003 - Debian 3.0r2 released
=========================================

stable/non-US/main/binary-sparc/python-pgsql_2.0-3.2_sparc.deb
stable/non-US/main/binary-sparc/python2.1-pgsql_2.0-3.2_sparc.deb
stable/non-US/main/binary-sparc/python2.2-pgsql_2.0-3.2_sparc.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-s390/python2.1-pgsql_2.0-3.2_s390.deb
stable/non-US/main/binary-s390/python-pgsql_2.0-3.2_s390.deb
stable/non-US/main/binary-s390/python2.2-pgsql_2.0-3.2_s390.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-powerpc/python2.1-pgsql_2.0-3.2_powerpc.deb
stable/non-US/main/binary-powerpc/python-pgsql_2.0-3.2_powerpc.deb
stable/non-US/main/binary-powerpc/python2.2-pgsql_2.0-3.2_powerpc.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-mipsel/python-pgsql_2.0-3.2_mipsel.deb
stable/non-US/main/binary-mipsel/python2.2-pgsql_2.0-3.2_mipsel.deb
stable/non-US/main/binary-mipsel/python2.1-pgsql_2.0-3.2_mipsel.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-mips/python2.2-pgsql_2.0-3.2_mips.deb
stable/non-US/main/binary-mips/python-pgsql_2.0-3.2_mips.deb
stable/non-US/main/binary-mips/python2.1-pgsql_2.0-3.2_mips.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-m68k/python2.2-pgsql_2.0-3.2_m68k.deb
stable/non-US/main/binary-m68k/python2.1-pgsql_2.0-3.2_m68k.deb
stable/non-US/main/binary-m68k/python-pgsql_2.0-3.2_m68k.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-ia64/python2.2-pgsql_2.0-3.2_ia64.deb
stable/non-US/main/binary-ia64/python2.1-pgsql_2.0-3.2_ia64.deb
stable/non-US/main/binary-ia64/python-pgsql_2.0-3.2_ia64.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-hppa/python-pgsql_2.0-3.2_hppa.deb
stable/non-US/main/binary-hppa/python2.1-pgsql_2.0-3.2_hppa.deb
stable/non-US/main/binary-hppa/python2.2-pgsql_2.0-3.2_hppa.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-arm/python-pgsql_2.0-3.2_arm.deb
stable/non-US/main/binary-arm/python2.2-pgsql_2.0-3.2_arm.deb
stable/non-US/main/binary-arm/python2.1-pgsql_2.0-3.2_arm.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-alpha/python2.1-pgsql_2.0-3.2_alpha.deb
stable/non-US/main/binary-alpha/python2.2-pgsql_2.0-3.2_alpha.deb
stable/non-US/main/binary-alpha/python-pgsql_2.0-3.2_alpha.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-i386/python2.1-pgsql_2.0-3.2_i386.deb
stable/non-US/main/source/python-pgsql_2.0-3.2.dsc
stable/non-US/main/source/python-pgsql_2.0-3.2.diff.gz
stable/non-US/main/binary-i386/python2.2-pgsql_2.0-3.2_i386.deb
stable/non-US/main/binary-i386/python-pgsql_2.0-3.2_i386.deb
python-pgsql (2.0-3.2) stable; urgency=high
  * When calculating how much memory to allocate for the new string in
    libPQquoteBytea():
      - Do not recalculate the string length using strlen().  We already
        have the string length stored in slen, and since the string may
        contain null bytes, using strlen() may return incorrect results.
        This in turn can lead to the unexpected truncation of binary data
        and subsequent data loss.
      - Allocate up to 5 bytes per character (not 4).  Each null byte in
        the original string is converted to '\\000', and so allocating just
        4 bytes per character can lead to a segfault if the input string
        contains lots of null bytes.
    These patches are taken directly from upstream CVS and are already
    incorporated into newer upstream releases.
    Closes: #204342


stable/non-US/main/binary-sparc/libpam-pgsql_0.5.2-3woody1_sparc.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-s390/libpam-pgsql_0.5.2-3woody1_s390.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-powerpc/libpam-pgsql_0.5.2-3woody1_powerpc.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-mipsel/libpam-pgsql_0.5.2-3woody1_mipsel.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-mips/libpam-pgsql_0.5.2-3woody1_mips.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-m68k/libpam-pgsql_0.5.2-3woody1_m68k.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-ia64/libpam-pgsql_0.5.2-3woody1_ia64.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-hppa/libpam-pgsql_0.5.2-3woody1_hppa.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-arm/libpam-pgsql_0.5.2-3woody1_arm.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-alpha/libpam-pgsql_0.5.2-3woody1_alpha.deb
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/source/pam-pgsql_0.5.2-3woody1.diff.gz
stable/non-US/main/binary-i386/libpam-pgsql_0.5.2-3woody1_i386.deb
stable/non-US/main/source/pam-pgsql_0.5.2-3woody1.dsc
pam-pgsql (0.5.2-3woody1) stable-security; urgency=high
  * Security fix in logging function handles format string vulnerability.
    Thanks to Florian Zumbiehl for pointing this out. (CAN-2003-0672)


stable/non-US/main/binary-powerpc/libssl095a_0.9.5a-6.woody.3_powerpc.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-mipsel/libssl095a_0.9.5a-6.woody.3_mipsel.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-mips/libssl095a_0.9.5a-6.woody.3_mips.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-m68k/libssl095a_0.9.5a-6.woody.3_m68k.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-i386/libssl095a_0.9.5a-6.woody.3_i386.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-arm/libssl095a_0.9.5a-6.woody.3_arm.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-alpha/libssl095a_0.9.5a-6.woody.3_alpha.deb
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/source/openssl095_0.9.5a-6.woody.3.dsc
stable/non-US/main/binary-sparc/libssl095a_0.9.5a-6.woody.3_sparc.deb
stable/non-US/main/source/openssl095_0.9.5a-6.woody.3.diff.gz
openssl095 (0.9.5a-6.woody.3) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Applied upstream patch by Steve Henson from the upstream CVS
    http://cvs.openssl.org/chngview?cn=11470 (CAN-2003-0544,
    CAN-2003-0543, crypto/x509/x509_vfy.c, crypto/asn1/asn1_lib.c)


stable/non-US/main/binary-sparc/kdelibs3-crypto_2.2.2-6woody2_sparc.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-s390/kdelibs3-crypto_2.2.2-6woody2_s390.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-powerpc/kdelibs3-crypto_2.2.2-6woody2_powerpc.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-mipsel/kdelibs3-crypto_2.2.2-6woody2_mipsel.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-mips/kdelibs3-crypto_2.2.2-6woody2_mips.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-m68k/kdelibs3-crypto_2.2.2-6woody2_m68k.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-ia64/kdelibs3-crypto_2.2.2-6woody2_ia64.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-hppa/kdelibs3-crypto_2.2.2-6woody2_hppa.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-arm/kdelibs3-crypto_2.2.2-6woody2_arm.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-alpha/kdelibs3-crypto_2.2.2-6woody2_alpha.deb
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-i386/kdelibs3-crypto_2.2.2-6woody2_i386.deb
stable/non-US/main/source/kdelibs-crypto_2.2.2-6woody2.diff.gz
stable/non-US/main/source/kdelibs-crypto_2.2.2-6woody2.dsc
kdelibs-crypto (4:2.2.2-6woody2) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Update config.guess and config.sub to fix build on mips, mipsel


stable/non-US/main/binary-sparc/exim-tls_3.35-3woody1_sparc.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-s390/exim-tls_3.35-3woody1_s390.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-powerpc/exim-tls_3.35-3woody1_powerpc.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-mipsel/exim-tls_3.35-3woody1_mipsel.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-mips/exim-tls_3.35-3woody1_mips.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-m68k/exim-tls_3.35-3woody1_m68k.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-ia64/exim-tls_3.35-3woody1_ia64.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-hppa/exim-tls_3.35-3woody1_hppa.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-arm/exim-tls_3.35-3woody1_arm.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/binary-alpha/exim-tls_3.35-3woody1_alpha.deb
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


stable/non-US/main/source/exim-tls_3.35-3woody1.dsc
stable/non-US/main/binary-i386/exim-tls_3.35-3woody1_i386.deb
stable/non-US/main/source/exim-tls_3.35-3woody1.diff.gz
exim-tls (3.35-3woody1) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Fix buffer overflow in HELO/EHLO processing (CAN-2003-0698)
    Probably could not be used to execute arbitrary code


=========================================
Sun,  15 Dec 2002 - Debian 3.0r1 released
=========================================

Removed the following packages from stable:

 libgnupg-perl |      0.9-1 | source, all
 (Reason: requested by Stable Release Manager)
   "Moved to ftp-master."

----
	        
stable/non-US/main/binary-sparc/freeswan_1.96-1.4_sparc.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-s390/freeswan_1.96-1.4_s390.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-powerpc/freeswan_1.96-1.4_powerpc.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-mips/freeswan_1.96-1.4_mips.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-m68k/freeswan_1.96-1.4_m68k.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-ia64/freeswan_1.96-1.4_ia64.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-i386/freeswan_1.96-1.4_i386.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-hppa/freeswan_1.96-1.4_hppa.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-arm/freeswan_1.96-1.4_arm.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/binary-alpha/freeswan_1.96-1.4_alpha.deb
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*


stable/non-US/main/source/freeswan_1.96-1.4.dsc
stable/non-US/main/binary-all/kernel-patch-freeswan_1.96-1.4_all.deb
stable/non-US/main/binary-mipsel/freeswan_1.96-1.4_mipsel.deb
stable/non-US/main/source/freeswan_1.96-1.4.diff.gz
freeswan (1.96-1.4) stable-security; urgency=high
  * Non-maintainer upload by the Security Team
  * Second injection into the security build network since 8 buildds
    refuse to upload the binary packages and the maintainer refuses to
    answer.  *sigh*

=========================================
Sat,  20 Jul 2002 - Debian 3.0r0 released
=========================================