Problem with .ghci (fwd)

| explicitly tell ghci that they're okay! Hand-holding w.r.t.=20
| 'insecure' file permissions has a nasty habit of becoming a=20
| nuisance in unusual cases the original authors hadn't thought of. :-(
Constructive suggestions for how to improve are welcome.
What we are trying to avoid is obvious trojan horses, where
X can persuade Y's ghci to do rm *.*. This is bad.
Simon