[jitsi-dev] ${arch} provisioning parameter


#1

Hiya,

To work around the issue about the StartSSL CA certificate not
trusted by jitsi's JRE and the issue about amd64 Windows clients
not supporting using the Windows certificate store yet, I'm
trying to give different provisioning parameters based on the
architecture of the client.

Unfortunately, The jitsi architecture (amd64/x86...) is not
provided as part of the ${osname} parameter passed to the
provisioning server. Would it be possible to have an extra
${arch} parameter for that?

Thanks,
Stephane


#2

Hey

Unfortunately, The jitsi architecture (amd64/x86...) is not
provided as part of the \{osname\} parameter passed to the provisioning server\. Would it be possible to have an extra {arch} parameter for that?

Thanks for the suggestion! The parameter is supported from build 3686 onwards.

Regards,
Ingo


#3

2011-09-30 23:17:27 +0200, Bauersachs Ingo:
[...]

> Unfortunately, The jitsi architecture (amd64/x86...) is not
> provided as part of the ${osname} parameter passed to the
> provisioning server. Would it be possible to have an extra
> ${arch} parameter for that?

Thanks for the suggestion! The parameter is supported from build 3686 onwards.

[...]

Wow! A few hours from request to released solutions, amazing!
Thanks!

May I ask for another one then :-):

Now, I can update my provisioning URL to have the a=${arch},
except that I can't do that for users who have already gone
through the DHCP provisioning. For those, I have to tell them to
update the URI manually.

Could it be possible for the provisionning script to update the
provisionning URI (even if that means waiting for the next time
jitsi starts to be queried with the new URL)?

···

--
Stephane


#4

Now, I can update my provisioning URL to have the a=${arch},
except that I can't do that for users who have already gone
through the DHCP provisioning. For those, I have to tell them to
update the URI manually.

Could it be possible for the provisionning script to update the
provisionning URI (even if that means waiting for the next time
jitsi starts to be queried with the new URL)?

I'm not sure I follow. I never used the DHCP provisioning, but a short look at the code tells me that the URL discovery via DHCP is done every time Jitsi starts. If you change the URL on the DHCP server you should be fine.

If you want to change the provisioning parameters through the provisioning script, they are:
net.java.sip.communicator.plugin.provisioning.METHOD
net.java.sip.communicator.plugin.provisioning.URL

Did I miss something?

Ingo


#5

2011-10-03 17:57:32 +0200, Bauersachs Ingo:

> Now, I can update my provisioning URL to have the a=${arch},
> except that I can't do that for users who have already gone
> through the DHCP provisioning. For those, I have to tell them to
> update the URI manually.
>
> Could it be possible for the provisionning script to update the
> provisionning URI (even if that means waiting for the next time
> jitsi starts to be queried with the new URL)?

I'm not sure I follow. I never used the DHCP provisioning, but
a short look at the code tells me that the URL discovery via
DHCP is done every time Jitsi starts. If you change the URL on
the DHCP server you should be fine.

Actually, and I would certainly *not* want that to be changed,
upon a successful DHCP provisioning the provisioning.METHOD is
set to Manual and URL to the URL discovered by DHCP.

The idea is you do the DHCP provisioning only once and only from
a trusted network as it's not authenticated. If it were done
every time, you'd run the risk of getting malevolent settings
when connected to an insecure network (your passwords could be
stolen that way).

The same applies to bonjour provisioning.

If you want to change the provisioning parameters through the provisioning script, they are:
net.java.sip.communicator.plugin.provisioning.METHOD
net.java.sip.communicator.plugin.provisioning.URL

[...]

As I said in another thread
(http://thread.gmane.org/gmane.comp.voip.sip-communicator.user/1441/focus=1445), that
doesn't work, whatever you set for provisioning.METHOD and
provisioning.URL via the provisioning script is overriden once
the provisioning is done (or so it seems).

···

--
Stephane


#6

2011-10-03 17:57:32 +0200, Bauersachs Ingo:

> Now, I can update my provisioning URL to have the a=${arch},
> except that I can't do that for users who have already gone
> through the DHCP provisioning. For those, I have to tell them to
> update the URI manually.
>
> Could it be possible for the provisionning script to update the
> provisionning URI (even if that means waiting for the next time
> jitsi starts to be queried with the new URL)?

I'm not sure I follow. I never used the DHCP provisioning, but
a short look at the code tells me that the URL discovery via
DHCP is done every time Jitsi starts. If you change the URL on
the DHCP server you should be fine.

Actually, and I would certainly *not* want that to be changed,
upon a successful DHCP provisioning the provisioning.METHOD is
set to Manual and URL to the URL discovered by DHCP.

The idea is you do the DHCP provisioning only once and only from
a trusted network as it's not authenticated. If it were done
every time, you'd run the risk of getting malevolent settings
when connected to an insecure network (your passwords could be
stolen that way).

The same applies to bonjour provisioning.

That being said, it's true one can switch back to DHCP
provisioning once to get the new URI, I suppose that would work,
though that also means another manual step.

If you want to change the provisioning parameters through the provisioning script, they are:
net.java.sip.communicator.plugin.provisioning.METHOD
net.java.sip.communicator.plugin.provisioning.URL

[...]

As I said in another thread
(http://thread.gmane.org/gmane.comp.voip.sip-communicator.user/1441/focus=1445), that
doesn't work, whatever you set for provisioning.METHOD and
provisioning.URL via the provisioning script is overriden once
the provisioning is done (or so it seems).

···

--
Stephane


#7

As I said in another thread
(http://thread.gmane.org/gmane.comp.voip.sip-
communicator.user/1441/focus=1445), that doesn't work, whatever you set
for provisioning.METHOD and provisioning.URL via the provisioning script
is overriden once the provisioning is done (or so it seems).

Sorry I already forgot about that thread because it was about Bonjour :frowning:

I just committed a change so that the discovered URL is cached before the provisioned data is saved to the config file. You should now be able to set a new provisioning URL. (Wait for build 3691)

Ingo