Hi Martin,

I like your idea! it's wonderful!

> I just had a weired idea, and I haven't thought that to the bitter
> end, but anyway, here is how it goes:
> If we protect the swiki by a password then the question arises, how we
> make the password known to the good guys and hide it from the bad
> guys.
>
> Now how about we put the password into the squeak image.  We could
> even hide the password in some sort of smalltalk "riddle" that even a
> novice squeaker could solve, like <<create an instance of the Password
> class, send it the message #august and inspect the instance variable
> "password">>. The riddle could be changed from time to time and the
> current riddle could be published on the list. The required classes
> could be updated by the usual update mechanism if neccessary.
> A potential intruder would have to download squeak and learn a bit of
> smalltalk to play with it. Chances are he figures that this is more
> rewarding than hacking a swiki, or he may simply fail.

Here someone can think that in this case, we run the risk to create a hacker
that now knows Smalltalk!! :-)
But I still think that is better to give him a chance.

Diego Coronel