AES, RSA, and all the rest are published standards. Now, some companies claim that they can't reveal what kind of encryption they use or it would severely degrade their product. I'm not naming names because I have none, this is just a vague recollection. Just go with the high level idea.
Well, how safe does that make you feel? Someone guesses it and all your security goes out the window? Here's the claim made by AES, and possibly by extension open source: We have a thousand eyes watching us, everyone knows how we work since it's published, and we're still secure. How's that for tough?
And, yes, more logically valid arguments like stats between number of open and closed source vulnerabilities found and other things suggested by other posters.
Sure the big blocky feel of pretty much every window manager out there sucks on my Eee, but this is one reason I stick with GTK+ 1.x. I don't have a 1280x1024 monitor just so I can see the same material I could see on an 800x600 10 years ago but with cleaner rounded edges.
And I have the bigger Eee. 1024x600 resolution, and some dialogs don't even fit on the screen.
I have an Athlon64 but run a 32 bit OS. I tried running a 64 bit virtual machine using VMWare Server 1.0.x a year or so ago and it worked. The performance was not noticeably poor.
So... assuming I haven't missed anything too obvious, my response would be "No, vmware is not getting a run for their money." Not today anyways.
For me, it's about the money. If I buy a laptop with Fedora Core 6 pre-installed (for the sake of argument), that money spent on the software would go to people who actually develop code for the system I bought, even if I nuke the hard drive and install $OTHER_DISTRO later. If I buy the same laptop with Windows on it, the money going to somebody with whom I have no interest in whatsoever.
So, put some kind of non-Windows OS on it. If the software costs money, make sure it goes to the people who make the OS. Don't let Microsoft have it. Personally I'm okay with Red Hat getting a small amount of money for the system that will be turned into Gentoo. Microsoft, not so much.
This is one of the big reasons we want Linux pre-installed -- evasion of the microsoft tax.
This whole DHT (trackerless) thing has broken private clients from the start.
The 'private' flag was introduced probably by Azureus when they made their own DHT. People should have banned it (it = Azureus) right then and there because adding the 'private' flag broke every torrent in existance that wanted to keep private.
Mainline/official supports their own DHT, but only uses it if a torrent is explicitly marked as trackerless. This is probably best for sites that want to stay private, but people have been bitching that "if the tracker goes down, I can't download. Therefore DHT rules."
So personally they can all go to hell for breaking our stuff. (Well, except for mainline).
This should hold the worm off until I get the chance to do a proper upgrade. I've got too much of a headache to recompile Apache and try to get all the modules I want working right now.
Standard disclaimer: this workaround should not be used by anyone who actually wants protection against this exploit.
I literally got the error message Unsupported Application Version! when I tried running it just now.
So, yeah, it's dead.
RedHat 3.0.3 (that's what the readme says)
on
Old Distributions?
·
· Score: 1
I have an old copy of InfoMagic Linux Developer's resource dating back to September 1996. It was a 6 CD set. I still have it lying around. It also had some Slackware and one disk has "Debian JE Dist." on it. I'm not selling it or mailing it, but maybe I could arrange an ISO transfer if you're willing to put up with my provider's speeds.
Just a random thought, but I recently played with a Dual-PPro motherboard (only one CPU inserted) that exhibited a strange problem. When running Linux, only 64MB RAM would work. The memory sticks were fine, but 128 MB of RAM would just cause the kernel to OOPS its brains out during Mandrake installation startup. The paramater mem= didn't do a thing.
I finally fixed it by bring up the BIOS and doing a [Load BIOS defaults] which must have done something to the chipset settings because suddenly it started working. Now 128MB of ram works beautifully and the system has been handling a load very well.
The BIOS settings may not be optimal for speed, but it can make a difference. Try writing down your BIOS settings and do a defaults reload.
I seem to remember in an issue of Linux Magazine a while back (at least 5 months or more) they had a section on creating a virtual interface "driver" which redirected packets to a real interface and would cause random packet loss (either as a percentage or a network outage of half a second every 10 seconds or something like that). I don't have the magazines handy, but I would imagine you could find it somewhere on their web site somewhere.
It was called "insane" and compiled as a kernel module.
I think the biggest obstacle to overcome would be the funny names programmers assign for their variables and functions. While I use dragon naturallyspeaking (which come with Corel WP Suite 8 Win9x) and it does support saying things like "OPEN BRACKET", a function name like vsprintf would be difficult to choose how to put that into normal words. And then you have to type in the name of the word into the add to dictonary feature and then say the word three times to program it. Seems like a lot for work for the whole LIBC.
Also, I feel that programming languages were really meant to be written by keyboard. Saying int i equals sizeof open bracket int close bracket times four semicolon just seems like too much work compared to entering it on a keyboard. Even then i will most likely be misinterpreted as eye.
I think its possible to write code in such a way, but perhaps too impractical. It would either involve creating a whole new, large dictonary for your programming needs or maybe your very own #include file to convert things like equals to =.
Where "start" is the first port in a range and "end" is the last (I use 0 and 7000). Also assumes you use eth0 for your cable modem, but you might use eth1. Any connection attempts will be logged to SYSLOG.
I run a more complicated ruleset, but it's based on things like this. I also use my computer as a firewall and masquerading server too...
How about letting your target audience get a chance to use it at no major risk. Point them to one of the loopback distributions that exist like Phat or maybe the latest RedHat. I find the best way to make people appreciate (sp?) something is to get a chance to try it for yourself. By using a loopback installation, they can install it as a single file/directory that can be uninstalled by simply deleting that file.
The advantage is that you don't need to wipe everything on your hard drive repartitioning just to get Linux working as a trial.
The downside is obvious: going through two layers of filesystems (ext2 filesystem written to a file on a vfat partition written to the hard drive) really slows down file access, and makes running Windows defrag a royal pain. Also, a ramdisk is generally required to load the loopback device which may use a small amount of memory on the system.
Then, if they decide to take up Linux, it can be installed for real using partitions.
What bugs me is whether he is talking about the kernel itself or the software it runs.
If Netscape crashes under Windows, I can't call that a Windows bug, even though I may want to. That's a bug in netscape. If KERNEL32.DLL crashes, then you can call that a Windows bug, and I've had it crash plenty. If EXPLORER under Windows crashes, can you call that a bug in Windows or a bug in the software it ships with? I find this the source of many Windows bugs: too much integration. Internet exploder, DirectX (which isn't too bad), and an Active Desktop is too much space to go wrong in. If IE crashes, being so closely integrated into the system, it may take all of Windows with it.
Now if there's a bug in BIND under Linux (and there have been), you can't say that it's a fault in Linux. If netscape/mozilla crashes in Linux, it's not Linux's fault. If the kernel panics, then you can call it a Linux bug (unless you happen to ungzip a file to/dev/mem instead of/dev/ram (my mistake, I won't hold it against Linux)).
So, is Fred referring to bugs in the software that Linux ships with, or the kernel itself as being full of bugs? He just doesn't say enough in the article.
This has been present for FOUR years? That has really got to hurt Microsoft's reputation. Easy to use, absolutely. User-friendly? Of course! Secure? Umm, I'll take a rain check on that (patch released a month later).
Microsoft has been known for making buggy software, but whenever Windows crashes on me, it's (usually) because of an extreme load or some program crashing that ends up taking kernel32 down with it. To actually and purposely place a security flaw in a program is just unthinkable. Geez, what do you say to something like that?!?
Things just arn't going to well for them recently. What a shame.
My best recommendation would be to go to the ALSA Project web page. They deal with the creation of drivers for a lot of sound cards. I'm not sure if your particular version is supported, but it's worth a try. My Sound Blaster live was available. Maybe you can ask the coders about support if it doesn't. Does this sound card support other formats? Does it have features like Sound Blaster 16 compatibility or something along that line? Just a thought...
Assuming you get your IP address from a DHCP server, just install "DHCPCD" when you install RedHat. It's a DHCP client and will auto-configure your interface once it's set up and do the usual DHCP stuff. You can configure it from Linuxconf as one of your ethernet interfaces. PPPd usually sets the default gateway when you connect on it's own.
Slashdot Mirror
AES, RSA, and all the rest are published standards. Now, some companies claim that they can't reveal what kind of encryption they use or it would severely degrade their product. I'm not naming names because I have none, this is just a vague recollection. Just go with the high level idea.
Well, how safe does that make you feel? Someone guesses it and all your security goes out the window? Here's the claim made by AES, and possibly by extension open source: We have a thousand eyes watching us, everyone knows how we work since it's published, and we're still secure. How's that for tough?
And, yes, more logically valid arguments like stats between number of open and closed source vulnerabilities found and other things suggested by other posters.
Sure the big blocky feel of pretty much every window manager out there sucks on my Eee, but this is one reason I stick with GTK+ 1.x. I don't have a 1280x1024 monitor just so I can see the same material I could see on an 800x600 10 years ago but with cleaner rounded edges.
And I have the bigger Eee. 1024x600 resolution, and some dialogs don't even fit on the screen.
I have an Athlon64 but run a 32 bit OS. I tried running a 64 bit virtual machine using VMWare Server 1.0.x a year or so ago and it worked. The performance was not noticeably poor.
So... assuming I haven't missed anything too obvious, my response would be "No, vmware is not getting a run for their money." Not today anyways.
Looks like a variation (or maybe a dup) of this.
For me, it's about the money. If I buy a laptop with Fedora Core 6 pre-installed (for the sake of argument), that money spent on the software would go to people who actually develop code for the system I bought, even if I nuke the hard drive and install $OTHER_DISTRO later. If I buy the same laptop with Windows on it, the money going to somebody with whom I have no interest in whatsoever.
So, put some kind of non-Windows OS on it. If the software costs money, make sure it goes to the people who make the OS. Don't let Microsoft have it. Personally I'm okay with Red Hat getting a small amount of money for the system that will be turned into Gentoo. Microsoft, not so much.
This is one of the big reasons we want Linux pre-installed -- evasion of the microsoft tax.
The 'private' flag was introduced probably by Azureus when they made their own DHT. People should have banned it (it = Azureus) right then and there because adding the 'private' flag broke every torrent in existance that wanted to keep private.
Mainline/official supports their own DHT, but only uses it if a torrent is explicitly marked as trackerless. This is probably best for sites that want to stay private, but people have been bitching that "if the tracker goes down, I can't download. Therefore DHT rules."
So personally they can all go to hell for breaking our stuff. (Well, except for mainline).
Something related from a previous (ask) slashdot story.
http://slashdot.org/article.pl?sid=03/03/07/153223 3
# cd
# touch
# chattr +i
# exit
This should hold the worm off until I get the chance to do a proper upgrade. I've got too much of a headache to recompile Apache and try to get all the modules I want working right now.
Standard disclaimer: this workaround should not be used by anyone who actually wants protection against this exploit.
So, yeah, it's dead.
I have an old copy of InfoMagic Linux Developer's resource dating back to September 1996. It was a 6 CD set. I still have it lying around. It also had some Slackware and one disk has "Debian JE Dist." on it. I'm not selling it or mailing it, but maybe I could arrange an ISO transfer if you're willing to put up with my provider's speeds.
Reply email address: god at dehacked.2y.net
Just a random thought, but I recently played with a Dual-PPro motherboard (only one CPU inserted) that exhibited a strange problem. When running Linux, only 64MB RAM would work. The memory sticks were fine, but 128 MB of RAM would just cause the kernel to OOPS its brains out during Mandrake installation startup. The paramater mem= didn't do a thing.
I finally fixed it by bring up the BIOS and doing a [Load BIOS defaults] which must have done something to the chipset settings because suddenly it started working. Now 128MB of ram works beautifully and the system has been handling a load very well.
The BIOS settings may not be optimal for speed, but it can make a difference. Try writing down your BIOS settings and do a defaults reload.
It was called "insane" and compiled as a kernel module.
Also, I feel that programming languages were really meant to be written by keyboard. Saying int i equals sizeof open bracket int close bracket times four semicolon just seems like too much work compared to entering it on a keyboard. Even then i will most likely be misinterpreted as eye.
I think its possible to write code in such a way, but perhaps too impractical. It would either involve creating a whole new, large dictonary for your programming needs or maybe your very own #include file to convert things like equals to =.
Don't know how to do this with netfilter, but here's a command to run as root which will remove these small annoyances in 2.2.x kernels:
ipchains -A input -i eth0 --desination-port start:end -j DENY -l -y -p tcp
Where "start" is the first port in a range and "end" is the last (I use 0 and 7000). Also assumes you use eth0 for your cable modem, but you might use eth1. Any connection attempts will be logged to SYSLOG.
I run a more complicated ruleset, but it's based on things like this. I also use my computer as a firewall and masquerading server too...
How about letting your target audience get a chance to use it at no major risk. Point them to one of the loopback distributions that exist like Phat or maybe the latest RedHat. I find the best way to make people appreciate (sp?) something is to get a chance to try it for yourself. By using a loopback installation, they can install it as a single file/directory that can be uninstalled by simply deleting that file.
The advantage is that you don't need to wipe everything on your hard drive repartitioning just to get Linux working as a trial.
The downside is obvious: going through two layers of filesystems (ext2 filesystem written to a file on a vfat partition written to the hard drive) really slows down file access, and makes running Windows defrag a royal pain. Also, a ramdisk is generally required to load the loopback device which may use a small amount of memory on the system.
Then, if they decide to take up Linux, it can be installed for real using partitions.
What bugs me is whether he is talking about the kernel itself or the software it runs.
/dev/mem instead of /dev/ram (my mistake, I won't hold it against Linux)).
If Netscape crashes under Windows, I can't call that a Windows bug, even though I may want to. That's a bug in netscape. If KERNEL32.DLL crashes, then you can call that a Windows bug, and I've had it crash plenty. If EXPLORER under Windows crashes, can you call that a bug in Windows or a bug in the software it ships with? I find this the source of many Windows bugs: too much integration. Internet exploder, DirectX (which isn't too bad), and an Active Desktop is too much space to go wrong in. If IE crashes, being so closely integrated into the system, it may take all of Windows with it.
Now if there's a bug in BIND under Linux (and there have been), you can't say that it's a fault in Linux. If netscape/mozilla crashes in Linux, it's not Linux's fault. If the kernel panics, then you can call it a Linux bug (unless you happen to ungzip a file to
So, is Fred referring to bugs in the software that Linux ships with, or the kernel itself as being full of bugs? He just doesn't say enough in the article.
This has been present for FOUR years? That has really got to hurt Microsoft's reputation. Easy to use, absolutely. User-friendly? Of course! Secure? Umm, I'll take a rain check on that (patch released a month later).
Microsoft has been known for making buggy software, but whenever Windows crashes on me, it's (usually) because of an extreme load or some program crashing that ends up taking kernel32 down with it. To actually and purposely place a security flaw in a program is just unthinkable. Geez, what do you say to something like that?!?
Things just arn't going to well for them recently. What a shame.
My best recommendation would be to go to the ALSA Project web page. They deal with the creation of drivers for a lot of sound cards. I'm not sure if your particular version is supported, but it's worth a try. My Sound Blaster live was available. Maybe you can ask the coders about support if it doesn't. Does this sound card support other formats? Does it have features like Sound Blaster 16 compatibility or something along that line? Just a thought...
Assuming you get your IP address from a DHCP server, just install "DHCPCD" when you install RedHat. It's a DHCP client and will auto-configure your interface once it's set up and do the usual DHCP stuff. You can configure it from Linuxconf as one of your ethernet interfaces. PPPd usually sets the default gateway when you connect on it's own.