smd75jr

Hi, So I'm wondering how someone would go about setting up a console-based, networked, multi-user system. You know, the kind of system from about 20-30 years ago with no GUI. it would seem that it has completely died out, even among the Linux/BSD/UNIX communities (as far as I can tell anyway). -It MUST be accessible via ssh -It would be nice to have a decent amount of packages So if anybody could help me out, i would be eternally grateful. Thanks, Stephen

Up next: DyKnow?

That's what I'm thinking, i guess ill have to do it the hard way and "wait for the tamper evident sticker on the hard drive to peel of naturally"

That's what i was thinking, whatever the admin has done to it, its untouchable now (as is the registry, which i could edit a few days ago, grrrr)

I used 7zip when i decompressed it (yay Open Source) and it worked fine (it took forever). As for opening it, i was once able to open it but i don't remember the actual software i used (it may have been this: http://www.editpadpro.com/editpadlite.html ), but don't really think it was meant to be opened, just to be fed into a brute forcer.

24gb zip'd to 78mb http://rapidshare.com/files/30781645/huge_wordlist.rar

No, it says that it has been locked by the admin. http://hak5.org/forums/index.php?showtopic=15380 This thread will describe my current situation.

Ok, so, about a week ago, i could edit my boot.ini, now i cant, even on my power user. I need a way to edit it, or at least elevate my privlages to Administrator. Can anyone help me? Please?

That is what i have been trying to do, but again, i am not sure how grub4dos addresses USB flash drives, also it is not clear how to configure the menu.lst This is the menu.lst # This is a sample menu.lst file. You should make some changes to it. # The old install method of booting via the stage-files has been removed. # Please install GRLDR boot strap code to MBR with the bootlace.com # utility under DOS/Win9x or Linux. color blue/green yellow/red white/magenta white/magenta timeout 30 default /default title find and load NTLDR of Windows NT/2K/XP fallback 1 find --set-root --ignore-floppies --ignore-cd /ntldr map () (hd0) map (hd0) () map --rehook find --set-root --ignore-floppies --ignore-cd /ntldr chainloader /ntldr savedefault --wait=2 title find and load BOOTMGR of Windows VISTA fallback 2 find --set-root --ignore-floppies --ignore-cd /bootmgr map () (hd0) map (hd0) () map --rehook find --set-root --ignore-floppies --ignore-cd /bootmgr chainloader /bootmgr savedefault --wait=2 title find and load CMLDR, the Recovery Console of Windows NT/2K/XP fallback 3 find --set-root --ignore-floppies --ignore-cd /cmldr map () (hd0) map (hd0) () map --rehook find --set-root --ignore-floppies --ignore-cd /cmldr chainloader /cmldr ##################################################################### # write string "cmdcons" to memory 0000:7C03 in 2 steps: ##################################################################### # step 1. Write 4 chars "cmdc" at 0000:7C03 write 0x7C03 0x63646D63 # step 2. Write 3 chars "ons" and an ending null at 0000:7C07 write 0x7C07 0x00736E6F savedefault --wait=2 title find and load IO.SYS of Windows 9x/Me fallback 4 find --set-root /io.sys chainloader /io.sys savedefault --wait=2 title find and boot 0PE.ISO fallback 5 find --set-root /0PE/0PE.ISO map /0PE/0PE.ISO (0xff) || map --mem /0PE/0PE.ISO (0xff) map --hook chainloader (0xff) savedefault --wait=2 title find and boot MicroPE.ISO fallback 6 find --set-root /boot/MicroPE.ISO map /boot/MicroPE.ISO (0xff) || map --mem /boot/MicroPE.ISO (0xff) map --hook chainloader (0xff) savedefault --wait=2 title Parted Magic ISO fallback 7 find --set-root /pmagic.iso map /pmagic.iso (0xff) || map --mem /pmagic.iso (0xff) map --hook chainloader (0xff) savedefault --wait=2 title Ultimate Boot CD ISO fallback 8 find --set-root /ubcd.iso map /ubcd.iso (0xff) || map --mem /ubcd.iso (0xff) map --hook chainloader (0xff) savedefault --wait=2 title commandline commandline title floppy (fd0) chainloader (fd0)+1 rootnoverify (fd0) title back to dos quit title reboot reboot title halt halt title MAXDOS.IMG find --set-root --ignore-floppies /boot/MAXDOS.IMG map --mem /boot/MAXDOS.IMG (fd0) map --hook chainloader (fd0)+1 rootnoverify (fd0)

My main problem is my not knowing how to configure the menu.lst, Also, i need to know how grub4dos addresses usb flashdrives. There dosnt seem to be any documentation on either.

It doesnt let us do very much more than normal, although I do have a super user that isnt affected by deep freeze.

So heres my new thought, i can chainload grub4dos, now my problem is that it wont mount the flash drive. Any sugestions?

When i open the bootsect.lnx file, what should it look like? When i open it in the Linux distros text editor, its just a bunch of periods, whn i open it in windows, its just a bunch of spaces.

I am very confused on how to do this. I have tried on at least 4 different distros and still cannot get any more then a blank, empty file.

I have a super user, (though anti-executable still affects normal pragrams, java programs and cmd tools still work), so i can edit hidden files and the changes will stay.

Sadly thats exactaly whats installed

Right now, my thought is to use the MBR file (the name escapes me at the moment) that gets dumped from the linux MBR (using the dd comand listed in the links from sparda) and figure out how to edit those into the boot.ini file. my problem now being that i want to know what file the linux MBR file points to to simplify the process.

Its XP Pro, Running on an HP Tablet

Thanks, My original thought was to go into the boot.ini file in the root of the C: drive and and a section that simply told it to boot from (insert device id here), and if its not there, then to not complain about it and continue to boot windows.

Sadly, thats not possible, what im trying to do is creat a proof-of-concept hack to demonstrate to my high schools IT department and sys admins that there "super ultra secure" laptops (each student gets one) arent as secure as they think they are. (yes i asked if it was ok). The BIOS is locked up tight, and the boot device menu is disabled, thats where i keep running into problems.

I couldnt find a topic for this anywhere so here it is. I have been looking for a way to edit my boot.ini file so that ntldr will look for a a live linux operating system on a USB flash drive, and, if present, boot form that. If not, i needs to boot into windows WITH NO OBVIOUS CHANGES TO THE SYSTEM, meaning that if someone (like a sys admin) watched the boot process, they would not be able to tell that anything had been changed. I know that this would have to be VERY machine specific, but it may be useable for those that are in need of a more secure system, or those who are just very paranoid. Thanks, smd75jr