Thanks community for sharing your thoughts.<div><br></div><div>@ Faisal Hanif- </div><div><div>Both of the solutions you suggested seems equally good for me let me look into it how can i do that.</div><div><br></div><div>@Stiles </div>
<div>This has nothing to do with mean spirited. If an individual is using an open source technology then it don't means that he developed some thing using that technology , then his work also becomes open source ?</div>
<div><br></div><div>@Steve </div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">>Won't "show dialplan," "sip show [peers|users]," etc. and a bit of<br>
>scripting undo most of this "security."</span></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div>
<font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">You are right after taking all the measures at the end there will be no security :P</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><span class="Apple-style-span" style="font-size: 13px; ">>Seriously, if your business depends on obfuscation instead of technical<br>
>prowess and killer customer support, you don't have a business.<br></span></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I understand what you mean. These all things will be there. Regarding security it was just a thought in my mind i shared with you all people.</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">@Kevin P Fleming </span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Thanks for clearing the things.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">@ all others thanks for sharing your thoughts</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I am not going to modify any Asterisk source code for security (because this trade-off is expensive)</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Cheers<br>
</span></font><br><div class="gmail_quote">On Thu, Jul 8, 2010 at 1:44 AM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 07/07/2010 03:33 PM, Tilghman Lesher wrote:<br>
> On Wednesday 07 July 2010 14:58:05 Kevin P. Fleming wrote:<br>
>> On 07/07/2010 10:52 AM, Tilghman Lesher wrote:<br>
>>> On Wednesday 07 July 2010 05:24:10 A J Stiles wrote:<br>
>>>> On Tuesday 06 Jul 2010, ABBAS SHAKEEL wrote:<br>
>>>>> Hello Community,<br>
>>>>><br>
>>>>> ..... I am facing an issue of security i.e. We deploy<br>
>>>>> servers to client end. Now i dont want the client to see my<br>
>>>>> configuration files (Of course copy and distribute or replicate the<br>
>>>>> logic with out permission). [ 1 paragraph omitted ]<br>
>>>>> Is there a way that the configuration files get encrypted or some thing<br>
>>>>> else so that some one who have system access can not copy the<br>
>>>>> configuration files data or look into that files.<br>
>>>><br>
>>>> Well! It's a good job Mark Spencer was never so mean-spirited,<br>
>>>> otherwise you would never have been *given* the power of Asterisk.<br>
>>><br>
>>> In addition, depending upon how you do this, it may be a serious<br>
>>> violation of the license under which Asterisk was distributed to you and<br>
>>> under which you are required to distribute Asterisk to others. If you<br>
>>> are looking for a legitimate way to do this, you'd have to obtain a<br>
>>> commercial license from Digium.<br>
>><br>
>> That statement will likely lead to yet more confusion about how the GPL<br>
>> applies to Asterisk and distribution of Asterisk... without a specific<br>
>> example of how a violation could occur, users will tend to interpret<br>
>> such statements in the broadest possible terms, which does harm to their<br>
>> understanding of how they can use and distribute Asterisk.<br>
><br>
> Correct, which is why I used the word 'may'. The only way to sufficiently<br>
> protect the configuration files would be to alter Asterisk and then refuse<br>
> to provide the altered source to those to whom he provided the binary.<br>
> That would be a violation of the GPL. The only method I can see to get<br>
> around this would be to obtain Asterisk under a non-GPL license.<br>
<br>
</div></div>It would have been helpful if you had included that example then,<br>
instead of posting such a broad statement that will likely lead to<br>
misinterpretations when it is read from the list archives (and posted on<br>
wikis, and other places). When the 'may' qualifier represents a very<br>
small subset of the possible routes the user might take to achieve their<br>
goal (even if it is the only one to provide any significant level of<br>
security), the generalization will naturally be assumed by readers to<br>
cover many more routes than it actually does... and we have direct<br>
experience that users often can and do believe that the GPLv2 does<br>
somehow control the distribution of their configuration files. In<br>
situations like this, context is everything, and it's much easier to<br>
narrow the context of such a statement when it is written, than after it<br>
has been posted and repeated.<br>
<div class="im"><br>
--<br>
Kevin P. Fleming<br>
Digium, Inc. | Director of Software Technologies<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
skype: kpfleming | jabber: <a href="mailto:kfleming@digium.com">kfleming@digium.com</a><br>
</div><div><div></div><div class="h5">Check us out at <a href="http://www.digium.com" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a><br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Best Regards<br>Shakeel Abbas<br><br>
</div></div>