From: Albert Krewinkel <tarleb@moltkeplatz.de>
To: ding@gnus.org
Cc: Albert Krewinkel <tarleb@moltkeplatz.de>
Subject: [PATCH 0/2] Simpler authentication with SASL
Date: Sat, 26 Oct 2013 12:54:39 +0200 [thread overview]
Message-ID: <1382784881-16736-1-git-send-email-tarleb@moltkeplatz.de> (raw)
Hello,
even though gnus as an implementation of the SASL protocol, no part of
gnus other than managesieve makes use of it. A possible explanation
is that the current code is a transliteration of some Java program and
is rather awkward to use. This is an attempt to fix the situation.
SASL authenticating with the proposed code just requires three simple,
protocol specific functions. Sample usage of this method is
demonstrated in sieve-manage.el.
Please let me know what you think of the proposed changes. The
patches are also available at github (https://github.com/tarleb/gnus).
Cheers,
Albert
Albert Krewinkel (2):
sasl.el: simplify authentication with SASL, make code more lispy
sieve-manage.el: adapt sieve-manage to SASL simplification
lisp/ChangeLog | 34 +++
lisp/{sasl-cram.el => sasl-cram-md5.el} | 29 ++-
lisp/{sasl-digest.el => sasl-digest-md5.el} | 60 ++++--
lisp/sasl-ntlm.el | 24 +--
lisp/sasl.el | 312 ++++++++++++----------------
lisp/sieve-manage.el | 238 +++++++++------------
6 files changed, 323 insertions(+), 374 deletions(-)
rename lisp/{sasl-cram.el => sasl-cram-md5.el} (66%)
rename lisp/{sasl-digest.el => sasl-digest-md5.el} (74%)
--
1.8.4.rc3
next reply other threads:[~2013-10-26 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 10:54 Albert Krewinkel [this message]
2013-10-26 10:54 ` [PATCH 1/2] sasl.el: simplify authentication with SASL, make code more lispy Albert Krewinkel
2013-10-26 10:54 ` [PATCH 2/2] sieve-manage.el: adapt sieve-manage to SASL simplification Albert Krewinkel
2013-10-28 7:02 ` [PATCH 0/2] Simpler authentication with SASL Daiki Ueno
2013-10-29 14:21 ` Albert Krewinkel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1382784881-16736-1-git-send-email-tarleb@moltkeplatz.de \
--to=tarleb@moltkeplatz.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).