On Thu, Aug 13, 2009 at 8:15 PM, Brian Cully wrote:
> On 13-Aug-2009, at 21:06, Peter Saint-Andre wrote:
>> Whether any of these attack vectors are worrisome is another matter.
>
> I tend not to think so. In the case where a bare JID is reused (e.g.,
> "anonym...@example.com") then it's acce
On 13-Aug-2009, at 21:06, Peter Saint-Andre wrote:
On 8/13/09 6:45 PM, Andy Skelton wrote:
XEP-0175 1.2rc1, which states:
"After a client authenticates using the SASL ANONYMOUS mechanism, it
MUST bind a resource; the server SHOULD ignore the resource
identifier
provided by the client (if an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/09 6:45 PM, Andy Skelton wrote:
> XEP-0175 1.2rc1, which states:
>
> "After a client authenticates using the SASL ANONYMOUS mechanism, it
> MUST bind a resource; the server SHOULD ignore the resource identifier
> provided by the client (if an
On 13-Aug-2009, at 20:54, Peter Saint-Andre wrote:
On 8/13/09 6:53 PM, Brian Cully wrote:
On 13-Aug-2009, at 20:45, Andy Skelton wrote:
"After a client authenticates using the SASL ANONYMOUS mechanism, it
MUST bind a resource; the server SHOULD ignore the resource
identifier
provided by the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/09 6:53 PM, Brian Cully wrote:
> On 13-Aug-2009, at 20:45, Andy Skelton wrote:
>> "After a client authenticates using the SASL ANONYMOUS mechanism, it
>> MUST bind a resource; the server SHOULD ignore the resource identifier
>> provided by the
Sorry, I should have pasted this link:
http://xmpp.org/extensions/tmp/xep-0175-1.2.html
On Thu, Aug 13, 2009 at 7:53 PM, Brian Cully wrote:
> On 13-Aug-2009, at 20:45, Andy Skelton wrote:
>>
>> "After a client authenticates using the SASL ANONYMOUS mechanism, it
>> MUST bind a resource; the server
On 13-Aug-2009, at 20:45, Andy Skelton wrote:
"After a client authenticates using the SASL ANONYMOUS mechanism, it
MUST bind a resource; the server SHOULD ignore the resource identifier
provided by the client (if any) and instead assign a resource
identifier that it generates on behalf of the cli
Howdy, list! I'm Andy Skelton. I work on WordPress.com. I am using a
modified ejabberd to push our posts and comments through pubsub to
cool places like Collecta. Coincidentally you can subscribe to any
WordPress.com blog (e.g. icanhascheezburger.com) by chatting with my
pubsub bot. (See http://sup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI.
- Original Message
Subject: [Members] Board and Council Elections
Date: Thu, 13 Aug 2009 09:42:05 -0600
From: Peter Saint-Andre
Reply-To: XSF Members
To: XSF Members
In the member meeting last week, we decided on the followi
Hi,
I'd like to suggest the addition of a "countrycode" child element to
XEP-0080: User Location. This element would convey a xs:string
representing the ISO 3166 two letter country code of the user's
location.
The rational behind this is that while the location can be in the user's
local
On Thu, Aug 13, 2009 at 1:51 AM, Peter Saint-Andre wrote:
>
> 1. Who has implemented XEP-0203? Please note that the protocol must be
> implemented in at least two separate codebases (and preferably more).
Tkabber uses XEP-0203 timestamps as well as XEP-0091 ones (203 is preferrable).
>
> 2. Have
> 1. Who has implemented XEP-0203? Please note that the protocol must be
> implemented in at least two separate codebases (and preferably more).
First used in Prosody in November 2008 (before Prosody 0.1 was released).
> 3. Is the text of XEP-0203 clear and unambiguous? Are more examples
> needed
> 1. Who has implemented XEP-0202? Please note that the protocol must be
> implemented in at least two separate codebases (and preferably more).
Prosody has had a mod_time since November 2008 (before Prosody 0.1 was
released).
13 matches
Mail list logo
