On Tue, 2008-10-21 at 12:42 -0400, Steinmann, Martin (BL60:2500) wrote:
> >
> >
> >
> >On Tue, 2008-10-21 at 10:25 -0400, Martin Steinmann wrote:
> >> Installing sipXecs from RPMs still requires an additional manual step
> >> at the end to install a self-signed certificate by running a script.
> >> Given that we now use a default certificate, would it make sense to
> do
> >> this as part of the RPM installation so that no manual steps are
> >> required anymore after installation?
> >
> >Could you be more specific about what the "manual step" and "a script"
> >are?
> >
> >I don't believe that any additional step will be needed once the new
> >sipx-setup* scripts are in use (still trying to get a good build out
> >that includes them)...
>
> Scott
> As far as I know today after a fresh RPM install you have to run
> /usr/bin/ssl-cert/gen-ssl-keys.sh and /usr/bin/ssl-cert/install-cert.sh
Ah... sorry.
See
http://list.sipfoundry.org/archive/sipx-dev/msg14548.html
The sipXecs 3.11.7-013770 builds completed a little while ago (they have
not yet been copied to the unstable repo, but they should be soon) and
they have the changes described in that message.
> First System:
>
> Prompts for the SIP Domain.
> Generates Certificates (CA & Host) using fixed
> organization name inputs & SIP Domain
for adding a system to a cluster, the cert will be generated by
sipXconfig and downloaded and installed by the sipx-setup script. This
part doesn't work yet because the sipXconfig side is not yet done:
http://track.sipfoundry.org/browse/XCF-2615
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
