Scott wrote:
> >The current file replication mechanism through sipXsupervisor
> >requires that the file to be replicated be declared in the
> >process definition of some service. Since we don't know in
> >advance what the names (or even
> >number) of additional CA certificates might be, we'll need to
> >extend the supervisors capabilities and what a service can
> >declare in its process definition.
> >
> >I can think of two possible approaches:
> >
> > A. Allow the declaration of a directory, which would allow the
> > replication of any file whose directory path matches the
> > directory. A process might declare:
> >
> > <directory>/etc/sipxpbx/ssl/authorities</directory>
> >
> > B. Provide for a file glob or regular expression match for file
> > names. The process definition might include:
> >
> > <file
> >pattern='true'>/etc/sipxpbx/ssl/authorities/*.crt</file>
Raymond wrote:
> I think I prefer A over B just because for the certificate authorities,
> we don't necessarilly know the suffix as it may be different than what
> we use.
Actually, we could do both:
<directory>
<path>/etc/sipxpbx/ssl/authorities</path> <!-- exactly one path element
required -->
<filepattern>*.crt</filepattern> <!-- one or more name patterns -->
<filepattern>*.p12</filepattern>
</directory>
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
