Aces High Bulletin Board
General Forums => The O' Club => Topic started by: TopGear on June 26, 2013, 02:09:22 PM
-
Had a guy just call our shop phone and informed us that my dads computer was crashing and sending Microsoft multiple error reports. I don't have a computer at work so I played along and pretended to do as he asked. So when he said to type in 'eventvwr' in the run box, I told him the screen just went blue and it froze up. He says " well it shouldn't do that, try restarting your computer". I said okay and waited a few seconds then I started yelling " HOLY CRAP!!!! THERE IS SMOKE COMING FROM MY KEYBOARD!!!! He started panicking too and yells back " call the fire birigade immediately!!!!l I yelled back OKAY!!, and hung up. My brother was in the shop with me, he doubled over laughing so hard. :lol
Occasionally I play around with telemarketers, one time they called and asked for the owner and I handed the phone to a hired hand. He didn't miss a beat and started stringing out some wild stories. I try not to be to mean to them though, my wife used work as a one for a while, and she had some stories from mean things people said to her.
-
I had a guy who would call from Verizon asking for the previous owner everyday at exactly the same time around 5. Everytime I would reply that the owner had moved. Apparently, he must've forced by the company to keep calling so eventually, he would call, I'd say "hey", he said "hey" and we both hung up. It was kind of a neat bonding experience. :lol Finally stopped after 2-3 months out of the blue.
-
is it just me or are there more cockroach scammers coming out of the wood work than ever before?
-
TopGear, I'd like you to take care of some scam telemarketers that have got my home number apparently from our official Trade Register.
It just so happened that one morning my wife answered and according to my hand jive she then with her poor English told I wasn't there and that she didn't know my cell phone number. The opponent had got angry and yelled "Don't you understand, this is BUSINESS!" Then another day my daughter answered the phone and not knowing what it might have been about, gave my cell phone number to the caller. So I got a call from a polite gentleman who, after hearing I was busy with a customer, said he'd call me later at a more suitable time. The very same day I got an SMS saying my number had won millions in a lottery, what a coincidence! A day or two pass and the same gentleman calls again in the morning while I was packing my gear for the day. He says I had been contacted by one of their "fieldmen", <Name>, Mr <Family Name>, introducing himself as an executive manager, <Name>, Mr <Family Name>. (Is that a common way to introduce people in English?) He then started to tell that they weren't trying to sell me anything, but that he'd like to give me a website address. I told him that I would do no business related decisions in other languages than Finnish and that I run my firm alone with no extra money to invest anywhere. The same time I had noticed the cover of the desktop I was packing into my car was bent and tried to fix it. He asked if I was out of breath and I just told him what I was doing. He then asked me politely to get my breath back and in a definitive way told that their thing was not for me. "This is not for you. Get your breath back. This is not for you!" Goodbye...
-
I had the same thing the other week some asian sounding chap,
He said my PC has been flagged up with a virus. I asked him what company he was calling from, Microsoft technical services. Then I said is it doing it right now ? he was like yes I can see all the packets going through. I was like my computer is turned off so how is it sending any information? Computers can still transmit information when turned off!
I laughed and hung up.
-
I usually ask them for their home phone number and what time they will be home! I then ask them what time they eat at and promptly tell them great I'll call you back then!...... :D
:salute
-
This is how you pwn telemarketers.
http://www.youtube.com/watch?v=mkdoogjic4I (http://www.youtube.com/watch?v=mkdoogjic4I)
-
Computers can still transmit information when turned off!
I laughed and hung up.
:noid
Yea. You need to know about wake on lan, ATX power states, network card chipset firmware security, and how trusted the network stack is at various levels. Better yet, don't go digging, because you'll get upset.
Bottom line though is that with a little help from the hardware manufacturer, there is no "off", and a network controller card (or sound card) today has more computing power than many large/expensive computers had just a decade or so ago. And the firmware for those cards is often flashable, and TRUSTED by the operating system because the OS simply has no way to tell what any particular controller is doing when it isn't talking to the OS.
Lots and lots and lots of doors, and any true computer geek with time on his hands can exploit an awful lot of really unexpected vulnerabilities. People don't realize that their hard drive has a fairly capable controller chip and more RAM than is required to simply act like a hard drive. If someone is able to exploit the firmware validation process, they could probably make your hard drive do all sorts of naughty things. And now they're hanging SSDs directly on the pci-e bus, so they could theoretically talk to other devices (like network cards) without cpu or OS intervention. How about a hard drive firmware exploit that opens a network socket and streams your HD contents directly to the network stack? It could be done with 2 firmware hacks and MAYBE a driver hack to ensure the OS doesn't notice. Input buffers are simply memory address ranges. Yea this stuff shouldn't be possible (signed drivers/firmware, protected address spaces, etc) but almost everything has a back door, intentional or not. To exploit "black box" systems, hackers used to, and still do, send inputs to all memory addresses in sequence just to see what happens. Sooner or later you find out which address range does what, and with time you can reverse engineer almost anything. For a networking controller where the network stack has been well defined for decades, figuring out where you can directly make stack inputs may not take as long as you would hope.
I sort of did this kind of thing for fun right after I finished school while awating training. Back then it wasn't the heinous federal offense it is now, and the network admin helped me do it anyhow. Nowadays, running a program that talked directly to networking hardware on a military computer, or set up a TCP-IP tunnel over a telnet terminal connection would probably earn a few years of jail time. In 1994 it was simply zero credit post-grad work for fun and cool points. Just for fun I could duplicate that work in less than a week now (remaining within a browser sandbox using cookies to communicate between processes), but if they caught me I'd go to jail, so I won't do it or even explain my solution.
-
Not a telemarketer call, but several years ago I was sitting at home when the phone rang. I answered the phone with the normal hello. The other person on the line immediately starting talking about his recent hunting trip. I found it interesting, so I just listened and every now and then I would make a comment. When he was finished about the hunting trip he continued on to other subjects including family, job and so on. We were on the phone for about 30 minutes when he said something where I had to reply. After I replied, the phone suddenly went quite, and after a few seconds the guy stated something to the effect "is this Bob". I answered "no" this is Fred. He then asked me why I let him continue on, and I replied that I found his hunting trip interesting. We both laughed and said Goodbye. I had a good laugh about it.
Fred
-
:noid
Yea. You need to know about wake on lan, ATX power states, network card chipset firmware security, and how trusted the network stack is at various levels. Better yet, don't go digging, because you'll get upset.
Bottom line though is that with a little help from the hardware manufacturer, there is no "off", and a network controller card (or sound card) today has more computing power than many large/expensive computers had just a decade or so ago. And the firmware for those cards is often flashable, and TRUSTED by the operating system because the OS simply has no way to tell what any particular controller is doing when it isn't talking to the OS.
Lots and lots and lots of doors, and any true computer geek with time on his hands can exploit an awful lot of really unexpected vulnerabilities. People don't realize that their hard drive has a fairly capable controller chip and more RAM than is required to simply act like a hard drive. If someone is able to exploit the firmware validation process, they could probably make your hard drive do all sorts of naughty things. And now they're hanging SSDs directly on the pci-e bus, so they could theoretically talk to other devices (like network cards) without cpu or OS intervention. How about a hard drive firmware exploit that opens a network socket and streams your HD contents directly to the network stack? It could be done with 2 firmware hacks and MAYBE a driver hack to ensure the OS doesn't notice. Input buffers are simply memory address ranges. Yea this stuff shouldn't be possible (signed drivers/firmware, protected address spaces, etc) but almost everything has a back door, intentional or not. To exploit "black box" systems, hackers used to, and still do, send inputs to all memory addresses in sequence just to see what happens. Sooner or later you find out which address range does what, and with time you can reverse engineer almost anything. For a networking controller where the network stack has been well defined for decades, figuring out where you can directly make stack inputs may not take as long as you would hope.
I sort of did this kind of thing for fun right after I finished school while awating training. Back then it wasn't the heinous federal offense it is now, and the network admin helped me do it anyhow. Nowadays, running a program that talked directly to networking hardware on a military computer, or set up a TCP-IP tunnel over a telnet terminal connection would probably earn a few years of jail time. In 1994 it was simply zero credit post-grad work for fun and cool points. Just for fun I could duplicate that work in less than a week now (remaining within a browser sandbox using cookies to communicate between processes), but if they caught me I'd go to jail, so I won't do it or even explain my solution.
and of course dont forget about the hal 9000.
semp
-
Not a telemarketer call, but several years ago I was sitting at home when the phone rang. I answered the phone with the normal hello. The other person on the line immediately starting talking about his recent hunting trip. I found it interesting, so I just listened and every now and then I would make a comment. When he was finished about the hunting trip he continued on to other subjects including family, job and so on. We were on the phone for about 30 minutes when he said something where I had to reply. After I replied, the phone suddenly went quite, and after a few seconds the guy stated something to the effect "is this Bob". I answered "no" this is Fred. He then asked me why I let him continue on, and I replied that I found his hunting trip interesting. We both laughed and said Goodbye. I had a good laugh about it.
Fred
:lol that's funny.
I got a text message one time, all it said was " good morning xo Connie" I really wanted to reply to that, but my wife reads my texts regularly.
-
:noid
Yea. You need to know about wake on lan, ATX power states, network card chipset firmware security, and how trusted the network stack is at various levels. Better yet, don't go digging, because you'll get upset.
Bottom line though is that with a little help from the hardware manufacturer, there is no "off", and a network controller card (or sound card) today has more computing power than many large/expensive computers had just a decade or so ago. And the firmware for those cards is often flashable, and TRUSTED by the operating system because the OS simply has no way to tell what any particular controller is doing when it isn't talking to the OS.
Lots and lots and lots of doors, and any true computer geek with time on his hands can exploit an awful lot of really unexpected vulnerabilities. People don't realize that their hard drive has a fairly capable controller chip and more RAM than is required to simply act like a hard drive. If someone is able to exploit the firmware validation process, they could probably make your hard drive do all sorts of naughty things. And now they're hanging SSDs directly on the pci-e bus, so they could theoretically talk to other devices (like network cards) without cpu or OS intervention. How about a hard drive firmware exploit that opens a network socket and streams your HD contents directly to the network stack? It could be done with 2 firmware hacks and MAYBE a driver hack to ensure the OS doesn't notice. Input buffers are simply memory address ranges. Yea this stuff shouldn't be possible (signed drivers/firmware, protected address spaces, etc) but almost everything has a back door, intentional or not. To exploit "black box" systems, hackers used to, and still do, send inputs to all memory addresses in sequence just to see what happens. Sooner or later you find out which address range does what, and with time you can reverse engineer almost anything. For a networking controller where the network stack has been well defined for decades, figuring out where you can directly make stack inputs may not take as long as you would hope.
I sort of did this kind of thing for fun right after I finished school while awating training. Back then it wasn't the heinous federal offense it is now, and the network admin helped me do it anyhow. Nowadays, running a program that talked directly to networking hardware on a military computer, or set up a TCP-IP tunnel over a telnet terminal connection would probably earn a few years of jail time. In 1994 it was simply zero credit post-grad work for fun and cool points. Just for fun I could duplicate that work in less than a week now (remaining within a browser sandbox using cookies to communicate between processes), but if they caught me I'd go to jail, so I won't do it or even explain my solution.
:rofl back in the 90s anyone who left the wake on lan option enabled on their nics (simple wire or jumper setting) then allowed the transmission of magic packets on their network deserved what they got...hacked.
now we have home routers that can block magic packets at the front end. i haven't seen a system in the last 8 years that i couldn't disable the wake on lan option either in the driver or bios.
-
Another fun telemarketer trick is to just say ... Hello... Hello... Hello... Hello ..... make sure and drag out the hellos next noise ya hear is the click of him hanging up lol
-
This is how you pwn telemarketers.
http://www.youtube.com/watch?v=mkdoogjic4I (http://www.youtube.com/watch?v=mkdoogjic4I)
:rofl :rofl :rofl :rofl :rofl :rofl :rofl :rofl :rofl :rofl :rofl
-
Another fun telemarketer trick is to just say ... Hello... Hello... Hello... Hello ..... make sure and drag out the hellos next noise ya hear is the click of him hanging up lol
First I speak in Spanish, then if that doesn't work Japanese. And if THAT doesn't work, I have an airhorn that works quite nicely :devil :devil :devil
So far been about 3 weeks since I've gotten a call. What's funny is my number is on the "do not call" list.
Tinkles
:salute
-
we usually have the same 3 that call, I have stated answering, (in as hickish voice as I can) Homer's haulin' and trucking', if we cant haul it, we'll truck it and if we cant truck, it F@#$ IT!! this is Homer speakin' how can I help ya? they usually hang up :D I had one calling for a guy that used to have our phone number, started off being polite saying he wasn't here and it wasn't his number. it quickly escalated to pretty nasty phone calls after I said it weren't him I would get "okay well sue him then" and hang up. then one called and got pretty nasty so I got rude back and he hung up on me, so I called back and asked for the twerp. I got hung up on again :lol
-
Last I talked to one, I pretended I was retarded and the trolling began
-
"Pretended"? :D
<3.
-
"Pretended"? :D
<3.
das nut nis! Mi mom luvs mi! :neener:
-
Last I talked to one, I pretended I was retarded and the trolling began
...and you forgot to get out of character before getting back on the BBS?
:neener:
-
...and you forgot to get out of character before getting back on the BBS?
:neener:
Cause an actor must be prepared to act on command :old:
:rofl
-
Several years ago my wife started getting prank calls from an invisible number. When she answered, the other party kept silent. No heavy breathing or background noise, just plain silence. She had a clue that it might have been some student(s) from the school where she worked as a teacher, but she had no evidence.
So one afternoon her cell phone rang once again, not showing the caller's number, and I picked up the phone. In a formal, emphasized way used in taped messages I said: "The number you are calling to is under Police surveillance. Please hold, your call will be connected in a moment." That was the last prank call from the silent caller. :lol
-
Several years ago my wife started getting prank calls from an invisible number. When she answered, the other party kept silent. No heavy breathing or background noise, just plain silence. She had a clue that it might have been some student(s) from the school where she worked as a teacher, but she had no evidence.
So one afternoon her cell phone rang once again, not showing the caller's number, and I picked up the phone. In a formal, emphasized way used in taped messages I said: "The number you are calling to is under Police surveillance. Please hold, your call will be connected in a moment." That was the last prank call from the silent caller. :lol
Or just answer with the same response as a your local police department would. "so and so police dept., can I help you?" I did this back before caller id and when the cankers would call many times in a row.