I'd rather see most binary packages compiled for the 386 instruction set. If you really need/want the speed boost (unlikely, but certainly possible) you can just recompile from the source RPM's. And if you're running a Pentium class or faster, that probably won't even take too long. If packages come out compiled using the Pentium instruction set, then I'm going to be up the proverbial estuary without a paddle if I want to install on, say, a 486.
SSH can be configured to forward arbitrary ports over a secure connection. This is often done automagically for X, but you probably need to explicitly tell it to forward anything else. What happens is that the client listens on a local port (say 9000) and forwards any connections to it over the secure connection to the server. At the server, this encrypted stream is hooked up to a local port (say 110). At the client, you have your POP fetcher check localhost:9000 instead of remote:110. Neither side knows about the encryption. For details on how to set this up, you can check the ssh man page. On the server, you can block external access to port 110 so that only local connections can be made to it (from the ssh daemon, for example) to prevent remote exploits against a possibly insecure daemon.
As a previous poster indicated (humorously), you should use SSH for any remote administration. You can also use SSH along with a POP or IMAP server so that your password isn't passed in cleartext everytime you check your e-mail. (There are other ways to encrypt your password over POP, but I'm not sure about IMAP. I would think there is though.) For file transfer, you can use SFTP, SCP, or regular FTP forwarded over SSH.
It's already been done and it's called (strangely enough) SLINT. Unfortunately, it's not available to the public. Perhaps some polite inquiries could persuade them to release it? Or maybe not. Anyway, it's there.
Yes, it is nice. In fact, that's the entire idea of having plenty of choice in which OS you use. Apparently Linux worked out better for him. He'll use Linux. You, I assume, will use a BSD. And I'll use whatever works best for me. Don't bitch someone out for using the tool best suited to them, it only makes you look foolish.
Sure, that's reasonable. Gaining illegitimate access to a computer should be prosecuted no matter what is done with that access. (Be it destabilizing the world economy or reading/.)
For the most part, I agree with you. However, I'm not impressed with the way you slip sniffing in there with things that should be illegal. First of all, sniffing network traffic has plenty of useful applications (perhaps more useful applications than malicious) such as testing networking software (I do this all the time, it's great for helping track down otherwise inexplicable problems), keeping tabs on network usage, and tracking down malicious activity. Many IDS's could be described as glorified network sniffers. Besides all that, sniffing does not harm anyone. Should we make listening to other conversations in a restaraunt illegal? No. If people send data on a wire past my machine, I think that I have a right to know what that data is. Especially if it's _my_ data (as in the useful applications pointed out above). To go back to the restaurant example, if people do not wish to be overheard, the can speak more quietly or carry on their conversation elsewhere. On a network, people can either choose to use strong encryption or limit their traffic to a known secure network. That aside, I'll restate that I do agree with your other points.
The soccer team is in brazil and already has a.com.br as they should. The guy previously having the domain name was not using it for commercial purposes. He should have been given a pro-rated refund on his registration and the domain should have been put back in the pool. Simple as that. If you're not going to play by the rules, you shouldn't bitch when somebody else breaks them.
The company isn't holding a gun to their head to make them cheat. If they're dishonest and cheaters, then they're going to be whether they have to tools to do so or not. That's something inherent to the person. Furthermore, this would be a very useful thing for game developers. And don't tell me "then they should only give it to developers." Even if they did, it would still get out.
What it comes down to is that people need to take some fucking responsibility in their lives and not depend on the gov't and corporations to look out for them.
Slashdot Mirror
Quality troll. Keep 'em coming :)
I'd rather see most binary packages compiled for the 386 instruction set. If you really need/want the speed boost (unlikely, but certainly possible) you can just recompile from the source RPM's. And if you're running a Pentium class or faster, that probably won't even take too long. If packages come out compiled using the Pentium instruction set, then I'm going to be up the proverbial estuary without a paddle if I want to install on, say, a 486.
SSH can be configured to forward arbitrary ports over a secure connection. This is often done automagically for X, but you probably need to explicitly tell it to forward anything else. What happens is that the client listens on a local port (say 9000) and forwards any connections to it over the secure connection to the server. At the server, this encrypted stream is hooked up to a local port (say 110). At the client, you have your POP fetcher check localhost:9000 instead of remote:110. Neither side knows about the encryption. For details on how to set this up, you can check the ssh man page. On the server, you can block external access to port 110 so that only local connections can be made to it (from the ssh daemon, for example) to prevent remote exploits against a possibly insecure daemon.
Many companies use an OS like Win98 where any bozo can set the promisc flag on their card.
As a previous poster indicated (humorously), you should use SSH for any remote administration. You can also use SSH along with a POP or IMAP server so that your password isn't passed in cleartext everytime you check your e-mail. (There are other ways to encrypt your password over POP, but I'm not sure about IMAP. I would think there is though.) For file transfer, you can use SFTP, SCP, or regular FTP forwarded over SSH.
Nice technique, but you lose style points for posting it AC.
It's already been done and it's called (strangely enough) SLINT. Unfortunately, it's not available to the public. Perhaps some polite inquiries could persuade them to release it? Or maybe not. Anyway, it's there.
It doesn't a single thing. The only point to it was to upset you and reduce you to name-calling. It's served it's purpose now. Thanks.
Obviously because he would like an option to not see this article or your mindless posts to it.
fuckhead
homophobe.
What it comes down to is that people need to take some fucking responsibility in their lives and not depend on the gov't and corporations to look out for them.
Karma be damned
Um... so basically you'd need a beowulf cluster of these to get decent performance?