[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::hackers_v1

Title:-={ H A C K E R S }=-
Notice:Write locked - see NOTED::HACKERS
Moderator:DIEHRD::MORRIS
Created:Thu Feb 20 1986
Last Modified:Mon Aug 03 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:680
Total number of notes:5456

251.0. ">corrupted uaf<" by ACE::BREWER (John Brewer Component Engr. @ABO) Fri Jun 06 1986 17:30

    
    	I have a corrupted SYSUAF.DAT file. Listing/Showing entries
    bombs when it hits the corrupted area, and clobbers the process.
    I have resigned myself to rentering data manually (since the 
    backup disk was overwritten before the file corruption occurred).
    
    	The one difficulty is that I cannot get user UIC's. The f$file
    lexical returns only (owner_,Username) info. I was hoping to use
    this tact on the files in the top level directory on the user disk.
    
    
    	Any hints? Again, the file corruption affected only entries
    past "B" (naturally... it couldnt happen to a "Z" entry!)
    
    	Help!
    
    	-John Brewer
    	(ACE::BREWER)
T.RTitleUserPersonal
Name
DateLines
251.1correction.......ACE::BREWERJohn Brewer Component Engr. @ABOFri Jun 06 1986 20:403
    
    	...Make paragraph 1 in .0 end as "the backup was overwritten
    before the corrupted file was discovered!"
251.23 suggestionsDELNI::CANTORDave CantorSat Jun 07 1986 04:4317
      Re .0
      
      Three suggestions for getting the numeric UICs from file
      ownerships:
      
      1.  Rename SYS$SYSTEM:RIGHTSLIST.DAT to a temporary file and
          F$FILE to get the UICs; then rename the rights list file
          back to the original name.
      
      2.  Use F$IDENTIFIER to convert the alphabetic identifier to
          numeric UIC form.
      
      3.  Use F$FILE(filename,"GRP") and F$FILE(filename,"MEM") for
          the numeric group and member numbers.  (You'll need to
          convert them to octal with F$FAO("!6OL",number) .)

      Dave C.
251.3PIP?BISTRO::HEINHein van den Heuvel, Valbonne.Sat Jun 07 1986 15:2110
    (as in vmsnotes 934.7)
    
    -	Does the corruption affect ALL entries after "B"?
    	Perhaps to file comes back to live somewhere in the
    	higher key values?
    
    -	PIP disk:[0,0]*.DIR/FU could give a list of usernames/Uics.
    
        
    Hein.
251.4corruption in computersACE::BREWERJohn Brewer Component Engr. @ABOTue Jun 10 1986 17:0011
    
    	re: .3
    
    	Yes, all the entries past "B" are corrupted ... to an extent.
    The first entry was hosed to the extent that the user couldnt log
    in, subsequent entries (in alpha order) can log in, but as a manager
    I cat LIST or SHOW them. If I try, I get logged off after exiting
    AUTHORIZE.
    
    	Strange!
    	-John
251.5copy the file ...SWIFT::PITTTony Pitt, UK CS, Basingstoke, EnglandTue Jun 10 1986 22:098
    Try writing a program to read the UAF sequentially, chucking out
    the record you know is bad - you must know which one by now,
    presumably!  Then write all the other records into another file.
    
    You might be able to recover all but one record that way ...  Worth
    a try?
    
    T
251.6PASTIS::MONAHANWed Jun 11 1986 07:3615
    	The "logging out" is almost certainly an exec mode bug check
    which deletes your process.
    
    	The suggestion in .5 is good, but it may be even easier. Try
    something like :-
    
    $ CONVERT SYSUAF.DAT /KEY=n SYSUAF.CHECK
    $ DEFINE /SYSTEM /EXEC SYSUAF SYS$SYSTEM:SYSUAF.CHECK
    
    If this works (for any "n" up to however many keys SYSUAF has) then
    you should end up with a usable authorisation file. You can run
    with the logical name set up until you are sure it is reasonably
    sane, and then rename SYSUAF.CHECK to SYSUAF.DAT.
    
    		Dave
251.7Also, CONVERT /FAST /NOSORT will sometimes fix theseMDVAX3::COARA wretched hive of bugs and flamers.Sat Nov 21 1987 21:240