GNU bug report logs -
#57956
29.0.50; Add minimal authorization support to sasl-scram-rfc
Previous Next
Reported by: "J.P." <jp <at> neverwas.me>
Date: Tue, 20 Sep 2022 13:07:02 UTC
Severity: wishlist
Tags: patch
Found in version 29.0.50
Fixed in version 29.1
Done: "J.P." <jp <at> neverwas.me>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
"J.P." <jp <at> neverwas.me> writes:
> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> "J.P." <jp <at> neverwas.me> writes:
>>
>>> Anyway, ERC would benefit greatly from these (or superior) changes
>>> because we'd like to introduce `erc-compat' analogs in an upcoming
>>> release (probably ERC 5.6). If anyone out there can spare the time,
>>> your feedback would be greatly appreciated.
>>
>> Looks OK to me.
>
> Cool, thanks.
>
> * * *
>
> Question for Philip (Cc'd):
>
> Hi. When 29.1 is released, I might want to propose some of these updated
> sasl-scram-rfc.el items for inclusion in Compat. However, one of them,
>
> `sasl-scram--client-final-message'
>
> is obviously an internal function. Does that matter? Would you rather we
> export it (as in rename it or alias it) beforehand (IOW, now)?
I'd rather not add "internal functions" to Compat, at least in a way
that it would be exposed as part of the official Compat interface. That
being said, I am not familiar with the feature being discussed here, so
maybe an exception has to be made?
> Thanks,
> J.P.
This bug report was last modified 2 years and 181 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.