a5an0

No -O -A ? NAh, OS fingerprinting isnt really needed. -A would be nice though. good call

You know, I could do the usual thin and call the person a n00b or a lamer, or something. I could "give them a link" that points to google, and feel really clever. I could tell them to learn c, and then read a bunch of RFC's, and learn tcp/ip. I could tell them that hacking their school network is wrong and immoral and whatever, but its just so .... been done. Sometimes I et the feeling we're just kicking a dead horse here. So, instead, I'm going to tell you exactly what you need to know. figure out what services are running on your machine. This should be trivial to do, and if you really get stuck, install nmap and then do nmap -sS -sA -v -T5 localhost write down all the services and version numbers go to packetstorm or security focus and look for local privilage escalation exploits for the services that you just found. Keep in mind that many of these exploits are "skiddie-proofed". That is, they have made minor modifications to the code to keep it from compiling or running. So, you will ned to know enough of the chosen language (usually C) to fix the exploit. Once it is all set, compile, run, root. There, you are now a 1337 hax0r. you are k-rad. Have a nice day.

deep....

I've started listening to the clash while hacking around, it's kinda nice

I love peanut-butter sandwiches!!!!!!

I don't trust any cryptosystem where I can't see the source. that doesn't mean open-source, I'm talking about seeing the source for the encryption algorithm. for example, pgp isn't open-source in a gpl kinda way, but you can see the source to verify integrity. I havn't been able to find such a thing for bitlocker, so I would stay away. They claim it's 128 bit AES, but how do you know it's properly implimented, etc. I use trucrypt, and a few home-brew python scripts for all my crypto needs.

true, but it still sucks

If you used the switchblade, then I am assuming that those hashes came from a windows box, and are more than likely LM hashes, which is *not* the same as MD5. LM hashes are the result of trunking/expanding a pass to 14 chars, converting to all uppercase, spliting into two 7 char keys, and then using each key to encrypt the string “KGS!@#$%” using DES. the resulting cyphertext is the hash. MD5 is the password hash used in FreeBSD if memory serves me. now, where could you find lm rainbowtables??? :-P

We need to repeal the DMCA.

yeah, it not bad at all. For those of you hacking up asm on linux, you can find all the syscalls in /usr/include/unistd.h in the kernel. :-P

wow I have been gone for too long....

yeah

It's not *taht* bad going from intel to AT&T. its all the same concepts, and mostly the same syntax, there are just some differences that you need to be aware of. for example, in intel syntax, you do [instruction] [destination],[source] int AT&T, you do [instruction] [source], [destination], for example, to load the value stored in ebx into eax, it would look like: intel: mov eax,ebx AT&T: mov %ebx,%eax as you can see, another difference is that in at&t, registers are prefixed with a %. so theres a lot of little things like that. if you google for it, you can find concise 2 page-ish summaries of the differences.

if you're editing in vim, just push [esc] and then type ggVGg? (yes you do type the ?) ;-)

I remember back in the day, when moonlit would swoop down out of nowhere and nija the shit out of posts like this. and by ninja I mean lock. it turns out that sometimes ninja==lock