Hi,
On Sat, Mar 6, 2010 at 5:01 AM, Evgeniy Khramtsov xramt...@gmail.com wrote:
There is already STUN support in ejabberd :P
For me it is unclear why we need another way to discover client's public ip,
that's why I'm asking
Because I already have a XMPP stack, and if I can get away without
FYI: STUN and TURN are two separate mechanisms.
What are the requirements for the client when Jingle is used?
Pedro Melo wrote:
Hi,
On Sat, Mar 6, 2010 at 5:01 AM, Evgeniy Khramtsov xramt...@gmail.com wrote:
There is already STUN support in ejabberd :P
For me it is unclear why we need
Hi,
On Sat, Mar 6, 2010 at 9:35 AM, Hannes Tschofenig
hannes.tschofe...@gmx.net wrote:
FYI: STUN and TURN are two separate mechanisms.
I meant STUN, sorry.
Bye,
--
Pedro Melo
http://www.simplicidade.org/
xmpp:m...@simplicidade.org
mailto:m...@simplicidade.org
On Saturday 06 March 2010 01:33:25 Pedro Melo wrote:
On Sat, Mar 6, 2010 at 5:01 AM, Evgeniy Khramtsov xramt...@gmail.com
wrote:
There is already STUN support in ejabberd :P
For me it is unclear why we need another way to discover client's public
ip, that's why I'm asking
Because I
On 6 March 2010 18:12, Justin Karneges
justin-keyword-jabber.093...@affinix.com wrote:
On Saturday 06 March 2010 01:33:25 Pedro Melo wrote:
On Sat, Mar 6, 2010 at 5:01 AM, Evgeniy Khramtsov xramt...@gmail.com
wrote:
There is already STUN support in ejabberd :P
For me it is unclear why we
As noted in the XEP, the server actually returns what it perceives to be the
client's IP address.
What the security considerations miss is that doing so may unintentionally
cause disclose information about the network information the server operates in.
Server operators likely don't want to
While implementing mod_sift for Prosody, I saw some possibilities for
improvement and had thoughts about issues. Some of these follow.
1. Remove disallowed child elements for filtered messages and presence.
Here's a typical identi.ca message:
message from=upd...@identi.ca/xmpp001daemon
interesting - I've built a variation on this for offline messages,
but allowing quite complex allow criteria. I couldnt make xmpp do it
(I'm not saying xmpp couldnt, but just that I couldnt figure out how) as
my case seemed to require altered routing rules and a few other issues
surrounding my
