[jdev] SOCKS5 Bytestream initiation between chat users inSemi-Anonymous room

[Daniel Atallah]

Greetings,

I'm trying to figure out how it might be possible to successfully
initiate a SOCKS5 bytestream (XEP-0065) between two users in a
Semi-Anonymous chat room (XEP-0045).

The issue that I'm running into is that because the real JID of the
initiator is different than the JID the target is seeing (and vice
versa), the DST.ADDR hashes generated by the sender and recipient
don't match and consequently the SOCKS5 connection initiation must
fai.

Neither party knows how their JID is being presented to the other side
and the hash requires both parties to know both JIDs (DST.ADDR = SHA1
Hash of: (SID + Initiator JID + Target JID)), so, I don't see a way to
handle this correctly.

Am I missing something, or is this a gap in functionality?

Thanks,
Daniel
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe (AT) jabber (DOT) org
_______________________________________________

[Sergei Golovan]

On Sat, Jun 14, 2008 at 3:35 AM, Daniel Atallah <datallah (AT) pidgin (DOT) im> wrote:
>
> The issue that I'm running into is that because the real JID of the
> initiator is different than the JID the target is seeing (and vice
> versa), the DST.ADDR hashes generated by the sender and recipient
> don't match and consequently the SOCKS5 connection initiation must
> fai.

Tkabber simply uses MUC JIDs (room@server/nick) when it sends a
request to or receives it from a MUC contact.

--
Sergei Golovan
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe (AT) jabber (DOT) org
_______________________________________________

[Daniel Atallah]

On Sat, Jun 14, 2008 at 2:40 AM, Sergei Golovan <sgolovan (AT) nes (DOT) ru> wrote:
> Tkabber simply uses MUC JIDs (room@server/nick) when it sends a
> request to or receives it from a MUC contact.

I suppose that this would be a possible way to do it, I was hoping
that there was a better way though.
This isn't a great solution for me because I can't really tell if the
request is being sent to a MUC contact - if I know the real JID, that
will be used instead.

-D
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe (AT) jabber (DOT) org
_______________________________________________

[Sergei Golovan]

On 6/16/08, Daniel Atallah <datallah (AT) pidgin (DOT) im> wrote:
>
> I suppose that this would be a possible way to do it, I was hoping
> that there was a better way though.
> This isn't a great solution for me because I can't really tell if the
> request is being sent to a MUC contact - if I know the real JID, that
> will be used instead.

Unfortunately, MUC design implies that you have to know if the
message, presence or IQ is coming from a MUC contact. So, it's not a
big deal to substitute your MUC JID in filetransfer requests also.

--
Sergei Golovan
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe (AT) jabber (DOT) org
_______________________________________________