mistotebe / skeeter Goto Github PK

Skeeter should be able to at least snoop the beginning of a client-first SASL conversation to retrieve the user identity to guide the mailhost resolution.

And any other useful information.

Currently, the proxy callbacks make up a naive read/write pair, never limiting the amount of data buffered inside skeeter. This can easily get out of hand with asymmetric connections where one side is able to generate data faster than the other can receive.

Possibly a small state machine interacting with the watermarks should be able to fix this. Not sure about the buffering properties and the verifiability of that code.

The process should call daemon() unless asked not to, also it should create a pid file in this case.

Skeeter should be able to act the server part of a SASL authentication and then if that was successful, authenticate to the backend separately using its own credentials and the user's authorization identity.

The server banner and response to the CAPABILITY command are currently hardcoded. This manifests as several quirks:

• STARTTLS is advertised even when no configuration is present or when a TLS layer is already in place.
• the banner does not claim LOGINDISABLED but CAPABILITY does, this should be configurable (e.g. enable LOGIN only when a TLS layer is in place)

This is a blocker for #7 where all supported SASL mechanisms have to be advertised in the CAPABILITY string

#4 depends on it

The infrastructure is undergoing a sizeable rework, it would be good to have some tests in place to keep the development on track.

When connecting to the remote server, we should verify that the certificate is valid and matches the proper name in CommonName or DNSname.

README is not mentioning the dependency on libconfig. It also does not mention, that bufferevent_trigger is needed thus the latest released libevent 2.1.3 alpha is not sufficient.

Skeeter should be able to handle literal and quoted username and password arguments to the LOGIN command. The resolution of #3 was written with this in mind.
As imtest, the cyrus' IMAP utility, uses literals in these arguments by default, this belongs in the first alpha.