Scott wrote:
>Subject: Re: [sipX-dev] Distributing SSL CA certificates (and 
>other files not known at build time)
>
>
>On Mon, 2009-12-14 at 15:03 -0500, Dale Worley wrote:
>
>> > What are the semantics?  In particular, can one specify a 
>directory 
>> > and all of the files in all of the subdirectories?
>
>On Mon, 2009-12-14 at 15:19 -0500, Scott Lawrence wrote:
>
>> My thinking is/was that subdirectories should be specified 
>separately, 
>> so for example:
>> 
>>    <directory>
>>      <path>/etc/sipxpbx/foo</path>
>>      <filepattern>*.xml</filepattern> 
>>      <filepattern>*.wav</filepattern>
>>    </directory>
>>    <directory>
>>      <path>/etc/sipxpbx/foo/bar</path>
>>      <filepattern>*.abc</filepattern> 
>>    </directory>
>>    <directory>
>>      <path>/etc/sipxpbx/foo/bingo</path>
>>      <filepattern>*.xyz</filepattern>
>>    </directory>
>> 
>> allows three directories, each of which has a set of 
>suffixes it allows.
>> The '*' in the filepatterns should match anything but '/', '.', and 
>> '..', the way shell file globs do (I don't think we need to support 
>> any richer pattern primitive than that at this time).
>
>See attached patch for my suggested addition to the process 
>definition schema for this.
>
>

Patch looks good to me.  I like the flexibility that it provides and
that it would work for other things beside SSL CA Certificates. 

I guess now all we would need are XML/RPC interfaces to transfer these
certs, Config to make use of them and then some way for Config to then
trigger the regeneration of the Truststore/KeyStores on the remote box.

Raymond
_______________________________________________
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/

Reply via email to