[Newbies] Squeak in commercial projects
Ron at USMedRec.com
Tue Mar 6 14:13:03 UTC 2007
This is not an easy question. There are a number of things that you need to
consider. First you need to decide how secure the update needs to be. If
you are not worried about security then you have a much easier job and many
more options. In general Squeak is not secure, but it is also not less
secure then many other tools that are sent to end users.
So first answer some questions.
Is your system likely to be used by people that are interested in cracking
Does your system have access to network facilities that attach to other
installations of your system?
Are you concerned that someone might try to build a patch and upload that
code to your system installations? (i.e. spyware, worms, viruses)
Are you trying to prevent users from using features of your system without
authorization? (i.e. Try before you buy?)
There are no easy answers but I do believe it is a very interesting
President / Principal Software Engineer
US Medical Record Specialists
Squeak Cryptography Team Leader
> -----Original Message-----
> From: beginners-bounces at lists.squeakfoundation.org [mailto:beginners-
> bounces at lists.squeakfoundation.org] On Behalf Of Jens Pall
> Sent: Tuesday, March 06, 2007 2:09 AM
> To: Squeak Beginners
> Subject: [Newbies] Squeak in commercial projects
> How can I use Squeak in a commercial closed source project (whole image)?
> How about upgrades? I want to be able to send an upgrade to the customer
> which only contains the changed code.
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
More information about the Beginners