Re: [ jEdit-users ] Security problem

[Daniil V. K. <da...@vs...>]

??? ??? ????? - 4 ??????? 2001 17:03, ? HaJ...@ar... ?????:
> Hello,
>
> > Daniil V. Kolpakov wrote:
> > > Hello,
> > > I have a serious security problem.
> > > I have a unix-server on which my files are stored.
> > > The server is running samba 2.1.
> > > I connect a drive (e.g. M:) on my NT-box with the
> > > share of samba to access my files from NT.
> > > There is a directory which I own. I have also read and write
> > > access to this directory.
> > > There is a file in this directory which I do _not_ own and have
> > > no write access.
> > > I can load this file in jEdit and change it an !_store_! it.
> > > When I look then in the file properties, I am the owner
> > > of that file.
> > > It looks to me as if the original file is deleted and a new
> > > one is created instead of overwriting the file, because I
> > > cannot overwrite it with that permissions (UltraEdit complains
> > > about that). So I think it has nothing to do with samba and NT.
> > >
> > > Anybody else noticed something similar ?
> > > Any solutions.
> >
> > That's just the way jEdit saves files.
> >
> > --
>
> If you can change the contents of a file for which you have no
> permissions to write, then it seems not to be a save way to save.
> jEdit does not overwrite the original file and so it doesn't notice
> that there are no permissions. It there any reason for that behaviour
> ?

Yes, there is. When saving file, jEdit writes a new one, then renames 
this file to original - in such a case, if jEdit crashes in the middle 
of this operation (saving), you won't lose your work. However, I don't 
like it too, it introduces problems with ownership also, and I 
suggested to Slava to save file twice - copy then original, and then 
remove copy. (And I'm doing it again, Slava!) :)

-- 
Too lame to write my own MUA