|
Re: Limiting access to an EMF model [message #651983 is a reply to message #651968] |
Wed, 02 February 2011 11:03 |
|
No Real Name wrote on Wed, 02 February 2011 15:45 | Is there any way to limit the access by other plugins to a generated EMF model? I create a model that contains some sensitive info and I suspect it's easy to extract it from a running eclipse by installing additional plugins that query the model. Any suggestions? Are there any encryption/obfuscation tools/strategies?
|
Hi,
In the MANIFEST.MF of the model plugin under Runtime tab, you can specify which packages, you want to export. And there is one more option for package visibility to other plugins. These two options can help you in securing your classes if you don't want them to be accessed by other plugins.
Regards,
Animesh
Regards,
Animesh
[Updated on: Wed, 02 February 2011 11:07] Report message to a moderator
|
|
|
Re: Limiting access to an EMF model [message #651988 is a reply to message #651968] |
Wed, 02 February 2011 11:05 |
Ed Merks Messages: 33113 Registered: July 2009 |
Senior Member |
|
|
Comments below.
fritz.j.rybka@gmail.com wrote:
> Is there any way to limit the access by other plugins to a generated
> EMF model? I create a model that contains some sensitive info and I
> suspect it's easy to extract it from a running eclipse by installing
> additional plugins that query the model. Any suggestions?
I assume it's the instance of the model you're worried about. Unless
you provide some mechanism to access the instances, there's no way for
anyone else to get at them. I guess the only tricky thing someone could
still do is extend your factory so the control all instance creation,
but you could avoid exporting the packages for your API so that no one
will even have access to the classes.
> Are there any encryption/obfuscation tools/strategies?
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03011 seconds