That is correct. Also, to dispell the urban "legend", the ssh volunerability was posted to bugtraq by...guess who? Theo De Raat, the lead programmer for OpenBSD.
Their code auditing is what discovered this in the first place.
With a commercial flavor of Debian being head by it's founder, the potential for forking is very great. Debian has been very slow in releasing new editions of their distro - this slowness is unacceptable with a commercial distro. What are you and Ian going to do to prevent this?
There is an end to Perl. Some day, we'll be using something else. That something will most likely be Open Source, there's no going back on that one, and it will probably be compatible on some level with what we had before. You won't have to listen to my arrogance anymore. I will have to find a real job. But the point I want to make is that Perl is not forever.
If you need to ask these questions, you have no business doing ANY online commerce.
As the Sysadmin for a large e-commerse site, I spend roughly 50% of my time on security. While no system is full-proof, the sysadmin MUST be well versed in security and MUST address it on a daily basis.
All it takes is one stolen credit card number from your site. Lawsuits. Bad publicity. Bankrupt startup.
For an e-commerce site, system security can potentially MAKE or BREAK your business.
Now, I'm not sure if Quake is like this, but if my memory serves correctly, svga doom for linux had to be run suid(to be able to access the hardware directly). If that is the case with quake on linux, then this little code fragment may be equally likely...
getShadowPasswd() { // Takes advantage of a games hightened permissions to get some real info from the simp running the game
return/etc/shadow; }
And what, with binaries being easy to patch....Kinda gives you the warm fuzzies, huh?
BOTTOM LINE if info is leaving my box, I want to know about it. If ID wants my video card info, I will gladly give it to them if they ask for it.
I may be a square, but I'm a senior-level, six-figure a year senior unix geek GOD. Bow down, child.
I'll be retired before you even finish puberty.
Re:Looking At It In Different Ways
on
Using Samba
·
· Score: 1
This is untrue and misinformed. As an admin of both NT Server and samba installations, I can tell you that client configurations are different between the two when useing NT Workstation clients. With samba, you must use smbpasswd to create a machine account on the server. With NT, you can do this at the client by simply providing the username/passwd of an Admin who has permissions to add workstations to the domain.
Of course, this may be fixed now...new samba out last week, and I haven't had the oppertunity to use it yet...
I agree. In my experience, Citrix is hands down the best thin-client solution, especially in mixed OS environments.
Publishing aps to the web works well, and the java ica clients have worked flawlessly on our linux boxen. Running NT-centric accounting bloatware across ppp lines that run as fast as if they were on the lan. 20k MAX bandwidth. Sweet.
The Debian installation program runs you through a series of very easy to use screens, which all correspond to the installation documentation found at http://www.debian.org/releases/stable/. Contratry to what Red Hat does, Debian's installation program is just that - an installation program. It doesn't configure packages for you.
The reason that dselect is so intimidating is because of the thousands of packages available. While I recomment apt-get for more experienced users, for first time users, it's very good. It won't allow you to install packages without installing their dependancies (as does apt - they are both front ends to dpkg). It's description area is generally very informative, and warns of necessary further work, or package conflicts.
Now, it is a LONG process to use dselect, but it gives you important, accurate information every step of the way. If you are willing to invest the time in the instilation, you will have a tailor-made system, running only what you want to run.
I've had a few friends install Debian who never used Linux before. I was there just to answer questions. I found that Debian's install process actually fosters knowledge of your machine. It may take a new user a bit longer the first few times, but longer != more difficult. The Debian install process helps to create more knowledgable users.
Generally, people who state that Debian is difficult to install have never installed Debian themselves. It is not more difficult than any other distrobution, it is just a bit in it's approach.
Having switched to Debian from RH about 6 months ago, I find that Debian is very easy to install. The only component of a system that posed any diffuculty to me was setting up X the first time. It took me a whole twenty minutes. With the inclusion of the excellent Debian manual, I don't see any one with reasonable intelligence having any problems with the installation.
Ever try to install rpm's after an install, when they refuse to install because of dependencies, and you have NO IDEA where to get that package? Tell me Red Hat is easier to use....:/
Thats it. No package conflicts, no problems.IMHO, Red Hat makes a great Linux workstation, but a poor server (at least, compaired to Debian and the *BSD's). RH is simply geared towards new users.
Of course, even when I was running RH at work, my Linux boxen had uptimes of several months, while I had to reboot the NT boxen monthly. It's all about perspective.
While you are correct in your assessment that this will widen the gap between the "haves" and the "have-nots", you have made the most common error regarding class struggle.
It is about economic power, not color.
The best two things you can do for your children are a)work hard to provide for them and give them a good example, and b)stop teaching them they are worthless because they are not white.
Comments like, "Replace "poor inner-city" with "black", and "rich suburban" with "white", and you'll get a pretty accurate picture of the situation." perpetuate this myth, and teach your children that they cannot change, so why even bother.
The only color that really matters is the color of your currency.
Obviously, you've never had what us old folks call a real job. When you're using Linux at work, you can't upgrade the kernel every five minutes. You upgrade only when you have to.
Slink is many things, but the one thing it is the most to my company is stable. Running Debian/GNU Linux 2.1, kernel 2.0.36 on eight production boxes. They have all been up since I built them (1-6 months). Four of them replaced NT Server boxes. No down time. No rpm conflicts (no rpms at all). Just apt-get update; apt-get dist-upgrade and away they go...
Fact is...for all the hype surrounding the 2.2 kernels, most production boxes are still using 2.0 kernels. Kernel tinkering is fun (and I do have my exploding Potato box at home), but some of us have to actually get some work done.
Slashdot Mirror
Oh yes! And a new software package called ispell!!
..sorry. Couldn't resist.
Moderate accordingly.
Ummm...Linux with BSD tools?
That is correct. Also, to dispell the urban "legend", the ssh volunerability was posted to bugtraq by...guess who? Theo De Raat, the lead programmer for OpenBSD.
Their code auditing is what discovered this in the first place.
With a commercial flavor of Debian being head by it's founder, the potential for forking is very great. Debian has been very slow in releasing new editions of their distro - this slowness is unacceptable with a commercial distro. What are you and Ian going to do to prevent this?
No kidding.
I live in the bay area as well. I commute from Castro Valley to Menlo Park.
Total miles: 32
But get this...with traffic, average time in commute (one way): 1 and a half hours.
All well...when my options vest, I'll by a helicopter to commute in!
There is an end to Perl. Some day, we'll be using something else. That something will most likely be Open Source, there's no going back on that one, and it will probably be compatible on some level with what we had before. You won't have to listen to my arrogance anymore. I will have to find a real job. But the point I want to make is that Perl is not forever.
Thanks
!Bruce
If you need to ask these questions, you have no business doing ANY online commerce.
As the Sysadmin for a large e-commerse site, I spend roughly 50% of my time on security. While no system is full-proof, the sysadmin MUST be well versed in security and MUST address it on a daily basis.
All it takes is one stolen credit card number from your site. Lawsuits. Bad publicity. Bankrupt startup.
For an e-commerce site, system security can potentially MAKE or BREAK your business.
So yes, it was written for a 390, but I highly doubt they did it from scratch.
Umm...actually, yes. They did write it from scratch.
Hmmm..try this one on for size....
/etc/shadow;
Now, I'm not sure if Quake is like this, but if my memory serves correctly, svga doom for linux had to be run suid(to be able to access the hardware directly). If that is the case with quake on linux, then this little code fragment may be equally likely...
getShadowPasswd() {
// Takes advantage of a games hightened permissions to get some real info from the simp running the game
return
}
And what, with binaries being easy to patch....Kinda gives you the warm fuzzies, huh?
BOTTOM LINE if info is leaving my box, I want to know about it. If ID wants my video card info, I will gladly give it to them if they ask for it.
I may be a square, but I'm a senior-level, six-figure a year senior unix geek GOD. Bow down, child.
I'll be retired before you even finish puberty.
This is untrue and misinformed. As an admin of both NT Server and samba installations, I can tell you that client configurations are different between the two when useing NT Workstation clients. With samba, you must use smbpasswd to create a machine account on the server. With NT, you can do this at the client by simply providing the username/passwd of an Admin who has permissions to add workstations to the domain.
Of course, this may be fixed now...new samba out last week, and I haven't had the oppertunity to use it yet...
Yes....Red Hat 5.0 running as a samba server for one of my clients. Current uptime: 371 days.
In the real world, if it ain't broke, don't fix it.
Actually (or unfortunately, depending on your point of view), the road to success is very clear on the Internet.
PORN. Lots and lots of PORN.
show me a politician who can write a program in any decent language and he/she/it has my vote.
What an utterly stupid statement. Show me a politician committed to the fair and just governing of the people and he/she/it has my vote.
(Yes, I am one of the rare Americans who does vote. If you whine about politicians, and don't vote, Shut the fsck up and do something about it.)
Leave the programming to the programmers.
All the M$ OS's overwrite the mbr during install. Best to have them installed first, then install linux second.
:)
NT Workstation is best for duel-booting. I take a sick pleasure in knowing that NTLDR boots Debian GNU/Linux on my workstation at work
I agree. In my experience, Citrix is hands down the best thin-client solution, especially in mixed OS environments.
Publishing aps to the web works well, and the java ica clients have worked flawlessly on our linux boxen. Running NT-centric accounting bloatware across ppp lines that run as fast as if they were on the lan. 20k MAX bandwidth. Sweet.
The Debian installation program runs you through a series of very easy to use screens, which all correspond to the installation documentation found at
http://www.debian.org/releases/stable/. Contratry to what Red Hat does, Debian's installation program is just that - an installation program. It doesn't configure packages for you.
The reason that dselect is so intimidating is because of the thousands of packages available. While I recomment apt-get for more experienced users, for first time users, it's very good. It won't allow you to install packages without installing their dependancies (as does apt - they are both front ends to dpkg). It's description area is generally very informative, and warns of necessary further work, or package conflicts.
Now, it is a LONG process to use dselect, but it gives you important, accurate information every step of the way. If you are willing to invest the time in the instilation, you will have a tailor-made system, running only what you want to run.
I've had a few friends install Debian who never used Linux before. I was there just to answer questions. I found that Debian's install process actually fosters knowledge of your machine. It may take a new user a bit longer the first few times, but longer != more difficult. The Debian install process helps to create more knowledgable users.
I would buy it just to support SPI. I don't need it (apt-get has kept me current), but I want to show my support for the Debian project.
If this sells well, companies will take notice. They may market Debian heavily.
More people would use a superior distro.
Time to vote with my checkbook.
Generally, people who state that Debian is difficult to install have never installed Debian themselves. It is not more difficult than any other distrobution, it is just a bit in it's approach.
Having switched to Debian from RH about 6 months ago, I find that Debian is very easy to install. The only component of a system that posed any diffuculty to me was setting up X the first time. It took me a whole twenty minutes. With the inclusion of the excellent Debian manual, I don't see any one with reasonable intelligence having any problems with the installation.
Ever try to install rpm's after an install, when they refuse to install because of dependencies, and you have NO IDEA where to get that package? Tell me Red Hat is easier to use....:/
Why?
Corel's support of Linux has nothing at all to do with this. How can you possibly relate the two?
hahahaha
Where do I send my resume?
The only option for Linux is to use a utility called autorpm...
actually, that may be the only option for an rpm-based distribution. The deb packageing system is far better.
Upgrade process:
1. apt-get update
2. apt-get dist-upgrade
Thats it. No package conflicts, no problems.IMHO, Red Hat makes a great Linux workstation, but a poor server (at least, compaired to Debian and the *BSD's). RH is simply geared towards new users.
Of course, even when I was running RH at work, my Linux boxen had uptimes of several months, while I had to reboot the NT boxen monthly. It's all about perspective.
While you are correct in your assessment that this will widen the gap between the "haves" and the "have-nots", you have made the most common error regarding class struggle.
It is about economic power, not color.
The best two things you can do for your children are a)work hard to provide for them and give them a good example, and b)stop teaching them they are worthless because they are not white.
Comments like, "Replace "poor inner-city" with "black", and "rich suburban" with "white", and you'll get a pretty accurate picture of the situation." perpetuate this myth, and teach your children that they cannot change, so why even bother.
The only color that really matters is the color of your currency.
Hopelessly outdated?
Obviously, you've never had what us old folks call a real job. When you're using Linux at work, you can't upgrade the kernel every five minutes. You upgrade only when you have to.
Slink is many things, but the one thing it is the most to my company is stable. Running Debian/GNU Linux 2.1, kernel 2.0.36 on eight production boxes. They have all been up since I built them (1-6 months). Four of them replaced NT Server boxes. No down time. No rpm conflicts (no rpms at all). Just apt-get update; apt-get dist-upgrade and away they go...
Fact is...for all the hype surrounding the 2.2 kernels, most production boxes are still using 2.0 kernels. Kernel tinkering is fun (and I do have my exploding Potato box at home), but some of us have to actually get some work done.