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

Bug#747481: ITP: backports.ssl-match-hostname -- Backport of the Python 3.2 SSL hostname checking function

* Nicolas Dandrimont <olasd@debian.org> [2014-05-09 10:34:09 +0200]:

> Package: wnpp
> Severity: wishlist
> Owner: Nicolas Dandrimont <olasd@debian.org>
> * Package name    : backports.ssl-match-hostname
>   Version         :
>   Upstream Author : Brandon Craig Rhodes
> * URL             : https://bitbucket.org/brandon/backports.ssl_match_hostname
> * License         : Python
>   Programming Lang: Python
>   Description     : Backport of the Python 3.2 SSL hostname checking function
>  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 a backport of the ssl.match_hostname function for
>  Python 2.4 and above.

On IRC, Jakub kindly pointed me at #626539 and its resolution. As a recent
update of a package I maintain (websocket-client) actually needs this backport,
and I'll need to use it on wheezy (and therefore have to backport the
backport), I'll go ahead and package that anyway.

Nicolas Dandrimont

Microsoft is not the answer.
Microsoft is the question.
NO (or Linux) is the answer.
(Taken from a .signature from someone from the UK, source unknown)

Attachment: signature.asc
Description: Digital signature

Reply to: