On Fri, Oct 28, 2016 at 2:49 PM, Philipp Hancke <[email protected]> wrote: > I assumed that a new connection was used for the burner id. If so how would > you do this verification if not using a shared secret mechanism?
I wasn't planning on using a new session, but I could see that being easier and make managing the new identities easier (no need to check if incoming stanzas were sent to the burner JID before replying). The way I see it having burner JIDs use a new session probably makes implementations far easier, at the cost of the overhead of establishing a new session. My original (poorly explained) idea was that when the server received something that looked like a valid burner JID (because it's in the database and marked as a burner JID or because it's local part meets a certain format or however it's implemented) it would check what JID it was issued by and see if that corresponds to the JID associated with the session on which the stanza was sent. > Or did I misunderstand things and you authenticate as the real id with > authcid and password and use the burner jid as authorization identify > (authzid). I hadn't actually thought about that; I think doing separate sessions and using the burner JID as the authzid would be both easier to implement and harder to get wrong in terms of security. I'm going to experiment with this; thanks! —Sam -- Sam Whited pub 4096R/54083AE104EA7AD3 _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
