@zakany001: Okay, that one gets a hearty "LOL" from me - that's a great use of it.

@djsmiley2k: I was mortified when I found out the SSID is the salt, too. It makes dictionary attacks that much easier, since you can compile a list of common SSIDs as a starting point.

@Alex Swanson: Monitor mode may not work as expected with all wireless hardware, though. I have three wireless adapters and two of them have strange behaviour, only picking up ARP.

@Limbero: Don't forget that it's important to change the SSID away from the default. SSID names are used for the salt, so non-standard (and longer) names help improve the security, as well as longer passphrases.

@ascoteton77: MAC filtering is security theatre - spoofing is trivial, so all it really does is make you feel like you're secure because you're making it less convenient for you to connect legitimate machines to the network.

I'm loving Evil Week so far. The articles have been fun and the focus on things like understanding security by understanding how to circumvent it is smart.

@LuckyCharms: I think they're using the per-app settings thing nvidia provides. It's handled independently of Direct3d and OpenGL and works on games that don't offer direct support.

@KatsumeBlisk: Another distro to try is Debian. Most everything you know from Ubuntu will apply since it's Debian's offspring, minus some end-user tweaking Canonical does.

@Mark Hunt: Yep, that's the name I was trying to remember, thanks. To add some extra info: the Wikipedia article on deferred shading explains how it works and why AA doesn't work with it.

@kondrik: You should still be able to use JACK with GNOME, but pulseaudio is going to be integrated with everything better. GNOME was made with ESD in mind, and pulseaudio is compatible with ESD (it's basically ESD's replacement) so sticking with pulseaudio for network transport would probably be your best bet.

Anti-aliasing has been around for a long time, but many newer games don't allow you to adjust its settings

@Graviton1066: And if they do something that isn't inradical, you can say they're being irradical.

@KatsumeBlisk: In my experience, KDE and GNOME are both sluggish on ancient hardware (>7 years old) if compared to lighter environments, but seem mostly comparable on anything with >=512M RAM. KDE tries to use as many features as it thinks your system can handle, so it might be slower "out of the box" but it's easy…

@toxycated: It's more of a GNOME thing. GNOME design philosophy is to hide all but the most common features, which means you have to do the GNOME equivalent of registry hacking (gconf editing) to adjust more obscure settings, assuming they can be adjusted at all.

@kondrik: It's possible, but it's far from trivial to set up. If you use pulseaudio I can't help, but I can give you an idea of what I do with KDE and JACK in case you go that route. I just verified the procedure in KDE4, and it's pretty well integrated with JACK. If you use GNOME you're probably better off with…

@scoobertron: Definitely a bit on the complex side due to a different focus than pulseaudio. Hard to disagree there.

@Whitson Gordon: Just make sure to update the firmware on the printer if you're using wireless. A lot of the wireless-capable HP printers and scanners have a firmware bug that can cause it to hard-lock when you enable wireless with certain SSIDs. If you've already enabled it and it hasn't died you got lucky, but…

@Prairie Moon: Yep, I know exactly what you meant, which is why I threw in the extra functionality for you to chew on ;) Solving the puzzle is usually more fun than actually using the answer.

@Whitson Gordon: Seems like the only area that's a consistent thorn in your side (at least for me) with Linux is printing. Wireless might be annoying to set up if you piss off the broadcom gods, but you can still get it going eventually. Printing can be annoying no matter what OS, and some vendors (*cough* Lexmark)…

@Whitson Gordon: It's hard to blame the companies for not spending time and money on it, but I do blame them for not making it easier for the people that care enough to do it for them. A lot of times it's something as simple as documenting their API and letting the community do the work for them, and they won't even…