XSF Discussion - 2020-01-03

flow, I sent an email about that post-summit, it should be possible to find

In case people are interested, I've spent this evening making a start on getting my/Surevine's old SASL2 code into shape for Openfire 3.5.0 - branch here, which probably doesn't work yet: https://github.com/dwd/Openfire/tree/dwd/sasl2

That branch has both SASL2 and TOTP-2FA, and also a PASSWORD-RESET task that can be used to force a client that knows about it to change its password with the server.

Does SASL2 natively support per-device passwords/etc.? Would that just be a matter of a new mechanism?

MattJ, A new mechanism, like CLIENT-KEY. Surevine did publish (quietly, in its public github repos) CLIENT-KEY's predecessor, DEVICE-KEY, but I'm not bothering to include that because it had some flaws I've now forgotten.

MattJ, Might be, though, that I could massage DEVICE-KEY into CLIENT-KEY. They're not much different.

I applaud your effort to backport this to a release made 11 years ago.

more likely: you ment the upcoming 4.5.0 release.

you hope he meant that release :)

maybe he's working for redhat now

You'd be surprised how much people he'd make happy.

Our users aren't known for dutifully updating...

Yeah, typo. :-)

the second-most recorded update checks made in year-to-date was made by Openfire instances that identify themselves as 3.8.2 😞

(released May '13)

I like how that table contains references to version numbers that we never used.

I hope this guy doesn't team up with jonas’ https://devpost.com/software/sed-pathfinder probably take over the world (with sed)