[squeak-dev] Securing access to the .changes file
Herbert König
herbertkoenig at gmx.net
Tue Apr 18 17:59:45 UTC 2017
Hi Hari,
It seems you want to hide your sources from your users. Under that
assumption:
As I wrote in my other reply removing sources and changes still gives
very readable code in the browser.
A VM which ignores StartUpList will give anyone who has your image most
of your sources. Especially your encryption can be easily avoided from
there. Maybe there even is a tool which already loads an arbitrary image
into the simulator for debugging.
http://wiki.squeak.org/squeak/518 collects the details on deployment,
the changeset it refers to may need some rework for recent images. (In
case you didn't already know, I got the pointer from Hannes.)
Cheers,
Herbert
Am 18.04.2017 um 18:06 schrieb Hari:
> Hi Herbert,
> 'disableProgrammerFacilities' appears (from the comment) to disable
> snapshotting, which I do need to do within my client. However, I do disable
> debugger, halos, browser, workspace... selectively using a switch in my app,
> which I am looking to control using an username and password.
> Kind regards,
> Hari
>
>
>
> --
> View this message in context: http://forum.world.st/Ma-Client-Server-Squeak-launch-issues-tp4928722p4942562.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
More information about the Squeak-dev
mailing list
|