Re: disk-destroyer.c

From: Khimenko Victor (khim@sch57.msk.ru)
Date: Sat Jul 22 2000 - 11:09:09 EST


In <Pine.LNX.4.10.10007211109230.13659-100000@master.linux-ide.org> Andre Hedrick (andre@linux-ide.org) wrote:
> On 21 Jul 2000, Henning P. Schmiedehausen wrote:

>> There is simply no point in hiding anything from root.

> I am not hiding anything, you as root must make a choice to expose full
> unrestricted access to the hardware or filter for correct usage.

It's policy. Policy does not belond to kernel. Period.

>> What I tried to understand in between Andre's swearwords, is that you

> Sorry, but this is very serious to me (fist fights not excluded to win).

>> can enable drives to access a full set of parameters ("taskfile") or
>> you can disable this. If you enable it, you can fry the drive. If you
>> disable it, you can't but you can still use the regular ATA command
>> set which is all that the kernel will ever need.

> You only need access to the commands that are used and described in the
> ATA-ATAPI specification.

No. You :
  1. need access to hardware (if you have CAP_SYS_RAW) and then you'll have FULL
access to hardware
 or
  2. do not need access to hardware at all and removed CAP_SYS_RAW from system

If you need filtering - feel free to implement it in libata.so ...

> You do not need to send commands to the drives that violate the standard
> making :

Huh ? Why not ?

> LINUX NON-ATA-ATAPI COMPLIANT!

This is bold accusation and if we'll get such accisating then we'll have to
point out that:
  1. DOS is non-ATA-ATAPI compliant
  2. Windows9X is non-ATA-ATAPI compilant
  3. WindowsNT/Windows2000 pro is non-ATA-ATAPI compilant
  4. Probably any other OS for PC out there are non-ATA-ATAPI compliat as well

All of above is right when you are superuser in system (Administator in
WindowsNT/Windows2000 case) in default configuration - just like Linux case.
For 1., 2. and 3. I know peoples who will be able to do working .VxD and .SYS
files to make ubuse of IDE/ATAPI drivers possible (I can try to find peoples
who will be able to do the same for FreeBSD, Mac OS, BeOS, etc if needed).
Then we'll have simple fact: if you are used your IDE/ATAPI drive in PC with
[almost] any PC OS you used it with non-ATA-ATAPI compilant and thus lost
warranty. I think on this stage general public can be notified and then
manufacturers will have BIG pressure to change specification.

> Here is a good phrase.

>> The question now is: Once you disabled this, you can't enable it
>> again? If this is truw, then I can understand many of the strange
>> words that Andre used (though I still think that he was/is under deep
>> sleep deprivation and strong drugs). If you can reenable this access,
>> then there is no point.

> I do take strong drugs to keep me from getting hyper.

> The access decision is made at compile time.

And any such decision made at compile time can be changed in run-time via
clever poking in memory. I know how to do this with Windows9X/NT/2000pro
and Linux (at least).

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:19 EST