[jitsi-dev] Which smack version does Jitsi use? In which code is the handling of digest-uri?


#1

Hi Guys,

I am facing an issue with beem. Beem seems to have a problem setting the
right
digest-uri. It uses the domain of the server if a separate server is set and
not the domain of the JID. As Beem also uses Smack, the question came
up which version Jitsi uses and how the issue with the digest-uri has
been solved.
Beem developers say that his would not be so easy to change.

Thanks a lot.

Cheers,
Matt


#2

Hi,

we are using smack version 3.2.2. And there is nothing about
digest-uri within our provider. If I'm right, I see the digest uri is
generated on the server and smack just uses the domain which is coming
from server, there is nothing special on our side for this.

Regards
damencho

···

On Mon, Mar 25, 2013 at 8:18 PM, Buddy Butterfly <buddy.butterfly@web.de> wrote:

Hi Guys,

I am facing an issue with beem. Beem seems to have a problem setting the
right
digest-uri. It uses the domain of the server if a separate server is set and
not the domain of the JID. As Beem also uses Smack, the question came
up which version Jitsi uses and how the issue with the digest-uri has
been solved.
Beem developers say that his would not be so easy to change.

Thanks a lot.

Cheers,
Matt


#3

Hi,

thanks for the information. That helped a developer from Beem.
The problem is within Smack library. See this link:

https://github.com/Flowdalic/smack/blob/master/source/org/jivesoftware/smack/SASLAuthentication.java

There are two authenticate method. One with callback and one without.
The one without
uses connection.getHost() (which is wrong) and the other one uses
connection.getServiceName()
which is correct and obiously used by Jitsi :wink: The developer Da_Risk
(#beem) directed it to
the Smack developers.

Thanks a lot,
Matt

···

Am 26.03.2013 08:34, schrieb Damian Minkov:

Hi,

we are using smack version 3.2.2. And there is nothing about
digest-uri within our provider. If I'm right, I see the digest uri is
generated on the server and smack just uses the domain which is coming
from server, there is nothing special on our side for this.

Regards
damencho

On Mon, Mar 25, 2013 at 8:18 PM, Buddy Butterfly <buddy.butterfly@web.de> wrote:

Hi Guys,

I am facing an issue with beem. Beem seems to have a problem setting the
right
digest-uri. It uses the domain of the server if a separate server is set and
not the domain of the JID. As Beem also uses Smack, the question came
up which version Jitsi uses and how the issue with the digest-uri has
been solved.
Beem developers say that his would not be so easy to change.

Thanks a lot.

Cheers,
Matt


#4

Correction: Vice versa:
The one without callback uses connection.getServiceName()
and the one with callback the connection.getHost() (wrong)

···

Am 26.03.2013 18:47, schrieb Buddy Butterfly:

Hi,

thanks for the information. That helped a developer from Beem.
The problem is within Smack library. See this link:

https://github.com/Flowdalic/smack/blob/master/source/org/jivesoftware/smack/SASLAuthentication.java

There are two authenticate method. One with callback and one without.
The one without
uses connection.getHost() (which is wrong) and the other one uses
connection.getServiceName()
which is correct and obiously used by Jitsi :wink: The developer Da_Risk
(#beem) directed it to
the Smack developers.

Thanks a lot,
Matt

Am 26.03.2013 08:34, schrieb Damian Minkov:

Hi,

we are using smack version 3.2.2. And there is nothing about
digest-uri within our provider. If I'm right, I see the digest uri is
generated on the server and smack just uses the domain which is coming
from server, there is nothing special on our side for this.

Regards
damencho

On Mon, Mar 25, 2013 at 8:18 PM, Buddy Butterfly <buddy.butterfly@web.de> wrote:

Hi Guys,

I am facing an issue with beem. Beem seems to have a problem setting the
right
digest-uri. It uses the domain of the server if a separate server is set and
not the domain of the JID. As Beem also uses Smack, the question came
up which version Jitsi uses and how the issue with the digest-uri has
been solved.
Beem developers say that his would not be so easy to change.

Thanks a lot.

Cheers,
Matt