[erlang-questions] Preventing calling some functions

Vasilij Savin <>
Sun Dec 13 10:31:51 CET 2009


Hej Mazen,

Actually there several valid reason for restricting access.

First of all, security, you do not want every plugin to be able to access
sensitive services to prevent malicious sabotage through plugins.

Secondly, the quality of plugins is not guaranteed and they might
inadvertently crash the system due to bugs in them.

Regards,
Vasilij Savin


On Sun, Dec 13, 2009 at 8:49 AM, Mazen Harake <
> wrote:

> Hi,
>
> I'm curious to why you want to have this restriction in place? The only
> thing I can come up with is if you have a proprietary reason. If you don't
> then I am _really_ curious because I don't see why restricting a user to do
> what ever he/she wants is of any benefit (assuming that we are talking about
> plugins now)?
>
> Regards,
>
> /Mazen
>
>
>
> On 10/12/2009 13:06, Kiran Khaladkar wrote:
>
>> hi,
>> I have a server written in which i allow erlang plugins also. But the
>> problem is i dont want the plugin code the call certain functions such as
>> 'gen_tcp:listen' etc .. The plugin writer should not be able to call certain
>> functions thought he might know all the erlang lib.
>> Can anyone suggest a way to do such a thing??
>> regards,
>>
>> ________________________________________________________________
>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>> erlang-questions (at) erlang.org
>>
>>
>
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
>
>


More information about the erlang-questions mailing list