[Fwd: Bug#94739: ./.ghci -- isn't it dangerous?]

[Simon Marlow]

> So, I think a safe solution is to ensure that the .ghci file belongs
> to the user.  Checking for decent permissions would increase security,
> but well, IMO it's the users' fault, if he creates a 777 .ghci :-P

I've thought about this a bit more.  It's not enough to just check the
owner and permissions of .ghci if the current *directory* is world
writable.  Therefore I'm thinking of backing off to the approach of
never reading ./.ghci by default.

Cheers,
	Simon