Hi Gato,Thanks for the feedback. It seems that I will need to poke other developers directly. :)
/psa Gaston Dombiak wrote:
Hey Peter, Openfire uses the SASL support provided by Java. That means that SASL PLAIN, DIGEST-MD5, GSSAPI, etc. are provided by Java. The only SASL mechanisms that we manually implemented on the server are SASL ANONYMOUS and SASL EXTERNAL. On the Smack side I recall implementing SASL PLAIN but we might now be using the one provied by Java. Regards, -- Gato On 7/30/08 12:34 PM, "Peter Saint-Andre" <[EMAIL PROTECTED]> wrote:This may be of interest here -- the SASL folks are working to advance RFC 4422 to Draft and are looking for implementation reports. Has anyone on this list developed their own SASL implementation, or are all the XMPP clients, servers, and libraries incorporating specialized SASL code? Thanks! /psa -------- Original Message -------- Date: Tue, 29 Jul 2008 17:14:32 +0100 From: Chris Newman <[EMAIL PROTECTED]> Subject: SASL to draft questionnaire To: [EMAIL PROTECTED] Here's a proposed questionnaire for an implementation report. I am not volunteering to compile responses to the questions, but I am willing to answer these questions for my implementations. - Chris --- RFC 4422 Implementation Questionnaire =============================================== 0. Contact and Description Organization Name: Implementation (Software or Service) Name: 1. Have you implemented SASL and/or SASL mechanism? 2. Which SASL mechanisms have you implemented? 3. For how long has it been deployed? 4. What features have NOT been implemented from SASL? 5. What features of SASL or SASL mechanisms are problematic for your implementation? 6. Please add any other comments you wish to share:
smime.p7s
Description: S/MIME Cryptographic Signature
