Add upstream documentation --- /dev/null +++ b/bootdisk.html @@ -0,0 +1,548 @@ + + +Offline NT pw & reg-editor, bootdisk + + +

Offline NT Password & Registry Editor, Bootdisk / CD

+
+

+I've put together a single floppy or CD which contains +things needed to edit the passwords on most systems. +
+

+The bootdisk should support most of the more usual disk controllers. +You most likely have to select "d" to auto-load the drivers, it should +then detect PCI based hardware. For ISA hardware, you have to load manually. +Both PS/2 and USB keyboard supported. +

+Tested on: NT 3.51, NT 4 (all versions and SPs), Windows 2000 (all +versions & SPs), Windows XP (all versions, also SP2), +Windows Server 2003 (all SPs), Vindows Vista 32 and 64 bit. +

+DANGER WILL ROBINSON!
+If used on users that have EFS encrypted files, and the system is XP +or Vista, all encrypted files for that user will be UNREADABLE! +and cannot be recovered unless you remember the old +password again
If you don't know if you have encrypted files +or not, you most likely don't have them. (except maybe on corporate systems) + +

+Please see the Frequently Asked Questions +and the version history below before emailing questions to me. Thanks! +

+Also take a look at Grenier's DOS port +

+ +How to fix it if you lost your admin password for your +ActiveDirectory. Thanks to John Simpson. +

+Other ways to recover lost password etc at +MCSE World +

+


+

How to use?

+Yes, long text. Please read it all and the FAQ before mailing me questions +

+If you have the CD, all drivers are included. If you use the floppy, +and you need the SCSI-drivers set, either prepare a floppy with +the scsi-drivers .zip file unzipped (in \scsi), or put a selection +of the drivers you need in the \scsi folder on the main floppy, +there should be enough space for maybe a couple of drivers. In the latter +case you don't need to carry around and swap floppies. +

+

Overview

+
    +
  1. Disk select, tell which disk contains the Windows system. + Optionally you will have to load drivers. +
  2. PATH select, where on the disk is the system? +
  3. File select, which parts of registry to load, based on what you + want to do. +
  4. Password reset or other registry edit. +
  5. Write back to disk (you will be asked) +
+DON'T PANIC!! - Most questions can usually be answered with the +default answer which is given in [brackets]. Just press enter/return +to accept the default answer. +

+ +

1. DISK SELECT

+Which disk contains your Windows system? +

+

+=========================================================
+. Step ONE: Select disk where the Windows installation is
+=========================================================
+Disks:
+Disk /dev/sda: 2147 MB, 2147483648 bytes
+NT partitions found:
+ 1 :   /dev/sda1    2043MB  Boot
+
+Please select partition by number or
+a = show all partitions, d = automatically load new disk drivers
+m = manually load new disk drivers
+l = relist NTFS/FAT partitions, q = quit
+Select: [1] 
+
+ + +

2. HOW TO MANUALLY LOAD DRIVERS

+Try auto-probe (d) first, only do this if you have to manually +try to load some or all drivers. +
+Select: [1] m
+==== DISK DRIVER / SCSI DRIVER select ====
+You may now insert or swap to the SCSI-drivers floppy
+Press enter when done: 
+Found 1 floppy drives
+Found only one floppy, using it..
+Selected floppy #0
+Mounting it..
+Floppy selection done..
+SCSI-drivers found on floppy:
+
+1 BusLogic.o.gz
+2 aic7xxx.o.gz
+3 sym53c8xx.o.gz
+[ ... ]
+
+SCSI driver selection:
+  a - autoprobe for the driver (try all)
+  s - swap driver floppy
+  q - do not load more drivers
+  or enter the number of the desired driver
+
+SCSI driver select: [q] 
+
+ + +
+SCSI driver select: [q] a
+[ BusLogic.o.gz ]
+Using /tmp/scsi/BusLogic.o
+PCI: Found IRQ 11 for device 00:10.0
+
+[.... lots of driver / card info ...]
+
+scsi0: *** BusLogic BT-958 Initialized Successfully ***
+scsi0 : BusLogic BT-958
+  Vendor: FooInc   Model: MegaDiskFoo  Rev: 1.0 
+  Type:   Direct-Access                      ANSI SCSI revision: 02
+
+[ ... ]
+
+Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
+SCSI device sda: 8388608 512-byte hdwr sectors (4295 MB)
+Partition check:
+ /dev/scsi/host0/bus0/target0/lun0: p1
+Driver BusLogic.o.gz loaded and initialized.
+
+
+ +

+ +

3. PATH AND FILE SELECT

+Where's the Windows system located? +

+On the selected partition/disk, the main files for windows can +theoretically be anywhere. And we must find the registry files +to be able to edit them. There are however some usual places: +

+These usual paths will be checked, and if found, they will +be suggested as the default. +

+

+Selected 1
+Mounting on /dev/ide/host0/bus0/target0/lun0/part1
+NTFS volume version 3.1.
+Filesystem is: NTFS
+
+=========================================================
+. Step TWO: Select PATH and registry files
+=========================================================
+What is the path to the registry directory? (relative to windows disk)
+[windows/system32/config] : 
+-r--------    1 0        0          262144 Jan 12 18:01 SAM
+-r--------    1 0        0          262144 Jan 12 18:01 SECURITY
+-r--------    1 0        0          262144 Jan 12 18:01 default
+-r--------    1 0        0         8912896 Jan 12 18:01 software
+-r--------    1 0        0         2359296 Jan 12 18:01 system
+dr-x------    1 0        0            4096 Sep  8 11:37 systemprofile
+-r--------    1 0        0          262144 Sep  8 11:53 userdiff
+
+Select which part of registry to load, use predefined choices
+or list the files with space as delimiter
+1 - Password reset [sam system security]
+2 - RecoveryConsole parameters [software]
+q - quit - return to previous
+[1] : 
+
+ +

+We select 1 to edit passwords.. +

+

4. PASSWORD RESET

+Everything is set and ready, let's roll! +

+ +

+=========================================================
+. Step THREE: Password or registry edit
+=========================================================
+chntpw version 0.99.2 040105, (c) Petter N Hagen
+
+[.. some file info here ..]
+
+* SAM policy limits:
+Failed logins before lockout is: 0
+Minimum password length        : 0
+Password history count         : 0
+
+<>========<> chntpw Main Interactive Menu <>========<>
+
+Loaded hives: <sam> <system> <security>
+
+  1 - Edit user data and passwords
+  2 - Syskey status & change
+  3 - RecoveryConsole settings
+      - - -
+  9 - Registry editor, now with full write support!
+  q - Quit (you will be asked if there is something to save)
+
+
+What to do? [1] -> 1
+
+===== chntpw Edit User Info & Passwords ====
+
+RID: 01f4, Username: <Administrator>
+RID: 01f5, Username: <Guest>, *disabled or locked*
+RID: 03e8, Username: <HelpAssistant>, *disabled or locked*
+RID: 03eb, Username: <pnh>, *disabled or locked*
+RID: 03ea, Username: <SUPPORT_388945a0>, *disabled or locked*
+
+Select: ! - quit, . - list users, 0x<RID> - User with RID (hex)
+or simply enter the username to change: [Administrator] 
+
+

+Here you can enter the username you want to reset the password for. +NOTE: It is case-sensitive, write it exact as listed (without the < +and > of course) +

+Or if the name uses some characters that cannot be displayed, enter +it's ID number (RID), like this: 0x1f4 would select administrator. +

+We select the default, which is administrator. +

+

+
+RID     : 0500 [01f4]
+Username: Administrator
+fullname: 
+comment : Built-in account for administering the computer/domain
+homedir : 
+
+Account bits: 0x0210 =
+[ ] Disabled        | [ ] Homedir req.    | [ ] Passwd not req. | 
+[ ] Temp. duplicate | [X] Normal account  | [ ] NMS account     | 
+[ ] Domain trust ac | [ ] Wks trust act.  | [ ] Srv trust act   | 
+[X] Pwd don't expir | [ ] Auto lockout    | [ ] (unknown 0x08)  | 
+[ ] (unknown 0x10)  | [ ] (unknown 0x20)  | [ ] (unknown 0x40)  | 
+
+Failed login count: 0, while max tries is: 0
+Total  login count: 3
+
+* = blank the password (This may work better than setting a new password!)
+Enter nothing to leave it unchanged
+Please enter new password: *
+
+

+Some information is displayed. Also, if the account is locked, you +will be asked if you wish to unlock it (not shown here) +

+We go for the blank password option (*) WHICH IS HIGLY RECOMMENDED +over setting a new one. +

+

+Please enter new password: *
+Blanking password!
+
+Do you really wish to change it? (y/n) [n] y
+Changed!
+
+
+Select: ! - quit, . - list users, 0x - User with RID (hex)
+or simply enter the username to change: [Administrator] !
+
+

+! brings us back to the main menu here. +

+

+
+<>========<> chntpw Main Interactive Menu <>========<>
+
+Loaded hives:   
+
+  1 - Edit user data and passwords
+  2 - Syskey status & change
+  3 - RecoveryConsole settings
+      - - -
+  9 - Registry editor, now with full write support!
+  q - Quit (you will be asked if there is something to save)
+
+
+What to do? [1] -> q
+
+

+

5. WRITING OUT THE CHANGES

+Everything has been done, time to commit the changes. +

+

+
+Hives that have changed:
+ #  Name
+ 0   - OK
+
+=========================================================
+. Step FOUR: Writing back changes
+=========================================================
+About to write file(s) back! Do it? [n] : y
+
+

+THIS IS YOUR LAST CHANCE! If you answer y here there will be a +write to disk! +

+

+Writing  sam
+
+***** EDIT COMPLETE *****
+
+You can try again if it somehow failed, or you selected wrong
+New run? [n] : n
+
+
+

+That was all. +

+Please answer n here and then reboot, CTRL-ALT-DEL. Remember to remove +the floppy or CD. +

+

+ +

What can go wrong?

+Lots of things can go wrong, but most faults won't damage your system. +

+The most critical moment is when writing back the registry files to +NTFS. +

+The most common problem is that the computer was not cleanly shut +down, and my disk won't write correctly back. (it says: read only +filesystem). If so, boot into Windows Safe Mode (F8 before windows +logo appears) and shut down from the login window. +

+Also, see the FAQ for help with other common problems. +

+For linux-knowledged people, you may do things manually if the scripts fail, +you have shells on tty1-tty4 (ALT F1 - ALT F4). +


+

+

Bootdisk history

+

+2007-04-09 +

+

+2005-03-03 +

+

+2005-03-03 +

+

+(earlier history removed)
+9705xx +

+
+

Download

+

+Note: Some links may be offsite. +

+

+ +

+Previous versions may sometimes be found here (also my site) +

+

+NOTE THAT THE BOOTDISK CONTAINS CRYPTHOGRAPHIC CODE, and that it may be +ILLEGAL to RE-EXPORT it from your country. +

+ +

How to make the CD

+

+Unzipped, there should be an ISO image file (cd??????.iso). This can +be burned to CD using whatever burner program you like, most support +writing ISO-images. Often double-clikcing on it in explorer will pop +up the program offering to write the image to CD. Once written the CD +should only contain some files like "initrd.gz", "vmlinuz" and some +others. If it contains the image file "cd??????.iso" you didn't burn +the image but instead added the file to a CD. I cannot help with this, +please consult you CD-software manual or friends. +

+The CD will boot with most BIOSes, see your manual on how to set it +to boot from CD. Some will auto-boot when a CD is in the drive, +some others will show a boot-menu when you press ESC or F10/F12 when +it probes the disks, some may need to have the boot order adjusted +in setup. +

+ +

How to make the floppy

+

+The unzipped image (bdxxxxxx.bin) is a block-to-block representation +of the actual floppy, and the file cannot simply be copied to +the floppy. Special tools must be used to write it block by block. +

+

+

Or from unix:

+dd if=bd??????.bin of=/dev/fd0 bs=18k +

+

How to make and use the drivers floppy

+

+NOTE: Not all files will fit on a floppy, so leave out what you +think you do not need! +

+

+


+

+

Bootdisk credits and license

+

+Most of the stuff on the bootdisk is either GPL, BSD or similar +license, you can basically do whatever you want with all of it, +the sourcecode and licenses can be found at their sites, I did not change/patch +anything. +

+The "chntpw" program (password changer, registry editor) is licensed +under GNU GPL v2. COPYING.txt +

+Stuff I used, big thanks: +

+

+


+

+ +

+


+
070410, pnordahl@eunet.no
+ + --- /dev/null +++ b/faq.gif.uu @@ -0,0 +1,125 @@ +begin 644 faq.gif +M1TE&.#EAS`%!`-4``)B8F*#=ZGIZ>PG-ZD;!VJBHJ`O9]*O@[`6\W"FZUEC% +MVQFWU0O5\0G+YV#(WC6]UPNTU5V6H`?"X0K0[8S6Y05@SPB5YB`:_WH#3Y#4U-<#`P`?%XVFSP`>A +MO`S<]P(O-SV,FC>VSP5^D1FNRP>OS$JVR6)G:6O,X"2RS4&AL23`V12TU'S0 +MX@1#3AV'G`6YV0FVT`_`W`2WUPC(Y@```"'Y!```````+`````#,`4$```;_ +MP))P2!3&2)FD!PFQ8KH-+&@R5PL\+A\ +M3J_;[_B\?L_O^_^`@8*#A(6&AXB)BH@7&1H%:I%"`!H5%BXSF1V;G)V>GZ"A +MHJ.DI::GJ*FJJZRMKJ^PL;*SM+6MF3,N%A4:`))I`"0AF!TLQA[(R+:QBP=N2$DOK]#`B0Y,\4>!`0*]O?X^?K[ +M_/W^_P`#"AQ(L*#!@P@3*ES(L*'#AQ`5TO-@;D8.$@+8E0B60UX]!S)D8!A) +MLJ3)DRA3JES)LJ7+ES!CRIQ)LZ;-FSASZMS)LV?-_Y`.%!"@V.'BND@OW[^``PL>3+BPX<.($RM>S+BQX\>0(TN>3+ERX[P41K05 +M&E>=&@TAZLJX@9?O@=.H4ZM>S;JUZ]>P8\N>3;NV[=NX<^O>S;NW[]_`@^?F +MNX'"#1F<.X30D"9&A1DL/-C%4#J`\.O8LVO?SKV[]^_@P]?>6WPSQ1D5SA`1 +MD,%"!^D.,#C5:UV\_?OX\^O?S[]_;_*981"4!QU8D,%1!;P#G72CX47?7OY% +M*.&$%%9H885]87:<`N==!/])"?`4!VXD-Y&[<4#WVA..9C7D$06:>212":IY)),-NGDDU!&*>645%9IY958 +M9JGEEEQN^=0(-G)XCH$`A+B@`B4VI=::;+;IYIMPQBGGG'36.59389ZGXQ$7 +M8!(=FB+=T-2@A!9JZ*&()JKHHHPVZNBCD$8JZ:245FKII9AFJNFFG'9*Z`UM +M#L\<8<=^RQ0PI'[((-O#9L@PV_/A`L/2RW[/++ +M,,\@`T0,.WTTU%+K?;:;+?M]MMPQRWWW'37;??= +M>.>M]]Y\]^WWWX`'+OC@<8M]245V[YY9AGKOGF +MG'?N^>>@AR[ZZ*27;OKIJ%O..-F(-_S"V8PW#CH,)]1N__OM)T20^NZ\X)\]"[\PG0/L)PEN>/.X@-"\Z"\1;K[WJJY/]@MF*GQS[ +M^.27;_X)!0"@_OKL_V#^^_#'+__\]-=OO_P<%.`<^>F_<[_\("A`^MA'0`"L +MX'\(3"#]T`<`%<2/!0(L(`%C,`,%6M!^,$B?^R[(P0[>[W"*8]KKPG>R$IKP +MA"@\(0@`((`8:."%,'SA#U)(PQK:\(8XS*$.=WA##@`@`Q4X80$$\(,+\-"& +M"TB?"V,(PQ@(@#T6.*(4IXC#%6I`!3;,GP"8V,0GDB"(5`RC#B%(1#&:\8Q2 +M5!P$OM>K#WQ`C7",HQSGJ,85QO_@!RK(HQ[U2,<^^O&/@`RD(`=)2,7Y$(AQ +M'&(1"]E',N)QCWK$@1,1RK)Q!.]U9@`B\@)7TY&T9O_"LWE-KOY@0!Z5)OT%,`%6'G.CJZ3E0'L:$*A^<20VC2A-4VI2@&J +MU'Y2U(U!Y>=-84K5;*ZRJEBM)DVWZ<,G>O6K3]1`"]P(08."]:O.825)S_I5 +M(,I3D1AUZP>2.$2V?A4'K*RK79\8`[Q^H*M/E.M"/\#"#(PUF^C[@5\K"E>N +M9E2>.;7K2S_:V(T*,`,_T*@;&;C7L.[THY'=ZV2W.=ALTG2KV1QL63O;0LTF +MU:QGE2M1GWC1FC(3JNECK08^J]>]]A6HN;6K7+.:5:;UX+@]^`!RE\OLP'$SR)[T8I>\N3SN$$E@WQ_@]P??I41VY=L#9!X7!"WT+G61J\$+O+<' +M[GUO?+_+AOYB-[H05N2";8I'%"RW?_WE[A85#-X0@Q+#TV6N@8^;XAYD\L#, +M?/"*2]S?_S(X&!;.;'N'B%GLPOB*^L6Q?46L`07OM\;E#3)_+4S@!SMYN2TV +MK@YZH(,J'W?*4V8NEJE84MI`$(QDSF%028!#BX@)K7?($5;#&Z.O`A +MFMG,9C<3DRRC9@X0]>P%P(MF'+7*9RAO^WN`(RF]JF0*RRI`V]YBI;=,HCU9^. +MKZQ?(C;:T6\^\Z3U[&8@6SG+6#8PEK/L8F96.9/`OO*49QR,7=/YT5QF-*LI +M/>4\J_G8,=:!M'$-9$MG%M=_7K2MI^WA0`-:U,1&+JB]/.62O0#0\(ZWO.<- +MYH,6$-)QSJB\D9WO5,N[`YIVM2+GW>\*"#S<\HXOMJ](<&2*NXC_#GC!X>WP +M*O^2!"V`=V(-3O#92E!]P%2UO@E^<$B7=;N*CG?%X\UOA>_;V`V_],L9K@-^ +MR[OB+H\WP!&^\HX/'-#\[CG082YT5TMI1MWK6IR[_]2Z#>8E,_('5XWMU0-.`ORJ0NIP-?G6N.S+JKZ9ZE\>>4;@/ +MG.MS5S@"H%OULB,`F5$'_-9++G(@9OWA%]`ZP&.@@K8GD8@HT'K7JPY-L#/1 +MB<",^MJQ?GBL0U,#-%`D#MX-[\"S)_&`GGK+1RYWJ_.[\U,'?.NECNR]&QOV +MB%=[,-B.=QV\W?1NF+S<`6W1K=N>YBOW>]`O7?627YW'J.=\WV%O?*E/?_B3 +M=WH&H*[U[GO_^^#OOAT?Z4FZ&_[[+E!SY!%0RU*?>LSH(Z+5BQ]^LB.`_N"W +M_]?%_/X`YM+J@N=]]&=_6A>`"*!IZX<`&90!.!!^BJ=(GI1'DI1Y_^Q7)N[W +M?C!@`_.G5_S5`@[X=RUT@:=F78U7@>?W?9GT@08H?LSD>BT8?H+7?OWW.XI4 +M@"$X@S```1LH?RQX10#X?^"7@B!81."'?T,4`R)H:BR@@Q_8A.&G?=SGA%*H +M=4)8?W7GA(#U<>J3!%:7`#5HA>?W>_EWA?7V<>ES7>NW@EWXA03X@T1(A>Y0 +M`5KG0S_@@1\HAM_'9W*(`"=@4%HH`!:``%X85BH0A3#H57^H6.:WARCX@H?X +MAHWH@\=7@N`7@WZHA5QH=6:EA3&P`X+XA53X@FKH@I(XBH,H=IJ(B!_7B5/8 +MBE`H`K`8B[(XB[18B["82;8(B_&5B[+85?]<%$.8U0*P>(JYN(LB0(RV:(Q? +M]XLOQ%\5$(O(5(O(:(S0F$NRN``LI`*PF$1WQ(O#J$C%F%&PZ`*6QT1\I8V# +MV%H[X(U'R(PR]`,HH(OB6(NXF(O12(_,=(OY:(OWZ(ON&(RQ2`/NB'E?=(S@ +M*(OU>(^TF)#62(O(*`("R8P$^8S>6)&S^(H6F9'Z>$6\2(T=&0R=%($J@`/" +M^(U$%(Y`9)(_@)(4.7XBF4<4"8L**8O3.(_56$2SR`&0)P(9E%D5^9"T2(TH +M@`,B^5\&N468UP&\R&,O.9+Q*(\IB8\<:8\-N9#[6(^UV(\@^9(D.8L70)01 +M>&)'N9((N8\S69;_4WF6*BF+7RF28JF1%@F%$C"7=%F7$B`"=8F7=KF7$I!) +M>:F7=QE??+F7@CF8=GF*>7F7%F8?FF8=HE,?/D`BA28&369N627 +M+$`)%2`!&O0"@PF8Q'B7>HF7(E"8DBD!,Z!I$F"9MH9?-,`#C@F:FTF7@*F8 +MBJF:NMF7S"29E,F7N.B;5V28P!F=P7F8 +ME[F:<]F<*C"7RYF8N+F:NU>>STF8F?F:V)5"\"7_6F@^[F7_^?I +MH+6IG7Y9H.9)GP\ZEY$YHB#JH?39H=H)A28PERW:HA)@ +M`B]*ES(*HRY*HS%*G"I@HS):E_$UHS:*H[44`L#B-AW``RT*FR3@`FXCF":@ +MI$S:-DX*9AHP`V^3``M0H\C$HS&*GRTZI&+3HL'YHB:`8#&0/W4(HSU:HSD* +MGT04HS7:HQ+@I#4`-_25GR#Z`A,H`#1`IC(Z1!JP`D7:-C,`HT/:`6W3AU>T +MIFPJIJ0VJ&JCJ`-*I5;:-ELZIV42&F]SI#E:IV\CJ4^Z7TQ:J#H:HX`JJ(G* +M3']ZFXWJI2WJJ6XCJ3E`EM:I%U*L\ +M8%!WU`/%6J.NZJO$&E52=5VA2D1QR@M/%`%96J.;*%`D8*S8ZDZJ*JQZE:S^ +MVDG6VJ_N=$?,:@+?*K`'F[`FL$\#BP,FX*Q>E2`R&JPF$+!21;`9RZV]NJX0 +MBTX_)+'I6K*\NJL^8`(IJ[(RZ@,KVZLOVZL8&[,U^J,I2[-Q.@.LE6@K&P&8 +MUUE`U+,_RU9W!&DRR@,MQ%I`M*U%A+.NJK->M;0=.ZXLR[(Z2402N[):RZL^ +ML*Z]VJZP=5;750'Q^@/_O(H"Z\6G-4H#0VM79BNC4*M;.]JR-.NSK-6!1YNT +MHH5'-1JWG=6TPQJV8,5?%R"C=DM;%_NOA[M7>#NUA?NQBE2S@OM5A/NK.$NW +M+9NY*ZM].^"RGONYH!NZHNNY-'!AH^NR*X!=%7"ZH&L@.89=%^"Y/(`#.39) +MJ^NRL_NZ*H`"G^L"*O"ZF>6YX16[H3L#2^:YKJNZ+CN\HNL!90*/K/NYQHM= +MIYNZP>L#I?NZMSN]/Q"Z//"[V(4#/."R%0"\W>NY.=!C.:8"K)N[V05*XG6[ +M+NN[KXL#.O"YR9MCQ.L#UFMAAB6[M)M=+IN][.L#[IMC\LN\Q7N\J/NZ_QN] +M_Q`_=$"[72^@,X@7=(F?=(HG=(JO=(LO=([0D\D<`$,P``3,-,S7=,U?=,Z +M;=,\S=,YO=,^_=,WGW57TW6:*W4.-W54=W64-W56:W6:3W5 +M1.W68)W76QW7:#W61LW59IW5?MW73>W6AKW78OW55\W50(W7.5TJ'U("[+$# +MA%W9EGW9F)W9FKW9G-W9GOW9H!W:HCW:I%W:IGW:G#W!&4$$SH':KOW:L!W; +MLCW;M%W;MGW;N/W2:X!QFFT`/.W;#`#[-W> +M[OW>\!W?\CW?]%W?]GW?^)W?^KW?_-W?_OW?`![@`C[@!%[@\UTJ1X$&/X0" +M!M[@_P[^X!`>X1(^X11>X19^X?K-*PF>!NS!X!C^X2`>XB(^XB1>XB8^X+RR +MVK_0X2FPWBVNWB^>`C(.XS,.XP8PXS&>XS*^XRU>XSQ^XS2^XR[NXSU^XT)> +MXT9NY#_.XS\.Y$(>Y$FNY#H>Y5*NY$[.Y#@.Y%*>Y5C.Y%M^Y"^^Y3;^Y$U. +MXU"NXST>X^RMYF6>YDC^YDV^Y%KNXF.>Y&&^YCA>Y%;NYGF.YGMNYG8^YU4^ +MY'+.YED>Y'WNYEJ^Y&&>YS9NY7/>Z"FN$4+@#A?0Y9B>Z9J^Z9S>Z9[^Z:`> +MZJ(^ZJ1>ZJ9^ZJB>ZJJ^ZJS>ZJB^H)0^!,&0Q*Y>Z[9^ZW6XGNNZONN\WNN^ +M_NN8W@#DO>&43@DR7,2F;,B9?,J#O,I6S.Q>?,A1S,F8+,IF[.QQ+,<_G.S2 +M/LK53LK3WNV?3,78CL;AONRI#,>KC.T3W`NQWAQD$._R/N_T7N_V'@7FF^_Z +3ON_\WN\Y=N\`C^\.S%WL$`0`.P`` +` +end --- /dev/null +++ b/faq.html @@ -0,0 +1,343 @@ + + +Offline NT pw & reg-editor, FAQ + + +

+
+ +Last update: 080526 + +

+

+The changes does not take effect.
+I get some errors like "read-only filesystem" and such. +

+
    +
  • The current version does not like to write to the NTFS filesystem if +windows was not shut down cleanly. +
  • Shut down windows from the login page, or from the start menu. +
  • If there is no way to shutdown from the login-page, try this: +
      +
    1. Boot windows into Safe Mode (press a lot on F8 before the + windows logo screen appears) +
    2. The login screen in safe mode should usually have a shutdown + option, so shut it down! +
    3. You may have to do this TWICE! quite often.. +
    +
+

+

+Why can't I access my encrypted (EFS) files after resetting the password? +

+
    +
  • Because in XP and possibly later service packs in win2k the +password itself is used to encrypt the keys needed for EFS. +
  • Sorry, there is no way to recover the files once the +password has been reset. +
+

+

+The .bin-file inside the .zip won't fit on a floppy. +

+
    +
  • You didn't read the bottom of the bootdisk +download page +
  • Click on the install.bat after extracting the .zip file, +and follow the on screen prompts. +
+ +

+ +

+The keyboard does not work! I can't answer the questions!! +

+
    +
  • If you have a USB keyboard either your USB controller or your +keyboard is not supported with the rather generic drivers I use. +Nothing I can do at the moment, sorry! Try a PS/2 keyboard if possible. +
  • If the keyboard is PS/2 and won't work, I do not have a +solution. Sorry. +
+

+ +

+When loading the floppy it stops with "boot failed." +

+
    +
  • Bad floppy. Or bad bootloader (some versions are known to give up +easy) +
  • Use another floppy or a new version of the ldlinux.sys file (go +allthewebbing for it for instance. grab one from a linux distros +bootdisks. I did.) +
  • Or get the CD image from the download page. +
+ +

+

+ I have the CD in my CD drive, but it starts on the haddrive. +

+
    +
  • Check your BIOS manual on how to boot from CD, or if the CD-ROM is +on a SCSI-card, check the cards manual. +
  • For those of you without manuals: Try hitting ESC or F10 or F12 +for bootmenu right after the RAM-count. +
  • Or enter BIOS setup and change the boot order. Either you can +figure that one out from the menus, or you really need the manual. +
  • I don't remember when BIOS-folks started implementing the CD boot +(El Torito) standard, but it was around 1995? Older computers won't CD boot. +
  • But BIOS-programmers never actually READ the bloody standard, so +you may have a buggy one that only boots some CDs. +
  • If it boots (first banner page), the same problems as for the +floppy may show, please read on.. +
+ +

+

+The floppy stuff crashes with "VFS: Unable to mount root.." and panic etc. +

+
    +
  • The are several ways of getting the size of the memory out of the +BIOS at boot. +
  • It probably selected the wrong one, and 16MB is a bit too little. +
  • Strangely, this most often happens on big brand machines, like +Compaq and DELL. +
  • At boot, hold down LEFT SHIFT key until "Boot: " prompt appears. +
  • Then enter: +
      +
    • boot mem=128M +
    +
  • but substitute with how much memory you have (or a bit less to be safe) +
  • If this doesn't help, there is probably not support for your +motherboard, CPU or BIOS. +
+ +

+

+It cannot find any NT disks or paritions. +

+
    +
  • Some controllers require more than one driver. Usually the +auto-load should take care of dependencies, but it does not hurt to +try auto-load (d) again. +
  • It's either caused by unsupported controller or filesystem driver problems. +
  • See next questions.. +
  • Please don't ask about inclusion of new drivers. I'm often short +on time, get lot's of mail, and it's difficult to put in things I +cannot test. +
  • If you really insist on asking for new drivers, you must at least +provide me with correct info on controller card or chip brandname, +type, model etc, and a link to website(s) with drivers for linux. +If there also are docs for using it on linux, I need that, too. +However, as I get a lot of mail, I cannot guarantee an answer or that +your needed driver will be included. +
  • There are however several other things to try: +
      +
    • Try to build Grenier's DOS floppies +
    • Move harddisk to another machine as secondary, then try + Grenier's chntpw.exe +
    • Install new NT/2k/XP in another dir than \winnt etc, then login + with new install to access the old ones sam file. Either rename it + (will leave admin with blank pass) or use chntpw.exe on it. +
    +
  • You could boot a live linux CD + (like Ubuntu or others), it + will allow access to the windows disk. Then run the "chntpw.static" + program included in the source zip file on the source download page +
  • Or why not look at +The password recovery page at MCSE World +
+ +

+

+How to load a 3rd party driver +

+
    +
  • There is a menu selection for it. Put file(s) drivers*.zip + on a floppy or on a USB stick (may be a different one from the one + you boot from). The zips should contain *.ko files. The files will be automatically unzipped and ready + for auto-load or manual menu selection. +
  • I do not know how easy or difficult it will be to actually get the + drivers to load into my kernel. There may be versions incompatibilities. +
+

+ +

+It hangs when mounting the windows disk +

+
    +
  • Hangs when it says something like "NTFS volume version 3.xx" +
  • If there is disk activity, just wait. Took more than 10 minutes in + one of my tests once. +
  • If there is no disc activity, what a few minutes, then reset and + try again. +
  • If it still hangs, try to boot windows into safe mode first, then + shut down etc. See other faq entries about that. +
+

+ +

+It seems to change the password, but NT won't agree. +

+
    +
  • The NTFS code wasn't that great after all (probably didn't write +things properly) +
  • My code wasn't that great after all. (it didn't change or changed +in the wrong place. The V struct is still marked "here be dragons..") +
  • Try blanking the password instead (menu selection 1), this +may straighten things out. In fact, reports indicate: BLANKING RECOMMENDED! +
  • If it still won't work, see the previous solution. +
  • Blanking will probably be the only option in newer releases. +
+

+ +

+

+I'm told that the account is locked, even if I know it is not. +

+
    +
  • Ok, then the code to identify lockout is not good enough. Sorry +for that. +
  • Happens sometimes when there are failed logins on a user, even if +it is not in fact locked out. +
  • Just ignore it, you may still clear the password if you wish. +
+

+ +

+

+I'm not told that the account is locked out, even Windows says it +is. How can I reset it? +

+
    +
  • Oops, probably more to the lockout stuff than I know about. +
  • You can try resetting it (selection 4 from the user menu), but it +may not help. +
  • May have something to do with Security / Group policies, which +editing of is not supported yet. +
  • Unless you'd like to play with the registry editor yourself and +figure it out. I cannot give lessons in registry edit. +
+ +

+

+The user promotion (putting user into admin group) did not work: I +cannot log in! +

+
    +
  • Some users (like Guest often) are prevented from login by +"Security policies". Does it say something like that when trying? +
  • Sorry, but my program cannot change policy settings. (yet?) +
  • It does not even know how to check them. +
  • Sorry, nothing to do.. +
+ +

+

+The user promotion (putting user into admin group) worked, but I +cannot put user back into other groups in windows! +

+
    +
  • This is known to happen sometimes. +
  • Try the local user part of "computer management" in +"administrative tools", it is more detailed than the stupid control +panel applet. +
  • But that may not work, either. +
  • Sorry, have no other known workarond. I told you it was experimental! +
+ +

+

+

+I tried it on Win2k/2003/2008 PDC (Active Directory), and it didn't change the password. +

+
    +
  • ActiveDirectory (AD) is a completely different database. +
  • There is no support for directly changing passwords in AD. +
  • To clear things up: The Active Directory SERVER itself is not +directly supported, but workstations (w2kprof) and servers (w2k server) that is +just MEMBERS of the domain can have their LOCAL passwords changed by +the utility. +
  • But.. +
  • John Simpson has made +instructions on how to reset that pesky lost administrator password in AD. +
  • Many thanks goes to John for this! +
  • And I may as well in a future relase make a frontend for the +screensaver trick he uses, so it will be even easier. +
+

+

+

+What is the 'Can't access tty...' error message when I quit the +floppy/cd procedure? +

+
    +
  • It's from the shell, and has nothing whatsoever to do with the +password edit. +
  • My scripts don't allocate the terminal correctly. +
  • Only thing it means is that ctrl-c to break etc won't work on +console 1. Should work on console 2-4 (ALT-F2 and so on) +
  • Please don't ask about this in mail AGAIN! +
+

+

+My language uses characters in the usernames that are not readable +with the floppy, and i cannot enter/search for them, thus not edit. +

+
    +
  • There is no support for the full unicode character set. Perhaps +never will. +
  • Select user with the RID (user ID) instead. +
  • At the username prompt, enter the RID in hex, just as it is listed +in the user listing. 0xfa0 for instance. +
+

+ +

+

+What about support? and I just paid $$ for it on eBay! +

+
    +
  • Yes, some people sell it on eBay. +
  • Most of them didn't bother to ask me, but I haven't cared too much +about it, at least not yet. +
  • If the price is reasonably low (for media, shipping etc), they offer some kind of help and +support if customers need it, that's good, and no problem for me. +
  • Please do not blaim me if eBay sellers can't deliver or it doesn't +work, or you feel ripped off. Leave feedback on eBay instead. +
  • I DO NOT ENDORSE ANY SPECIFIC SELLER ON eBAY! +
  • I give my tool away for free here, because I do not have the time +for real support. +
  • Usually I go through my mail 1 or 2 times a week, and I usually +end up replying about 40-50% of it. +
  • What I answer depends on my mood that day, what the problems +are, and how they are presented. +
  • Mails with questions for which an answer can be found here in the +FAQ or on the other webpages will not be answered. +
  • Questions for drivers will almost never be answered. They take too +much time to figure out. Sorry. +
  • And.. I understand English, Norwegian, Swedish and Danish. +
  • My answers are either in English or Norwegian. (as appropriate :-) +
  • Thank you all for a lot of positive feedback or small tips for +improvement, I appreciate it :-) even if I often don't reply to you. :-( +
+ +

+

+Can I donate money? +

+
    +
  • Not a the moment, I have closed the donations. There are several +reasons I will not talk about. +
  • But a big thank you to all that have donated, especially to some I +guess I have missed a personal reply to! +
+

+


+

+


+
091201, pnh@pogostick.net
+ + --- /dev/null +++ b/syskey.txt @@ -0,0 +1,124 @@ +The Offline NT Password Editor + +(c) 1997-2002 Petter Nordahl-Hagen + +Update: 08 dec 2002 + +What happens when syskey is installed, and how to get rid of it +--------------------------------------------------------------- + +Background: +----------- + +Syskey was added to NT with Service Pack 3 as a way to prevent easy +access to the actual password hashes in the SAM (Security Accounts Manager) +The original methods of making and storing the hashes makes it +rather easy to bruteforce or dictionary-attack it to find the plaintext +passwords. (mostly caused by a somewhat flawed implementation & use +of the cryptoalgorithms involved, but that's discussed elsewhere) +Enabling syskey is optional, the administrator must run syskey.exe and +answer some dialog-boxes to turn it on. On Windows 2000 it's not optional +anymore, it's enabled by default at installation time. + +When syskey is active, the hashes are encrypted/obfuscated yet +another time before being stored in the SAM registry. +However, they're stored in the old form in memory after boot +(pwdump2 demonstrates this), +since the old form is needed for NTLM authentication on the network etc. + +The key that obfuscates the hashes, or rather it looks like something +that decrypts the key, can be stored on floppy, generated from a +passphrase to be entered at boot, or stored (obfuscated again) in +the registry. + +There's no official supported method to switch off syskey +once activated, except restoring the registry from a rescuefloppy +made before activation of syskey. + +So.. what's this got to do with my utility? +------------------------------------------- + +My utility doesn't try to crack passwords, it puts new hashes into +the SAM, thus changing a users password. And it does this offline. +Syskey was a showstopper for this. +As far as I can see, there's 2 ways to solve this: + +1) Find the key in registry, get user to enter it, or get hold of floppy + then use the syskey on the new password too. However, it's not documented + and I haven't found any reverse engineering of it anyplace. + +2) Try to turn it off. This has one drawback, and one good side: + Bad: all passwords must be reset, since the old hashes will be invalid. + VeryBAD: SWITHCHING OFF IN WINDOWS 2000 AND XP NOT PERFECT, + WILL CAUSE TROUBLE, but you can access the computer + afterwards. Domain relationships & syskey may be + impossible to change after this, requiring a reinstall + (or possibly only an upgrade) + Good: There's no need for the key (which may be lost). + +3) (NEW 2000-04-01, no, not a joke) Insert old styles password-hashes + into the SAM, will be converted to syskey-hashes on next boot. + This is how syskey is enabled on NT4, the hashes won't be touched + until the first reboot after turning on syskey. + +I've found out how to do #2 and #3. + +What happens when syskey is turned on, and how to turn it off again: +-------------------------------------------------------------------- + +- 1 - +Serveral new keys are added to HKLM\System\CurrentControlSet\Control\Lsa, +it seems that most of the keys/values is used for the obfuscation of the key +they change when syskey is updated. +However the value named 'SecureBoot' holds the mode of syskey: + 1 - Key in registry + 2 - Enter passphrase + 3 - Key on floppy + +But removing this key (or setting it to 0) isn't enough to disable +syskey. There's more.. + +- 2 - +HKLM\SAM\Domains\Account\F is a binary structure usually containing the computer +SID and some other stuff related to that. +When syskey is installed it's expanded (about twice the size), with something +I guess is the key heavily encrypted + some flags and other values. +One of these other flag/values also contains the same mode as SecureBoot above. + +So.. resetting this mode flag and SecureBoot to 0 is all that's needed +to switch off syskey in NT4 (up to SP6 at time of writing). Changing only one of them +results in a warning about inconsistencies between the SAM and system settings +on completed boot, and syskey is re-invoked. + +- 3 - +On Windows 2000 there's yet another place info about syskey is stored: + +HKLM\security\Policy\PolSecretEncryptionKey\ +which also is a binary structure, but also there the mode is stored. +Reset this to 0, and syskey is gone on win2k. +(if there's a mismatch between the three, it silently resets them + to the most likely value on boot) + +- 4 - +Then there's the password hashes. +The usual (old) hashlength is 16 bytes, but all hashes are expanded to 20 bytes +with syskey, the first 4 bytes looks like some kind of counter. (maybe +history-counter?). +Strangely, they're not updated at once when syskey is turned on, +update of the hashes happens during next reboot after syskey has been turned on. +And when the key is later updated, the hashes are also updated? +NO!! Strangely it SEEMS like the password hashes REMAINS THE SAME! +(however, the binaries in the 3 keys noted above changes..) +I'll try to dig more into this. Help wanted :) + +When syskey has been switched off, all passwords must be reset. +My utility will write and adjust hash-lengths of the users (usually +administrator) that you reset the password for. +NT itself will fix the rest of the hashes when you set new passwords +from NT. + +And yes, it's possible to re-enable syskey after turning it off. +(not on win2k, yet!) + +So, anybody reverse engineered the whole syskeystuff? +(yes, I know something's on it's way..)