Thanks to Gordon and Paul for kind help.<div><br></div><div>Actually we have a limitation to place the Asterisk server in client premises if the server is in there premises then this means they have full control over it. </div>
<div><br></div><div>harddisk encryption seems a good option but no automated boot is big issue :(</div><div><br></div><div>Is there some thing possible like that ?<br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">
On Tue, Jul 6, 2010 at 5:21 PM, Gordon Henderson <span dir="ltr"><<a href="mailto:gordon%2Basterisk@drogon.net" target="_blank">gordon+asterisk@drogon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div>On Tue, 6 Jul 2010, ABBAS SHAKEEL wrote:<br>
<br>
> Hello Community,<br>
><br>
> I have a question , I have been working with asterisk and developed some<br>
> successful applications. 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 configuration<br>
> files (Of course copy and distribute or replicate the logic with out<br>
> permission).<br>
><br>
> Now the configuration files are stored in /etc/asterisk/* (Of course we can<br>
> specify a different location but at end we specify this in a configuration<br>
> file).<br>
><br>
> Is there a way that the configuration files get encrypted or some thing else<br>
> so that some one who have system access can not copy the configuration files<br>
> data or look into that files.<br>
<br>
</div></div>The simple answer is that you can't prevent anyone copying it if they have<br>
physical access.<br>
<br>
All you can do is make it hard.<br>
<br>
If you wanted to encrypt them, you'd need to alter asterisk.<br>
<br>
You could use something like trucrypt, or another whole disk encryption<br>
technology, but that'll require someone typing in a password at boot time<br>
making unattended reboots impossible.<br>
<br>
Another way which I have seen is to do away with the dialplan entirely and<br>
do it all in a single big compiled AGI C program. (Ok, you have minimal<br>
dialplan to pump everything into it, but...) and don't distribute the<br>
source to the C program...<br>
<br>
You need to work out just what it's worth to you if someone does copy it.<br>
Realistically, what's your target audience? Are your clients the sort of<br>
people likely to copy and and sell it on? For most businesses, I'd guess<br>
not.<br>
<font color="#888888"><br>
Gordon<br>
</font><div><div></div><div><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>