generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

TODO: Added IMAP section and removed unused Other protocols section

Browse Source
This commit is contained in:
Steve Holme 2013-03-16 10:18:43 +00:00
parent f660fc4423
commit 5e2ef3942f
1 changed files with 22 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/TODO
View File

@ -71,10 +71,12 @@
10.2 Initial response 10.2 Initial response
10.3 Graceful base64 decoding failure 10.3 Graceful base64 decoding failure
11. LDAP 11. IMAP
11.1 SASL based authentication mechanisms 10.1 auth= in URLs
10.2 Graceful base64 decoding failure
12. Other protocols 12. LDAP
12.1 SASL based authentication mechanisms
13. New protocols 13. New protocols
13.1 RSYNC 13.1 RSYNC
@ -411,9 +413,23 @@ to provide the data to send.
gracefully shutdown the authentication process by sending a * response to the gracefully shutdown the authentication process by sending a * response to the
server as per RFC5034. server as per RFC5034.
11. LDAP 11. IMAP
11.1 SASL based authentication mechanisms 11.1 auth= in URLs
Being able to specify the preferred authentication mechanism in the URL as
per RFC5092.
11.2 Graceful base64 decoding failure
Rather than shutting down the session and returning an error when the
decoding of a base64 encoded authentication response fails, we should
gracefully shutdown the authentication process by sending a * response to the
server as per RFC3501.
12. LDAP
12.1 SASL based authentication mechanisms
Currently the LDAP module only supports ldap_simple_bind_s() in order to bind Currently the LDAP module only supports ldap_simple_bind_s() in order to bind
to an LDAP server. However, this function sends username and password details to an LDAP server. However, this function sends username and password details
@ -421,8 +437,6 @@ to provide the data to send.
be possible to use ldap_bind_s() instead specifing the security context be possible to use ldap_bind_s() instead specifing the security context
information ourselves. information ourselves.
12. Other protocols
13. New protocols 13. New protocols
13.1 RSYNC 13.1 RSYNC