Comment Re:Deal breaker (Score 1) 638
One of the best things about the old mac minis is they had optical digital audio output in the 3.5mm jack as well - if they have kept that then you should be able to get proper surround sound....
Crispin
VirtualBox 2.1 Supports 64-Bit VM In 32-Bit Host 374
Stephen Birch writes "Following closely behind the mid-November 2.06 release of VirtualBox, Sun Microsystems has released version 2.1. This has a number of new features, but one of the most interesting is the ability to run a 64-bit VM inside a 32-bit host. Another useful feature is integrated host-based networking; no more fiddling around with network bridges. Sun is really giving VMWare a run for their money."
Vista to Allow "One Significant" Hardware Upgrade 641
fiorenza writes "Ars Technica spoke with Microsoft concerning the controversial changes in Windows Vista's licensing, and they have learned that Vista will permit one 'significant' hardware change before requiring users to either appeal to Microsoft support or purchase another license. Automatic re-activation online will fail after one use. Microsoft is using a new algorithm to monitor hardware changes and enforce licensing compliance, and the company says that it is more forgiving now than it was with Windows XP."
Comment Re:why remove it? (Score 1) 131
You don't end up using the worst SSL version, a well written server will use the best common SSL version.
The SSL handshake is a multi-step process, it is only the initial 'ClientHello' record that is in the SSLv2 format. Inside that record is information telling the server the maximum SSL version the client supports. The SSL server will then respond with an SSLv3 (or TLS) 'ServerHello' record, and from that point on, the server and client will complete the SSLv3 handshake.
There isn't any security problems leading with an SSLv2 ClientHello message, the only problems come from when the server only support SSLv2 and so an SSLv2 handshake has to be completed.
If you don't believe me with any of this, download ethereal or ssldump and see what SSL versions each of the encoded SSL records is returned as.
The SSL handshake is a multi-step process, it is only the initial 'ClientHello' record that is in the SSLv2 format. Inside that record is information telling the server the maximum SSL version the client supports. The SSL server will then respond with an SSLv3 (or TLS) 'ServerHello' record, and from that point on, the server and client will complete the SSLv3 handshake.
There isn't any security problems leading with an SSLv2 ClientHello message, the only problems come from when the server only support SSLv2 and so an SSLv2 handshake has to be completed.
If you don't believe me with any of this, download ethereal or ssldump and see what SSL versions each of the encoded SSL records is returned as.
