lol I almost posted a similar reply ~Quote:
Originally Posted by Melcar
There's some nice irony there though.
:p
Printable View
lol I almost posted a similar reply ~Quote:
Originally Posted by Melcar
There's some nice irony there though.
:p
It is essential to get enough irony in your diet.Quote:
There's some nice irony there though.
From one of our other Tech's...
How do I find what computer 127.0.0.1 is?
Electric signals travel at about 1/3th the speed of light, Ping that IP, take down the time in it takes for that ping to come back, devide that time by 2, calculate the distance traveled during that time at 1/3th the speed of light, then follow your network cable out of your computer for that amount of meters to 127.0.0.1Quote:
Originally Posted by Melcar
:P
Little faster then that.Quote:
Electric signals travel at about 1/3th the speed of light
http://en.wikipedia.org/wiki/Speed_of_electricityQuote:
Propagation speed is affected by insulation, such that in an unshielded copper conductor range 0.95 to 0.97 that of the speed of light, while in a typical coaxial cable it is about 66% of the speed of light
Ethernet is UTP unshielded Twisted Pair... So, near 95% the speed of light.
So your calculations at 1/3 would be off by a significant margin...
Probably, I just picked the travel speed of an electron through a basic copper power wire.
Looking at data, you look at em-field travel time which is indeed influenced by shielding etc. The field travels faster then the electrons that sustain it. It just means they have to follow more meters of cable, so they have more time to reach the facepalm moment.
Which of course, doesn't even matter because communication to the Loopback doesn't even touch the wire - it doesn't leave the NIC.Quote:
Probably, I just picked the travel speed of an electron through a basic copper power wire.
Looking at data, you look at em-field travel time which is indeed influenced by shielding etc. The field travels faster then the electrons that sustain it. It just means they have to follow more meters of cable, so they have more time to reach the facepalm moment.
How many femtoseconds does it take to completely overshoot the building, though? Like ten? You need a really accurate timepiece.
Customer: Hi, I'm having a problem with (stupid configuration for usage thing that I broke)
Me: Okay well I need to get you in contact with our user group.
Me: *holds for a minute* Ma'am, unfortunately no one in the other group is available. WOuld you like to leave a voicemail or call back tomorrow?
Customer: I'm going on vacation. I need help NOW and I'm leaving the office in 10 minutes.
Me: Well unfortunately the other group is unavailable. Do you want to hold?
Customer: Fine. They're probably not even going to pick up, they're leaving in ten minutes.
Me: That's not the case ma'am - after all, I answered...
Customer: *silence*
Boo and Yah.
Good one I had at comcast was somebody already on vacation, they called in to complain their modem did not work at the beach house. after a quick google of the location it was charter territory, took about 30 minutes to get them to understand they can only use their modem on the Comcast system and technically only in their service area(though sometimes a modem will work on any comcast system because provisioning is weird like that and does its own thing)
Just one to share:
During a recent password audit, it was found that someone was using the following password:
"MickeyMinniePlutoHueyLouieDeweyDonaldGoofySacrame nto"
When asked why she had such a long password, she said she was told that it had to be at least 8 characters long and include at least one capital.
id hope there was never a password Audit of me, I always just used a password with a number that I changed at the end. Take that "Must change every 30 days" policy on the network.
Month + Year is my favorite revolving password. It never repeats, uses letters and numbers and impossible to forget!
:p
Booo, Branaman, BOOOO! :p
Yup, Month+year after the basic similar blurb to circumvent that 30 day password change policy.
which of course is why I feel 30 days is to frequent, and instead favor a 90 day policy.Quote:
Yup, Month+year after the basic similar blurb to circumvent that 30 day password change policy.
The company I'm currently working for just went through a security audit. They were able to crack about 1/3 of the company's passwords. My personal favorite was 'FuckYou2'.
I knew my password was weak. Now that I'm help desk with the new company, I find myself doing all the things that used to annoy me as an Admin. Weak passwords, casually tossing 600GB worth of images on the file server, ... I may not like my job, but the lack of responsibility is very refreshing.
But that's the perfect password for a support tech!Quote:
Originally Posted by Filthy
I wonder if the person with FuckYou2 got in trouble.Quote:
Originally Posted by Filthy
I'm surprised they were able to crack that. It is 8 characters long with upper case lowercase and a number. I wonder if it would be harder to crack if they went with FuckUtw0.