On Fri, 2009-04-03 at 12:38 -0400, Raymond Dans wrote:
> Issue XECS-2354 is an upgrade issue that has occurred because of a
> change in the 4.0 program because of the "naming" of the SSL files that
> sipXecs generates.
>
> In previous releases, these files were using the same "naming" but were
> hidden in the directory (i.e. had a dot in front of the name).
>
> I'm not familiar enough with how SSL uses these files but in an upgrade
> scenario would renaming the files so that they're no longer hidden be
> enough that SSL would still work?
>
> If renaming is a good enough solution, I propose to simply add scripting
> in the post install of the sipXcommserverLib rpm such that any hidden
> files it finds in the sipXecs SSL directory will be renamed so that
> they're no longer hidden.
>
> Is this a good enough or even proper solution for this issue?
Probably not.
There are other changes to how those files are constructed now (though
it is not yet entirely clear those changes are correct).
The contents of the java {key,trust}store files (which is what those
are) _should_ be generated from the other files in that directory, so we
may be able to regenerate them in place by running the script that
creates them now in some new mode for upgrades.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
