GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
darn you slashdot!!!!, thanks to you i cant open the page
but from the slashdot article, I'm confused what to do, feel sorry for some "hacker" *script kiddie** for thinking 127.0.0.1 was a real IP of someone else, or laugh at that persons stupidity.
either way its quite sad, lots of people know 127.0.0.1 is loopback, actually, everyone that has network experience should know, and certainly anyone trying to "hack" someone across a network should know. ...... this story is quite sad,
now that thats over with, thats all laugh at this "hacker", and curse slashdot (darn them!!!, i still cant got that page to load, been trying for a hour ......)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.