zekrahminator
McLovin
- Joined
- Jan 29, 2006
- Messages
- 9,066 (1.31/day)
- Location
- My house.
Processor | AMD Athlon 64 X2 4800+ Brisbane @ 2.8GHz (224x12.5, 1.425V) |
---|---|
Motherboard | Gigabyte sumthin-or-another, it's got an nForce 430 |
Cooling | Dual 120mm case fans front/rear, Arctic Cooling Freezer 64 Pro, Zalman VF-900 on GPU |
Memory | 2GB G.Skill DDR2 800 |
Video Card(s) | Sapphire X850XT @ 580/600 |
Storage | WD 160 GB SATA hard drive. |
Display(s) | Hanns G 19" widescreen, 5ms response time, 1440x900 |
Case | Thermaltake Soprano (black with side window). |
Audio Device(s) | Soundblaster Live! 24 bit (paired with X-530 speakers). |
Power Supply | ThermalTake 430W TR2 |
Software | XP Home SP2, can't wait for Vista SP1. |
When open source software makers made what would eventually become the more current versions of Linux, Unix, and Mac OS X, they undertook a very important task: ensuring that whenever a password was generated to keep confidential data secret, that it would actually be secure. However, they apparently made a rudimentary programming error, and it went out into the world of open source software unnoticed. A couple years down the road, some hackers pointed out with glee that the OpenSSL key generator is basically useless as a security measure (the actual flaw is explained much more thoroughly in the source link). Because OpenSSL is used in far more systems than a couple home servers, we have a serious problem on our hands. Even though the original authors have issued a patch, there's no guarantee that it will get around fast enough to prevent some serious damage.
View at TechPowerUp Main Site
View at TechPowerUp Main Site