alain.fischer at bluewin.ch
Mon Aug 26 20:05:47 UTC 2002
ip68-7-80-223.sd.sd.cox.net has locked
In the last weeks I have tried to restore the swiki to keep our
Squeak documentation. But now, I wasn't able to restore it.
Peraps a simple scheme that could possibly work in most case is to have
a list of ip address or range of address with editing capability
This seem to be a low cost solution. I know that it's easy to switch to
provider with other range of ip but the more work for the malicious one.
After a few week, I think the swiki will be free of these bad boys.
> 1. A single password that is possibly updated every once in a while.
> This is annoying, it has troubles with distributing the password, and
> it's probably not *real* effective, but it is a step forward.
> 2. A password per contributor, plus machinery and beauracracy to deal
> with who is allowed to post. This sounds similar to the above, but note
> that now we can detect who is making bad changes and we can kick them
> off. We have the extra cost, though, of needing an application process
> for accounts that is good enough to prevent repeat attacks.
> 3. The same as #2, but with public key encryption instead of
> This is more convenient for users, once we have a new client
> implemented. (This is where, IMHO, we should focus any Squeak-based
> efforts. Try to make it authenticate using PGP keys....)
More information about the Squeak-dev