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

Accepted haproxy 1.8.13-2~bpo8+1 (source amd64 all) into jessie-backports-sloppy



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 19 Sep 2018 23:08:02 +0300
Source: haproxy
Binary: haproxy haproxy-dbg haproxy-doc vim-haproxy
Architecture: source amd64 all
Version: 1.8.13-2~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: high
Maintainer: Debian HAProxy Maintainers <haproxy@tracker.debian.org>
Changed-By: Apollon Oikonomopoulos <apoikos@debian.org>
Description:
 haproxy    - fast and reliable load balancing reverse proxy
 haproxy-dbg - fast and reliable load balancing reverse proxy (debug symbols)
 haproxy-doc - fast and reliable load balancing reverse proxy (HTML documentatio
 vim-haproxy - syntax highlighting for HAProxy configuration files
Changes:
 haproxy (1.8.13-2~bpo8+1) jessie-backports-sloppy; urgency=medium
 .
   * Rebuild for jessie-backports-sloppy
 .
 haproxy (1.8.13-2) unstable; urgency=high
 .
   * Fix improper sign check on the HPACK header index value (CVE-2018-14645)
   * Bump Standards-Version to 4.2.1; no changes needed
 .
 haproxy (1.8.13-1) unstable; urgency=medium
 .
   * New upstream version.
     - BUG/MEDIUM: h2: don't accept new streams if conn_streams are still
                   in excess
     - BUG/MEDIUM: h2: make sure the last stream closes the connection
                   after a timeout
     - BUG/MEDIUM: h2: never leave pending data in the output buffer on close
     - BUG/MEDIUM: h2: prevent orphaned streams from blocking a connection
                   forever
     - BUG/MEDIUM: stats: don't ask for more data as long as we're responding
     - BUG/MEDIUM: stream-int: don't immediately enable reading when the
                   buffer was reportedly full
     - BUG/MEDIUM: threads/sync: use sched_yield when available
     - BUG/MEDIUM: threads: Fix the exit condition of the thread barrier
     - BUG/MEDIUM: threads: properly fix nbthreads == MAX_THREADS
     - BUG/MEDIUM: threads: unbreak "bind" referencing an incorrect thread
                   number
   * d/patches: drop systemd exit status patch (applied upstream).
Checksums-Sha1:
 2c9fdaa481cb2e2c2e8d90ffa55aea92add9feeb 2326 haproxy_1.8.13-2~bpo8+1.dsc
 2888dc396b34949ada180437d442e170ee7601dc 67660 haproxy_1.8.13-2~bpo8+1.debian.tar.xz
 e3d88717b5a6e8674b5804872943b7b64e980060 1285630 haproxy_1.8.13-2~bpo8+1_amd64.deb
 321c9b2d7b3f0e65f7021cd93bf38d4f2612a184 3211898 haproxy-dbg_1.8.13-2~bpo8+1_amd64.deb
 89c979e07f904df2bc08e354707e8e33feb96c0a 523600 haproxy-doc_1.8.13-2~bpo8+1_all.deb
 7a93c003dd065d59ca4c0d471bdfc8943b4447d9 173376 vim-haproxy_1.8.13-2~bpo8+1_all.deb
Checksums-Sha256:
 6b2c605580854714e38d31bcdf057a75cdc68f2bfd22ce23d864b4d981075497 2326 haproxy_1.8.13-2~bpo8+1.dsc
 1dd5fa3e9b9dc2d9128c5100551e93ff3faa87650ae21adb4802bbe4bb2c9085 67660 haproxy_1.8.13-2~bpo8+1.debian.tar.xz
 33083ede70643878464fae98b91f249d0cbdb9ace91cfca1ccd8828d771c8f05 1285630 haproxy_1.8.13-2~bpo8+1_amd64.deb
 d5ce4e3325346cf59160fee598fae33b447bbd0493b7907cf09508cc58127b09 3211898 haproxy-dbg_1.8.13-2~bpo8+1_amd64.deb
 d07292c094f41d94ea219a38f92eb286ff8222703e05cdd953327062eec6bbe0 523600 haproxy-doc_1.8.13-2~bpo8+1_all.deb
 6f18963ff81e39c29acae6b25c0e618a9a2e06fefdf16f452d3d34a27663fcf7 173376 vim-haproxy_1.8.13-2~bpo8+1_all.deb
Files:
 2dc96929efbf32b70f8c6e72b3c98f04 2326 net optional haproxy_1.8.13-2~bpo8+1.dsc
 4ec48b86ee53f9475aa6fb496bdde1a2 67660 net optional haproxy_1.8.13-2~bpo8+1.debian.tar.xz
 c22e83a5b699bbf2643bde173d7656f5 1285630 net optional haproxy_1.8.13-2~bpo8+1_amd64.deb
 0a95e0302c0e71b70b909d9a1111f14b 3211898 debug extra haproxy-dbg_1.8.13-2~bpo8+1_amd64.deb
 5af1300172c7eed8234cf50f6ab15699 523600 doc optional haproxy-doc_1.8.13-2~bpo8+1_all.deb
 67b342057116f4802a7987659aa0f2f3 173376 net optional vim-haproxy_1.8.13-2~bpo8+1_all.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAlujoqAACgkQ9RsYxyAk
giS0Lg//YhJMHtdtuvBp+ITcdAZWWRCqNM8w5bp2mJHnSB186Qvb1g0oPV8pboxB
pu2tL0LCBHWRTL8bUid1rHmCbu3CACrcUuqizy9j4hXFOwbhNE60UJdgBcA46CjX
e9j++2Tv3o5+0s3jBm2Q3o2TuduViUd51ADiyl6nJQbZMcxFWYNnTYyJMpyI5QIl
97U7Zn0KGVBe0EJuCOtZHZwXmmL3ePh9o4WDLYBWfOBdwoiQrxsgo1qLSK1qGZ8s
BFibUZFd2A8r5sy3ey/AS52QTbJZcGHoJozpvSGtEgaRcbctBIi1wzkX04/g8F86
WPsQgBaUB0IhCvlxYy0CupZ5F58qWocl1o3+3+IlqKHk0AUi+6YzpxLNu9AJokqm
EJLxQSzSGmapOm1QS4hDH6ARpr8CBECCWExox1IIqJECqBwdpmULdhikzWJwtVE9
qZ31gqB94Pj127zwEjGvOmipEI9+tB/101yGTnQbfRSVS7QhjWpPSQRzRNypzNgn
0tCNJWv3OplrcZSU2FxVN0HHV4sehfbaw5PxwLevIYzFZVEC0Y76oVAE7Us+TAgB
Q5y9NsRr/9062+5v6og0ToV3Uf3XmoxV0wV+Yj0+x4cwdLYqD4IZMGIOHiO++WrZ
++VtL3/ZJqO+1AWyqrTHEtmRB/MQiHZFS1YnfXzgOxtYsP0E3Bs=
=9dk9
-----END PGP SIGNATURE-----


Reply to: