Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » restricting access to XMI from EMFStore client.

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » restricting access to XMI from EMFStore client.(restricting access to XMI from EMFStore client.)

Show: Today's Messages :: Show Polls :: Message Navigator

restricting access to XMI from EMFStore client. [message #1734907]

Mon, 13 June 2016 15:40

Neil Mackenzie

Messages: 131
Registered: December 2013

Senior Member

I have some data stored as a large XMI file which I would like to allow other users to view and edit using an EMFStore client (ECP with EMFstore provider) . However I dont want the users to have access to the actual XMI file or to be able to recreate it easily. I can easily create a custom version of ECP for users to use which doesn't have an 'export' menu item. I was wondering though if the XMI files are stored in the client side anywhere such as in .emfstore\client or maybe the models are in memory only.
Thanks,
Neil

Report message to a moderator

Re: restricting access to XMI from EMFStore client. [message #1735056 is a reply to message #1734907]

Wed, 15 June 2016 05:53

Jonas Helming

Messages: 699
Registered: July 2009

Senior Member

Hi,

the data is indeed stored in .emfstore, so any solution which removes
the export feature is just making it a little bit harder to get the
data, but is not secure at all. Even if the data would only be in
memory, it would be pretty simple to get them by just adding a new
plugin to the application...

Best regards

Jonas

On 13.06.2016 17:40, Neil Mackenzie wrote:
> I have some data stored as a large XMI file which I would like to allow
> other users to view and edit using an EMFStore client (ECP with EMFstore
> provider) . However I dont want the users to have access to the actual
> XMI file or to be able to recreate it easily. I can easily create a
> custom version of ECP for users to use which doesn't have an 'export'
> menu item. I was wondering though if the XMI files are stored in the
> client side anywhere such as in .emfstore\client or maybe the models are
> in memory only.
> Thanks,
> Neil
>

Report message to a moderator

Re: restricting access to XMI from EMFStore client. [message #1735076 is a reply to message #1735056]

Wed, 15 June 2016 11:09

Neil Mackenzie

Messages: 131
Registered: December 2013

Senior Member

Thanks Jonas.
Maybe I could create a custom client. This client would encrypt the text files it stores in .emfstore, and then decrypt them when it loads them again. Do you think this would work? Maybe it is not so simple if there is code that uses classes which requires the actual files.
If someone goes to the effort of writing a new plugin then they can have the XMI files Smile

...I guess there are ways to prevent this also (like a custom client and server which add some small step to the connection process, so that only the custom client can connect to the server). Note that in my case the server would be on a different machine that the client users dont have access to.

Report message to a moderator

Re: restricting access to XMI from EMFStore client. [message #1735176 is a reply to message #1735076]

Thu, 16 June 2016 06:08

Jonas Helming

Messages: 699
Registered: July 2009

Senior Member

Hi Neil,

I am not a fan of "half secure" solutions, but encrypting the files
would at least make it a little harder to get the data.
However, I wonder, how you want to encrypt something locally, without
storing the secret key somewhere locally, so it is more an obfuscation
anyways.

Best regards

Jonas

On 15.06.2016 13:09, Neil Mackenzie wrote:
> Thanks Jonas.
> Maybe I could create a custom client. This client would encrypt the text
> files it stores in .emfstore, and then decrypt them when it loads them
> again. Do you think this would work? Maybe it is not so simple if there
> is code that uses classes which requires the actual files.
> If someone goes to the effort of writing a new plugin then they can have
> the XMI files :)...I guess there are ways to prevent this also (like a
> custom client and server which add some small step to the connection
> process, so that only the custom client can connect to the server). Note
> that in my case the server would be on a different machine that the
> client users dont have access to.

Report message to a moderator

Previous Topic:	emfforms spreadsheet renderer
Next Topic:	export model to xsd with referenced generator model

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 04:12:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter