Hi Gerard.
>> The most damage you can do when running anything as a
>> non-privledged user is to that user's own files.
> Yes, but ...
> I remember a silly script I tried. It was a recursive
> script that was creating a directory, then moved itself in
> that directory, then run again ... and again.
> The result was a deep tree of directory (thousands!) and I
> never manage to delete it. It ate all free inodes on the
> disk partition. I tried several remedy like debugfs, shell
> script or binary executables, none success. So now, I learn
> to use quota to set boundaries for a user ;-)
Assuming /dud was the root of the problem partition, d you try
the following:
Q> find /dud | sort -r | xargs -s 99999 rm -fr
That starts at the bottom of the tree and prunes it up towards
the root, so shouldn't ever be able to fail...
> Morality: Although it was a process running with
> non-priviledged rights, it damaged the whole partition
> (filling and locking the free part).
As the old saying goes, "Unix gives one enough rope to shoot
oneself in the foot"...
> Be aware of security hole!
What security hole?
Best wishes from Riley GM7GOD / KB8PPG.
---
* God Made 7 Greedy Old Devils
* Kilroy Bought 8 Personal Pregnancy Guides
