[jdev] SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Anthony Ortiz
Good morning everyone, Last week I decided to sit down and write a Jabber client in a Java applet, and I've implemented the basics so far (am able to digest/plain-text log in, check roster, send/process presence, and chat.) Now I would like to add File Transfer capabilities, specifically SOCKS5

[jdev] ByteStream Out-Band SOCKS5 problem... SHA1 Host not found

2005-02-25 Thread Anthony
Good morning everyone, Last week I decided to sit down and write a Jabber client in a Java applet, and I've implemented the basics so far (am able to digest/plain-text log in, check roster, send/process presence, and chat.) Now I would like to add File Transfer capabilities, specifically

[jdev] Re: SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Magnus Henoch
Anthony Ortiz [EMAIL PROTECTED] writes: sid = s5b_8e463861b5e6bc04 from = [EMAIL PROTECTED]/Psi to = [EMAIL PROTECTED]/JClient // using libidn/java/gnu/inet/encoding/Stringprep.java -- too boring to implement, thk god I found this! String SocksHost = SHA1(sid + Stringprep.nameprep(from +

Re: [jdev] Re: SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Anthony Ortiz
Thanks for the quick reply, but there's no problem with the SHA-1 due to : 1) The difference in our hash results is due to your applying SHA1(sid + from + to) rather than SHA1(sid + Stringprep.nameprep(from + to)), which in this particular case simply transforms the from and to variables to all

[jdev] Re: SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Magnus Henoch
Anthony Ortiz [EMAIL PROTECTED] writes: Thanks for the quick reply, but there's no problem with the SHA-1 due to : 1) The difference in our hash results is due to your applying SHA1(sid + from + to) rather than SHA1(sid + Stringprep.nameprep(from + to)), which in this particular case simply

Re: [jdev] Re: SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Anthony Ortiz
I SEE!! said the blind man to the deaf man as he pissed into the wind... It's all coming back to me! I get it... so what you're saying is that given : [EMAIL PROTECTED]/Psi I should do : Nodeprep(venkata) + @ + Nameprep(68.101.84.233) + / + Resourceprep(Psi) Well, I've implemented it and it

[jdev] docs.jabber.org?

2005-02-25 Thread Tim Martin
Is the documentation that was up at docs.jabber.org still available anywhere online? These documents particularly: The Jabber Protocol Overview http://docs.jabber.org/general/html/protocol.html The Jabber Programmer's Guid http://docs.jabber.org/jpg/html/main.html

Re: [jdev] docs.jabber.org?

2005-02-25 Thread Peter Saint-Andre
Some time ago, we moved old documents to: http://www.jabber.org/old-docs/ However, documents that were hopelessly out of date were not moved (IIRC, we set up forwards to appropriate newer locations). For instance, the Jabber Protocol Overview is pretty much superseded by the XMPP RFCs and

Re: [jdev] Query regarding development

2005-02-25 Thread Peter Saint-Andre
On Thu, Feb 24, 2005 at 09:52:57PM -0800, Justin Karneges wrote: On Thursday 24 February 2005 09:35 pm, Krishna Prashanth wrote: Thanks for all the information. Since I have said above that I would want to develop a component (I have also read most of jabber's documentation), is plugging in

[jdev] deferred delivery

2005-02-25 Thread Oleg Motienko
Hello. What's about deferred delivery of messages via XMPP ? For example, [EMAIL PROTECTED] send message to [EMAIL PROTECTED] and server at domain2 is down for some time. In SMTP such message is waiting for some time in spool on server at domain1 and [EMAIL PROTECTED] recieve messages from

Re: [jdev] deferred delivery

2005-02-25 Thread Peter Saint-Andre
If domain2 is down when you send the message, you will receive an error message in your client. So chat later. :-) On Fri, Feb 25, 2005 at 08:34:18PM +0300, Oleg Motienko wrote: Hello. What's about deferred delivery of messages via XMPP ? For example, [EMAIL PROTECTED] send message to

[jdev] Re: Query regarding development

2005-02-25 Thread Stephen Marquard
Peter Saint-Andre wrote: On Thu, Feb 24, 2005 at 09:52:57PM -0800, Justin Karneges wrote: On Thursday 24 February 2005 09:35 pm, Krishna Prashanth wrote: Thanks for all the information. Since I have said above that I would want to develop a component (I have also read most of jabber's

[jdev] Re: deferred delivery

2005-02-25 Thread Stephen Marquard
Oleg Motienko wrote: Hello. What's about deferred delivery of messages via XMPP ? For example, [EMAIL PROTECTED] send message to [EMAIL PROTECTED] and server at domain2 is down for some time. In SMTP such message is waiting for some time in spool on server at domain1 and [EMAIL PROTECTED] recieve

Re: [jdev] SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Justin Karneges
On Friday 25 February 2005 04:45 am, Anthony Ortiz wrote: // using libidn/java/gnu/inet/encoding/Stringprep.java -- too boring to implement, thk god I found this! String SocksHost = SHA1(sid + Stringprep.nameprep(from + to)); // HASH OUTPUT=9134A1B74EB358B866C604B1E1B0DDEE0D664967 host =

Re: [jdev] SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Anthony Ortiz
Thanks for replying! Yes, I am trying to open up a SOCKS5 connection to the hash value as host : port 0 as per my understanding of the protocol : *** QUOTE [http://www.jabber.org/jeps/jep-0065.html#proto-establish] *** 4.6 Target Establishes SOCKS5 Connection with StreamHost [1] If the Target

[jdev] s2s packet routing

2005-02-25 Thread David Sansot
I was wondering if it is posible for a server to route a packet bound for another server through a third server. That is, server A has a packet for server B, but sends the packet to server C who forwards it on to server B. I guess my question is, is this allowed by the protocol? The spec only

Re: [jdev] SOCKS5 Bytestream File Transfer problem

2005-02-25 Thread Justin Karneges
On Friday 25 February 2005 02:50 pm, Anthony Ortiz wrote: [1] If the Target is willing to accept the bytestream, it MUST attempt to open a standard TCP socket on the network address of the StreamHost communicated by the Initiator. If the Initiator provides more than one StreamHost, the Target