File: //usr/lib/python3/dist-packages/twisted/mail/__pycache__/interfaces.cpython-310.pyc
o
�bI} � @ sl d Z ddlmZ G dd� de�ZG dd� de�ZG dd� de�ZG d d
� d
e�ZG dd� de�ZG d
d� de�ZG dd� de�Z G dd� de�Z
G dd� de�ZG dd� de�ZG dd� de�Z
G dd� de
�ZG dd� de�ZG dd� de�ZG dd � d e�ZG d!d"� d"e�ZG d#d$� d$e�ZG d%d&� d&e�ZG d'd(� d(e�ZG d)d*� d*e�ZG d+d,� d,e�Zg d-�Zd.S )/z/
Interfaces for L{twisted.mail}.
@since: 16.5
� )� Interfacec @ �( e Zd ZdZdd� Zdd� Zdd� ZdS ) �IChallengeResponsez;
An C{IMAPrev4} authorization challenge mechanism.
c C � dS )zd
Return a client challenge.
@return: A challenge.
@rtype: L{bytes}
N� r r r �9/usr/lib/python3/dist-packages/twisted/mail/interfaces.py�getChallenge � zIChallengeResponse.getChallengec C r )aL
Extract a username and possibly a password from a response and
assign them to C{username} and C{password} instance variables.
@param response: A decoded response.
@type response: L{bytes}
@see: L{credentials.IUsernamePassword} or
L{credentials.IUsernameHashedPassword}
Nr )�responser r r �setResponse r zIChallengeResponse.setResponsec C r )a=
Are there more challenges than just the first? If so, callers
should challenge clients with the result of L{getChallenge},
and check their response with L{setResponse} in a loop until
this returns L{False}
@return: Are there more challenges?
@rtype: L{bool}
Nr r r r r �moreChallenges'