Clan x86
Technical (Development, Security, etc.) => Unix / Linux Discussion => Topic started by: Krazed on October 28, 2009, 10:30:10 am
-
Every two years the Ubuntu project releases a long-term stable version of their distribution with support/updates for three years on the desktop software, and five years on the server. Personally, I'm definitely going to attempt to use this release for long-term. The aim towards UI, boot speeds, and just overall speed is a pretty awesome.
I personally use Ubuntu because it's so easy and painless. Five or six years ago I would've spent hours bothering iago on AIM trying to get my wireless working with Slackware 9.1, whereas with Ubuntu it works on initial install!
Actual Announcement: http://fridge.ubuntu.com/node/1916
-
I wouldn't blame Slackware for the wireless problems. Back then there just wasn't very good drivers, like with ATI/AMD video cards. (Everyone has pleasant memories about NDSIWrapper right :)?) Now, they are supported much better that even with the default SLAX LiveCD/USB kernel/drivers I can pretty much be assured it'd work on most computers.
I'll give props to Ubuntu to making things many things working without touching a text editor though.
-
Support on Slackware for wireless is quite good nowadays.
-
Support on Slackware for wireless is quite good nowadays.
802.11n with WPA2 TKIP?
-
Support on Slackware for wireless is quite good nowadays.
802.11n with WPA2 TKIP?
I assume so.. those are all really standard.
But, why would you want to use TKIP? It's an ugly hack at best, and a security issue at worst. :)
-
Support on Slackware for wireless is quite good nowadays.
802.11n with WPA2 TKIP?
I assume so.. those are all really standard.
But, why would you want to use TKIP? It's an ugly hack at best, and a security issue at worst. :)
My work uses it to assign individual keys to each employee to expire at predetermined intervals.
-
My work uses PEAP tunneled through something else. Everyone just connects to the 'public' network which doesn't require a password, and then VPNs in to the corporate network.
-
Support on Slackware for wireless is quite good nowadays.
802.11n with WPA2 TKIP?
I assume so.. those are all really standard.
But, why would you want to use TKIP? It's an ugly hack at best, and a security issue at worst. :)
My work uses it to assign individual keys to each employee to expire at predetermined intervals.
It took me thirteen minutes, from not knowing how to use wpa_supplicant for WPA (ironic!), to having my WPA2 TKIP hidden SSID wireless connection installed. And yes, I know hiding a SSID is a bad idea.
-
It took me thirteen minutes, from not knowing how to use wpa_supplicant for WPA (ironic!), to having my WPA2 TKIP hidden SSID wireless connection installed. And yes, I know hiding a SSID is a bad idea.
To quote B-4, "Why?"
-
Support on Slackware for wireless is quite good nowadays.
802.11n with WPA2 TKIP?
I assume so.. those are all really standard.
But, why would you want to use TKIP? It's an ugly hack at best, and a security issue at worst. :)
My work uses it to assign individual keys to each employee to expire at predetermined intervals.
I don't know of the exact attacks or scenarios, but I know that TKIP is vulnerable to different attacks including, iirc, decryption and injection. You'd be better off using CCNP.
Which reminds me.. isn't TKIP the protocol for WPA and CCNA the protocol for WPA2? I wasn't aware you could use WPA2 with TKIP (though I'm definitely not a wireless guy, so I could very well be wrong)
-
I dunno. All I know is that our IT people set it up and that it's faster than our old wifi.
-
TKIP can be broken in like, 15 minutes now. I'm pretty sure AES is what they recommend now. TKIP was temporary so they could make a standard one, which I'm guessing is the method involving AES. At least, that's what I remember when reading up on a vulnerability for TKIP.