Isn't that only assuming that Wine's emulation isn't good enough to run a windows virus, trojan, or worm in it? I just get this feeling that all these people who think running windows apps in linux is safe are going to be bitten hard when a windows app they run in linux gets infected with a windows virus (through a buffer overflow in that program or the user running a malicious *windows* executable in linux) and wine's emulation allows it to trash their home directory (since many distributions map a user's entire home directory to a drive letter for windows apps run in wine).
Is there any way to have an ssh server slow down its responses on each successive login failure from an IP, so that the first failure might pause 2 seconds before even processing incoming data, 2nd would pause 4 seconds, 3rd would pause 8 seconds, etc (up to a limit) ?
With rules like that, does that mean someone could potentially spoof a TCP connect packet coming from a legitimate IP (such as maybe someone who regularly logs in via SSH to the server) and get them autobanned?
Those slashdot-enhanced sunglasses must be working well.
Control of what?
Is it possible to have a single autopackage that can detect what architecture it is being run in and install the appropriate binaries?
Ah, then AOL sucks even more than I thought.
Isn't that only assuming that Wine's emulation isn't good enough to run a windows virus, trojan, or worm in it? I just get this feeling that all these people who think running windows apps in linux is safe are going to be bitten hard when a windows app they run in linux gets infected with a windows virus (through a buffer overflow in that program or the user running a malicious *windows* executable in linux) and wine's emulation allows it to trash their home directory (since many distributions map a user's entire home directory to a drive letter for windows apps run in wine).
Are those long-standing bugs easy to reproduce? If not, then it could just be a man-power issue on why they aren't fixed yet.
You could use IMAP to grab the mail off of AOL's servers in any IMAP-capable email client, according to their site.
What if a customer wants a reformat and reinstall of windows and doesn't have a CD to do it from?
I've seen two adults do the same thing, but using telephones to talk to each other, when they have offices that are next door to each other.
Doesn't encryption generate overhead that could be detrimental to VoIP calls?
Is there any way to have an ssh server slow down its responses on each successive login failure from an IP, so that the first failure might pause 2 seconds before even processing incoming data, 2nd would pause 4 seconds, 3rd would pause 8 seconds, etc (up to a limit) ?
With rules like that, does that mean someone could potentially spoof a TCP connect packet coming from a legitimate IP (such as maybe someone who regularly logs in via SSH to the server) and get them autobanned?