DebianThis forum is for the discussion of Debian Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Did you know that...
On November 21st, 2003, Debian Project staff annunced some of their servers have been compromised by a group of hackers.
Because "klecker" security servers are now under serious investigations, I suggest all the debian fans to keep away from possible risks.
Also, if you haven't already, upgrade your system as soon as possible.
If you already knew, sorry for being boring.
I can say for sure they were professionals.
Even though debian project is running many internet services (think when you're doing apt-get...) and this can increase vulnerabilty, I hardly believe that debian guru are unable to protect themselves properly.
probably Bill and pals.
Well, I'd like to think this way (he'd get in troubles this time...), but I don't think he did, mainly because he's too busy thinking of gaining money then thinking of what makes him losing money.
No it shouldn't be anymore.
It has been dangerous in the night among 22 and 23, then the servers have been shut down for investigation. Right now apt-get is working properly and I encourage everybody to do some upgrade.
At least, now I feel a little bit less silly when I think when I had been hacked... it happens to our gurus too.
that would explaing why i have been unable to access the site. i like to go and read the list of packages everyonce and a while and see what everything is. or i will read about a package or look for an app and see what the apt-get name is to install it.
this is a bunch of sh*t when ppl have to crack into a great site and stop most of the traffic. it is a dissipointing day when this happens.
It is truly sad that a bunch of spotted geeks decided that one of the great bastions of the GNU effort deserved to have this done to them - but everything happens for a reason, and looking into the future, this attack will only make the Debian project stronger.
Some cracker once said "We crack windows to prove that it is faulty". I guess that would apply to all systems, but when it comes to a great linux project such as Debian, all you have to do is send an email, which I seriously doubt is any more effort than actually cracking a system. So my conclusion is that it wasn't to make a point, merely to sabotage and piss me the fuck off.
Originally posted by dekket I dont think anyone said, nor thought, that it was.
Like the previous poster has said there are NO HACK/CRACK-proof systems in this world. The minute you go ONLINE, you are EXPOSED. Services are running, do not forget. HOWEVER, what distinguishes GNU/Linux and Debian in particular over certain proprietary OSes is the SWIFTNESS in RESPONSE i.e. in taking DECISIVE action and constructing an appropriate SOLUTION.
And the experience of having to re-patch, re-re-patch and re-re-re-patch (you get the idea ) security patches is literally NON-existent in Debian. And NEITHER does debian DENY an incident of security breach or DENY public knowledge of exploits (both REAL or Theoretical). It is the OPENNESS, TRANSPARENCY, DECISIVENESS and RAPIDNESS in RESPONSE that counts.