---
- branch: MAIN
  date: Mon Jan 27 19:53:30 UTC 2014
  files:
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/py-backports.ssl_match_hostname/DESCR
    pathrev: pkgsrc/security/py-backports.ssl_match_hostname/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/py-backports.ssl_match_hostname/Makefile
    pathrev: pkgsrc/security/py-backports.ssl_match_hostname/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/py-backports.ssl_match_hostname/PLIST
    pathrev: pkgsrc/security/py-backports.ssl_match_hostname/PLIST@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/py-backports.ssl_match_hostname/distinfo
    pathrev: pkgsrc/security/py-backports.ssl_match_hostname/distinfo@1.1
    type: added
  id: 20140127T195330Z.004e12f50d620a2a81dc93f17249e96612f4f36b
  log: |
    Import py27-backports.ssl_match_hostname-3.4.0.2 as
    security/py-backports.ssl_match_hostname.

    The Secure Sockets layer is only actually secure if you check the
    hostname in the certificate returned by the server to which you
    are connecting, and verify that it matches to hostname that you
    are trying to reach.

    But the matching logic, defined in RFC2818, can be a bit tricky to
    implement on your own. So the ssl package in the Standard Library
    of Python 3.2 and greater now includes a match_hostname() function
    for performing this check instead of requiring every application
    to implement the check separately.

    This package contains the backport of this functionality to Python 2.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/security/py-backports.ssl_match_hostname'
  unixtime: '1390852410'
  user: wiz