all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Magnus Henoch <magnus.henoch@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17636@debbugs.gnu.org
Subject: bug#17636: Implement SCRAM-SHA-1 SASL mechanism
Date: Thu, 05 Jun 2014 10:25:26 +0100	[thread overview]
Message-ID: <m1sinj908p.fsf@mail.gmail.com> (raw)
In-Reply-To: <jwvsinog1b7.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Sun, 01 Jun 2014 10:20:26 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>> SCRAM-SHA-1 requires an implementation of HMAC-SHA1, so I added a module
>>>> for that, too.
>>> Do we really need a whole file for those three lines?
>> Good point.  Should I just put it in hmac-md5.el?  I can't think of any
>> more logical place for it.
>
> If I could choose, I'd merge all hmac-*.el into a single file.

I just discovered that there is a second HMAC implementation in Emacs:
gnus/rfc2104.el.  Unlike hmac-*, it doesn't use a macro to make a
specific function for each hash, but just takes the hash function as an
argument.  I'll try to see if that makes any significant speed
difference, and if one implementation could be reasonably deprecated in
favour of the other.

(Incidentally, all but one usage of rfc2104-hash are in places where the
SASL library could be used instead: nnimap.el, smtpmail.el, imap.el.)

Regards,
Magnus





  reply	other threads:[~2014-06-05  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 21:32 bug#17636: Implement SCRAM-SHA-1 SASL mechanism Magnus Henoch
2014-05-30 16:15 ` Stefan Monnier
2014-06-01  2:43   ` Magnus Henoch
2014-06-01 14:20     ` Stefan Monnier
2014-06-05  9:25       ` Magnus Henoch [this message]
2014-10-09 20:14       ` Magnus Henoch
2014-10-17 16:41         ` Stefan Monnier
2015-02-13  8:57           ` Lars Ingebrigtsen
2015-02-13  8:55         ` Lars Ingebrigtsen

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=m1sinj908p.fsf@mail.gmail.com \
    --to=magnus.henoch@gmail.com \
    --cc=17636@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.