Re:Well, they may have a point somewhere in there.
on
ADTI Whitepaper Released
·
· Score: 2, Insightful
"Another security concern is that the primary distribution channel for GPL open source is the Internet. As opposed to proprietary vendors, open source is freely downloaded. However, software in the public domain could contain a critical problem, a backdoor or worse, a dangerous virus."
While what you say is technicaly true, at least with open source, hackers(as in the jargon file definition) have a chance to go over the source and fix any back doors implemented. If you only receive binary files, who's to say that the company themselves hasn't inserted a backdoor or left a myriad of security holes unfixed. The above quote is a bad way of looking at it, because the exact same arguement can be applied to closed source.
Recently I've had quite a bit of experience with a newbie linux user.(ie my roommate) As he doesn't have a comp, I installed linux on a POS (tm) machine and set it up on his desk for his personal use.
There seem to be few problems with his use of the computer. However, he has been getting increasingly beligerant about the fact that I haven't had the time to set up direct 3d rendering on the machine so he could play RTCW.
As I use Slackware Linux full time on my computer I think that GNU/Linux is quite ready for the desktop but not necessarily the desktop of a non do-it-yourselfer. Remember these are people used to playing games out of the box or not having to go through too technical of a setup to get them working. EZ Configuration is tops on my list for new users who don't necessarily have the time to RATFM(read all the...).
This document is no more than a formalization of @Stake and Microsoft's desire to see the public disclosure that takes place on Security Focus and Cert come to a grinding halt. In their process, the community isn't informed of a the hole/vulnerability until after there's a fix.
I feel that this gives the companies no motivation to fix the hole. I would instead suggest that when the "reporter" informs the company, The company receives a grace period of 30 days to work on a fix after such a point the "reporter" could come forward, and release the hole publically if he/she/it felt that the company wasn't making a good faith effort to fix the problem. Of course this whole process is null and void if the program is open source/free software and the "reporter" releases a patch for the flaw at the same time the "reporter" releases the flaw.
Who's going to pay for all of the O'Reilly Books if they do use linux? And then you bet there'll be a flame war about which distro to use.
Slackware isn't dead. It's just not for everyone.
on
Is Slackware Fading Away?
·
· Score: 5, Informative
I don't think Slackware is quite dead. I switched to Slackware 7.0 after Red Hat screwed up my partition tables. I now use Slackware 8.0 and haven't looked back since or regretted my dicision. Sure Slackware takes a little more time to maintain, but the people who use Slakware aren't above using./configure; make; make install to get the programs they need/want.
I've never had a problem with the stability of a Slackware distro because Patrick Volkerding puts out a quality distro with out a ot of bloat.
On behalf of Victoria's Secret, I would like to patent cleavage as they are obviously the inventor of the male attracting aparatus known as cleavage. Their tool for creating this strange and yet powerful device is underwire.
"Another security concern is that the primary distribution channel for GPL open source is the Internet. As opposed to proprietary vendors, open source is freely downloaded. However, software in the public domain could contain a critical problem, a backdoor or worse, a dangerous virus."
While what you say is technicaly true, at least with open source, hackers(as in the jargon file definition) have a chance to go over the source and fix any back doors implemented. If you only receive binary files, who's to say that the company themselves hasn't inserted a backdoor or left a myriad of security holes unfixed. The above quote is a bad way of looking at it, because the exact same arguement can be applied to closed source.
Recently I've had quite a bit of experience with a newbie linux user.(ie my roommate) As he doesn't have a comp, I installed linux on a POS (tm) machine and set it up on his desk for his personal use.
...).
There seem to be few problems with his use of the computer. However, he has been getting increasingly beligerant about the fact that I haven't had the time to set up direct 3d rendering on the machine so he could play RTCW.
As I use Slackware Linux full time on my computer I think that GNU/Linux is quite ready for the desktop but not necessarily the desktop of a non do-it-yourselfer. Remember these are people used to playing games out of the box or not having to go through too technical of a setup to get them working. EZ Configuration is tops on my list for new users who don't necessarily have the time to RATFM(read all the
Whoops my bad. Much to my chagrin, I only read the first several sections. Thank you for pointing out my error.
This document is no more than a formalization of @Stake and Microsoft's desire to see the public disclosure that takes place on Security Focus and Cert come to a grinding halt. In their process, the community isn't informed of a the hole/vulnerability until after there's a fix.
I feel that this gives the companies no motivation to fix the hole. I would instead suggest that when the "reporter" informs the company, The company receives a grace period of 30 days to work on a fix after such a point the "reporter" could come forward, and release the hole publically if he/she/it felt that the company wasn't making a good faith effort to fix the problem. Of course this whole process is null and void if the program is open source/free software and the "reporter" releases a patch for the flaw at the same time the "reporter" releases the flaw.
Ponder that my friends.
T.A. Forever
Who's going to pay for all of the O'Reilly Books if they do use linux? And then you bet there'll be a flame war about which distro to use.
I don't think Slackware is quite dead. I switched to Slackware 7.0 after Red Hat screwed up my partition tables. I now use Slackware 8.0 and haven't looked back since or regretted my dicision. Sure Slackware takes a little more time to maintain, but the people who use Slakware aren't above using ./configure; make; make install to get the programs they need/want.
I've never had a problem with the stability of a Slackware distro because Patrick Volkerding puts out a quality distro with out a ot of bloat.
Thanks for such a good distro Patrick.
Adam
On behalf of Victoria's Secret, I would like to patent cleavage as they are obviously the inventor of the male attracting aparatus known as cleavage. Their tool for creating this strange and yet powerful device is underwire.