New submission from Alex Gaynor:
The names are super misleading. First, they're written in a way that's the
opposite of how people think about these things (CLIENT_AUTH -> server socket;
SERVER_AUTH -> client socket). Second, they're misleading, you can have TLS
which is *mutually* authenticated. Third, CLIENT_AUTH is very frequently used
for a server socket where the client isn't authenticated (at the TLS layer) at
all!
A simple fix would be to add: Purpose.{CLIENT,SERVER}_SOCKET and alias the old
names to those values.
----------
messages: 289601
nosy: alex
priority: normal
severity: normal
status: open
title: Rename ssl.Purpose.{CLIENT,SERVER}_AUTH
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29810>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
