Pure Python SASL client and server library.
Pure Python SASL client and server library. The design of the library is intended to be agnostic of the protocol or network library.
The library currently offers
CRAM-MD5 mechanisms by
XOAUTH2 mechanisms are also available for special
Available in PyPi:
pip install pysasl
Install into a virtual environment:
virtualenv env source env/bin/activate python setup.py develop pip install -r test/requirements.txt
Run the tests and report coverage metrics:
Server-side SASL has three basic requirements:
- Must advertise supported mechanisms,
- Must issue authentication challenges to the client and read responses,
- Must determine if credentials are considered valid.
Implementations may decide on any sub-set of mechanisms to advertise. Make this
choice when instantiating the
from pysasl import SASLAuth auth1 = SASLAuth() # or... auth2 = SASLAuth([b'PLAIN', b'LOGIN'])
To get the names of all available mechanisms:
mechanisms = [mech.name for mech in auth1.server_mechanisms] mech = auth1.get(b'PLAIN')
Once a mechanism has been chosen by the client, enter a loop of issuing challenges to the client:
def server_side_authentication(sock, mech): challenges =  while True: try: return mech.server_attempt(challenges) except ServerChallenge as chal: challenges.append(chal) sock.send(chal.get_challenge() + b'\r\n') chal.set_response(sock.recv(1024).rstrip(b'\r\n'))
It's worth noting that implemenations are not quite that simple. Most will
expect all transmissions to base64-encoded, often with a prefix before the
server challenges such as
+. See the appropriate RFC for your
protocol, such as RFC 4954 for SMTP or RFC 3501 for IMAP.
Once the challenge-response loop has been completed and we are left with the
AuthenticationCredentials object, we can access information from the
print('Authenticated as:', result.authcid) print('Authorization ID:', result.authzid) # To compare to a known password... assert result.check_secret('s3kr3t') # Or to compare hashes... assert password_hash == hash(result.secret)
Some mechanisms (e.g.
EXTERNAL) will not support direct access to
the secret. In this case,
result.has_secret will be
False and you should
The goal of client-side authentication is to respond to server challenges until the authentication attempt either succeeds or fails.
Choosing a Mechanism
The first step is to pick a SASL mechanism. The protocol should allow the server to advertise to the client which mechanisms are available to it:
from pysasl import SASLAuth auth = SASLAuth(advertised_mechanism_names) mechanisms = [mech.name for mech in auth.client_mechanisms] mech = auth.get(b'PLAIN')
The resulting mechanisms will be the intersection of those advertised by the server and those supported by pysasl.
Once a mechanism is chosen, we enter of a loop of responding to server challenges:
from pysasl import AuthenticationCredentials def client_side_authentication(sock, mech, username, password): creds = AuthenticationCredentials(username, password) responses =  while True: resp = mech.client_attempt(creds, responses) sock.send(resp.get_response() + b'\r\n') data = sock.recv(1024).rstrip(b'\r\n') if data == 'SUCCESS': return True elif data == 'FAILURE': return False resp.set_challenge(data) responses.append(resp)
As you might expect, a real protocol probably won't return
FAILURE, that will depend entirely on the details of the protocol.
Supporting Initial Responses
Some protocols (e.g. SMTP) support the client ability to send an initial response before the first server challenge, for mechanisms that support it. A perfectly valid authentication can then have no challenges at all:
AUTH PLAIN AHVzZXJuYW1lAHBhc3N3b3Jk 235 2.7.0 Authentication successful
In this case, both client-side and server-side authentication should be handled a bit differently. For example for server-side:
except ServerChallenge as chal: challenges.append(chal) if initial_response: chal.set_response(initial_response) initial_response = None else: sock.send(chal.get_challenge() + b'\r\n') chal.set_response(sock.recv(1024).rstrip(b'\r\n'))
And for client-side, just call
resp = mech.client_attempt(creds, )
to get the initial response before starting the transmission. All
mechanisms should either return an initial response or an empty string
when given an empty list for the second argument.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size & hash SHA256 hash help||File type||Python version||Upload date|
|pysasl-0.3.1-py3-none-any.whl (12.5 kB) Copy SHA256 hash SHA256||Wheel||py3|
|pysasl-0.3.1.tar.gz (12.7 kB) Copy SHA256 hash SHA256||Source||None|