.. class:: SSLSocket(socket.socket)

SSL sockets provide the following methods of :ref:`socket-objects`:

- :meth:`~socket.socket.accept()`

- :meth:`~socket.socket.bind()`

- :meth:`~socket.socket.close()`

- :meth:`~socket.socket.connect()`

- :meth:`~socket.socket.detach()`

- :meth:`~socket.socket.fileno()`

- :meth:`~socket.socket.getpeername()`, :meth:`~socket.socket.getsockname()`

- :meth:`~socket.socket.getsockopt()`, :meth:`~socket.socket.setsockopt()`

- :meth:`~socket.socket.gettimeout()`, :meth:`~socket.socket.settimeout()`,

:meth:`~socket.socket.setblocking()`

- :meth:`~socket.socket.listen()`

- :meth:`~socket.socket.makefile()`

- :meth:`~socket.socket.recv()`, :meth:`~socket.socket.recv_into()`

(but passing a non-zero ``flags`` argument is not allowed)

- :meth:`~socket.socket.send()`, :meth:`~socket.socket.sendall()` (with

the same limitation)

- :meth:`~socket.socket.shutdown()`

However, since the SSL (and TLS) protocol has its own framing atop

of TCP, the SSL sockets abstraction can, in certain respects, diverge from

the specification of normal, OS-level sockets. See especially the

:ref:`notes on non-blocking sockets <ssl-nonblocking>`.