[JDEV] (no subject)
Heiner Wolf
wolf at bluehands.de
Thu Dec 4 13:39:29 CST 2003
Hi,
I am about to implement a whiteboard in Jabber client.
I found JEP 113, but not much else. Any clients using this?
I remember a discussion about SVG for Jabber whiteboarding, but I can
not find the thread in the list archives. Any hints before I start
coding?
hw
--
Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
http://www.bluehands.de/people/hw
+49 (0721) 16108 75
> -----Original Message-----
> From: xmppwg-bounces at jabber.org [mailto:xmppwg-bounces at jabber.org]On
> Behalf Of Peter Saint-Andre
> Sent: Thursday, December 04, 2003 7:29 PM
> To: Chris Mullins
> Cc: xmppwg at jabber.org
> Subject: Re: [xmppwg] XMPP Compliance Precludes inband
> registrations and
> oldstyle auth
>
>
> On Thu, Dec 04, 2003 at 10:21:06AM -0800, Chris Mullins wrote:
> > Section 9.1.2 of XMPP CORE states: "If a client attempts to
> send an XML stanza over a stream that is not yet
> authenticated, the server SHOULD return a <not-authorized/>
> stream error to the client. If generated, both of these
> conditions MUST result in closing of the stream and
> termination of the underlying TCP connection; this helps to
> prevent a denial of service attack launched from a rogue client."
> >
> > This implies that a XMPP compliant server (one that is
> implementing the "Should" portions) will disallow the older
> iq:register packets, thereby making inband registration
> impossible, and will also disallow the older IQ:Auth packets,
> thereby breaking older clients.
> >
> > Is this intentional? I don't believe that it is.
>
> It says SHOULD -- not MUST -- so that servers can handle such
> situations. Use your best judgment regarding which stanzas to
> accept prior to authentication.
>
> Peter
>
> --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.php
>
> _______________________________________________
> xmppwg mailing list
> xmppwg at jabber.org
> https://jabberstudio.org/mailman/listinfo/xmppwg
>
More information about the JDev
mailing list