command prompt in school
DOS is pretty unusual in schools as far as my experience is, although it would be an interesting method of attack in some instances. however, most of the other instances it's just degrading the entire network's performance to shit, which would be undesirable.
for the net send thing, cobain pointed it out, but it's mostly futile nowadays anyways. usually the net messenger service is disabled by default. to turn it on you'd use the command "net start messenger", but then there's usually and administrative block on starting it. besides, i'm sure more fun can be had with netbios null sessions, since chances are your school uses windows networking for file-sharing.
and for the net user command to give yourself admin rights, it only works on the local machine, and chances are your login info is stored on the DC, so that command would do nothing.
as for telnet, ssh is vastly preferred over it. it's more secure, and completely encrypted traffic. a word of caution though; if you get any clever ideas of having a telnet/ssh server on a home pc and tunneling out to it from the internet to bypass filters, be careful. i tried a setup like this not long ago, and a bot found my open ssh port within 4 hours. it tried to brute force it's way in, but it failed, so if you're thinking of this, make sure you know what you're doing, or it'll come back to bite you when your pc is conscripted into a botnet.
for the net send thing, cobain pointed it out, but it's mostly futile nowadays anyways. usually the net messenger service is disabled by default. to turn it on you'd use the command "net start messenger", but then there's usually and administrative block on starting it. besides, i'm sure more fun can be had with netbios null sessions, since chances are your school uses windows networking for file-sharing.
and for the net user command to give yourself admin rights, it only works on the local machine, and chances are your login info is stored on the DC, so that command would do nothing.
as for telnet, ssh is vastly preferred over it. it's more secure, and completely encrypted traffic. a word of caution though; if you get any clever ideas of having a telnet/ssh server on a home pc and tunneling out to it from the internet to bypass filters, be careful. i tried a setup like this not long ago, and a bot found my open ssh port within 4 hours. it tried to brute force it's way in, but it failed, so if you're thinking of this, make sure you know what you're doing, or it'll come back to bite you when your pc is conscripted into a botnet.
ASPARTAME: in your diet soda and artificial sweeteners. also, it's obviously completely safe. it's not like it will cause tumors or anything. >.>
always remember: guilty until proven innocent
always remember: guilty until proven innocent
- TomClancey
- Posts: 2565
- Joined: Sat Jan 28, 2006 6:49 am
- Location: Ohio
- Contact:
Our school mostly runs off of Thin Clients, which, they are pretty awful, even though it comes with USB ports on the back, you can't use them.
Though, our schools Computer Lab has all PC's, and 5 in the Media Center are PC's.
Our school use HP T5700 Thin Clients by the way, PCI Expansion Module isn't included.
Though, our schools Computer Lab has all PC's, and 5 in the Media Center are PC's.
Our school use HP T5700 Thin Clients by the way, PCI Expansion Module isn't included.
- TomClancey
- Posts: 2565
- Joined: Sat Jan 28, 2006 6:49 am
- Location: Ohio
- Contact:
-
- Posts: 24
- Joined: Sun Oct 28, 2007 6:53 am
- galvination
- Posts: 908
- Joined: Sat Jun 17, 2006 6:30 pm
- Location: I lack a witty comment to put here.
- Contact:
Pretty much this is the primary post to read in this thread. If you plan to use anything you're using telnet but in doing so you can get screwed over by bots that scour the internet waiting for a port to open and crack your key.[cc]z@nd! wrote:DOS is pretty unusual in schools as far as my experience is, although it would be an interesting method of attack in some instances. however, most of the other instances it's just degrading the entire network's performance to ****, which would be undesirable.
for the net send thing, cobain pointed it out, but it's mostly futile nowadays anyways. usually the net messenger service is disabled by default. to turn it on you'd use the command "net start messenger", but then there's usually and administrative block on starting it. besides, i'm sure more fun can be had with netbios null sessions, since chances are your school uses windows networking for file-sharing.
and for the net user command to give yourself admin rights, it only works on the local machine, and chances are your login info is stored on the DC, so that command would do nothing.
as for telnet, ssh is vastly preferred over it. it's more secure, and completely encrypted traffic. a word of caution though; if you get any clever ideas of having a telnet/ssh server on a home pc and tunneling out to it from the internet to bypass filters, be careful. i tried a setup like this not long ago, and a bot found my open ssh port within 4 hours. it tried to brute force it's way in, but it failed, so if you're thinking of this, make sure you know what you're doing, or it'll come back to bite you when your pc is conscripted into a botnet.
from CNN-
"i love water. i dont love drugs. i dont want drugs in my water..why on earth is hannah montana more important than this?"
"i love water. i dont love drugs. i dont want drugs in my water..why on earth is hannah montana more important than this?"
When i type in services.msc and scroll down theres nothing that even mentions "messenger". >_>Cobain wrote:ok here is what you gotta do...this is the command
net send <computer name> <message>
oh but first type services.msc
thengo down the list till you see messenger...the right click and start...then do that on yer brothers computer also...iewther through remote desktop...or just do there and do it.
since this was bumped i'll go ahead and mention this about developments with tunnels o server at home.
i did a honeypot a few days ago with a mostly-standard install of openssh. standard port and procedure except no root logins. after examining the log, i got some pretty statistics out of it, but learned a good way to protect your home ssh server.
first, go into the config file and disable root login over the network. once you're in, you can su to root anyways, so leaving this on is pointless. turning off root logins will defuse a good portion of attacks regardless of whether the password's right or now.
next, set the port to something other than 22, and preferably above 1024, up in the nonstandard range. since i'd assume the scans i was hit with were probably all directed at port 22 across a wide range of IPs, simply listening somewhere nobody will talk to should reduce hits. this is just security through obscurity, which is no replacement for real security and a bad habit, but is acceptable in this case.
once that's done you should have a relatively secure ssh server you can tunnel into from home. what i'm going to try with mine is using it as a socks proxy with portable firefox on my jumpdrive. the biggest challenge i'll face is finding a port allowed out of my school; ie uses an internal proxy on 8080, which then filters traffic and sends it out. i believe it is the only IP allowed internet traffic out. if i'm unlucky, it's also the only IP allowed to send anything out at all, but i'm betting they just let DNS through, so i'm gonna see what luck i have running the tunnel over port 53...
i did a honeypot a few days ago with a mostly-standard install of openssh. standard port and procedure except no root logins. after examining the log, i got some pretty statistics out of it, but learned a good way to protect your home ssh server.
first, go into the config file and disable root login over the network. once you're in, you can su to root anyways, so leaving this on is pointless. turning off root logins will defuse a good portion of attacks regardless of whether the password's right or now.
next, set the port to something other than 22, and preferably above 1024, up in the nonstandard range. since i'd assume the scans i was hit with were probably all directed at port 22 across a wide range of IPs, simply listening somewhere nobody will talk to should reduce hits. this is just security through obscurity, which is no replacement for real security and a bad habit, but is acceptable in this case.
once that's done you should have a relatively secure ssh server you can tunnel into from home. what i'm going to try with mine is using it as a socks proxy with portable firefox on my jumpdrive. the biggest challenge i'll face is finding a port allowed out of my school; ie uses an internal proxy on 8080, which then filters traffic and sends it out. i believe it is the only IP allowed internet traffic out. if i'm unlucky, it's also the only IP allowed to send anything out at all, but i'm betting they just let DNS through, so i'm gonna see what luck i have running the tunnel over port 53...
ASPARTAME: in your diet soda and artificial sweeteners. also, it's obviously completely safe. it's not like it will cause tumors or anything. >.>
always remember: guilty until proven innocent
always remember: guilty until proven innocent
- galvination
- Posts: 908
- Joined: Sat Jun 17, 2006 6:30 pm
- Location: I lack a witty comment to put here.
- Contact:
oooh, good idea, maybe they let SMTP out, although if they set up the internal proxy chances are they'd only allow the webserver to send out SMTP as well. maybe i can see what port windows update runs on.... i'll do some recon and develop some educated guesses for potentially open ports, but DNS would be a good one to start off with.
ASPARTAME: in your diet soda and artificial sweeteners. also, it's obviously completely safe. it's not like it will cause tumors or anything. >.>
always remember: guilty until proven innocent
always remember: guilty until proven innocent
My favorite thing is a bat file that really is quite hilarious imo.
it basically runs this command the nuber of times you type into the field.
(if you typed 2 it would send it 2 times)
the thing is i had this set up on my home server spaming it 5 times every 5 minutes. then i realized the domain covered our whole school district and i got suspend for 2 days after an ip trace.
it basically runs this command the nuber of times you type into the field.
(if you typed 2 it would send it 2 times)
Code: Select all
net send /domain:*your domain here* AHHHHHHHHHHHHHHHHH... hold on, had to take a breath... AHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
- Senor_Grunt
- Posts: 1672
- Joined: Thu Dec 22, 2005 5:43 pm
- Location: (Ò_Ó)
- Contact:
![]() |
- JacksonCougAr
- Posts: 2333
- Joined: Fri Jan 12, 2007 1:56 pm
- Location: Canada
- Contact:
![]() |
IIRC, the protocol the messenger service uses (netbios) won't travel over layer 3 devices like routers, but i might be wrong, i haven't read anything about netbios or what protocol exactly MS uses for it's networking lately.CrysisFX wrote:......Code: Select all
net send /domain:*your domain here* AHHHHHHHHHHHHHHHHH... hold on, had to take a breath... AHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
also, no bumping, although it's not nearly as bad as some i've seen.
ASPARTAME: in your diet soda and artificial sweeteners. also, it's obviously completely safe. it's not like it will cause tumors or anything. >.>
always remember: guilty until proven innocent
always remember: guilty until proven innocent
- JacksonCougAr
- Posts: 2333
- Joined: Fri Jan 12, 2007 1:56 pm
- Location: Canada
- Contact:
![]() |
- MarsMartianMan
- Posts: 431
- Joined: Tue Apr 01, 2008 11:34 am
- Location: Florida
- Contact:
Wanna know what else is fun?
Javascript.
Code: Select all
<script type="text/javascript">
window.setTimeout("location=('http://www.internetisseriousbusiness.com/');",0)
</script>