I've just started playing with Seaside again, having left off back when
it was at version 0.94.
Back in the 0.94 days, the 'config' app could be password protected, via
IAAuthenticatedSession>>authenticateUser:password:
How do you password protect the current 'config' app? It's a little
dangerous to present a working Smalltalk Browser to the world from
within their web browser (i.e., the 'classes' app), and even if you
remove it, they can add it back in if they can access the 'config' app.
So, what's the easy way to lock this thing down for presentation to the
world?
Furthermore, I personally prefer the default installation to be a
"locked-down" installation. Otherwise somebody could install this thing
in their Squeak image, put their image on the web without checking
Seaside security, and from there they are toast.
Nevin
