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

[Michael Weber]

On Mon, Apr 30, 2001 at 12:19:32 +0100, Simon Marlow wrote:
> > 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. 

If user X writes/modifies ./.ghci, then it gets the ownership of X,
doesn't it?

How do I trick the file system to keep the ownership of the modified
file to the original user?


Cheers,
Michael