COMMAND

    DIT TransferPro

SYSTEMS AFFECTED

    Solaris

PROBLEM

    Scott Smith posted following.  He was looking around for a method
    to access his MO drive in Solaris and found a program called
    TransferPro from a place called DIT.  He downloaded and installed
    the package, and just used tar to access the media since he didn't
    really need it for much else.  While fiddling with his MO drive,
    he made a typo and accidentally specified /dev/rff0a as the tape
    device, rather than rff5a, which was his MO.  It horked disk
    on target 0.  Note that tar was used as normal user.

    TransferPro package  installs a  device driver  used for accessing
    the removable media--ff is the name.   All of the devices that  it
    installs are  created with  the permissions  0666.   The ff driver
    works with normal disks, too, and that's why is possible to  screw
    up disk on  target 0.   (For some reason  the tar also  screwed up
    disklabel, hence messing up the whole disk.)  Observe:

    scott@tempe:~$ ls -l /devices/sbus\@1,f8000000/esp\@0,800000/ff\@0,0\:a,0,*
    brw-rw-rw-   1 root     sys       56,  0 Jan  4 23:53 /devices/sbus@1,f8000000/esp@0,800000/ff@0,0:a,0,blk
    crw-rw-rw-   1 root     sys       56,  0 Jan  4 23:53 /devices/sbus@1,f8000000/esp@0,800000/ff@0,0:a,0,raw

    They should, of course, be mode 0640.

SOLUTION

    The fix for this is to change the entry in /etc/minor_perm for the
    ff  driver.   At  DIT  said  that  the  devices  must  have  these
    permissions  in  order  for  users  to  access devices through the
    TransferPro application.  There are other methods, of course.