Patched MS Bluetooth Flaw Exposes Even Disconnected PCs
An anonymous reader writes "Among the 22 security holes Microsoft issued updates to fix yesterday is a critical kernel-level Bluetooth flaw that could let nearby attackers break into vulnerable systems even when the targeted computer is not connected to a network. An attacker could use the bug to gain access to any unpatched, Bluetooth-enabled Windows Vista or Win7 computer within 100 meters (or much further with specialized tools), all before the target system even gets an alert that another computer is requesting a Bluetooth connection."
"even when the targeted computer is not connected to a network."
"target would merely need to have Bluetooth turned on."
Meh, not as scary as I thought. You shouldn't be running around with bluetooth on anyway. Also, if you're using a 'hidden' connection there's no real way for an attacker to find you is there?
So basically computers at risk are those who always leave bluetooth on and shown to everyone. Which unless you're trying to connect to a new device should be NEVER.
Because 7 has features XP doesn't. Like support for the TRIM command for SSDs. Like an audio mixer that lets you set different volumes for each application, instead of each hardware output, which is floating point from the ground up. Like desktop rendering that is accelerated by your GPU. Like UAC. Like Aero Snap. Etc. It's not like Windows 7 is just a facelift on Windows XP, There are differences that aren't even hard to find.
Sooooo you expect highly secure devices in military installations, cash machines, banks etc are blue tooth enabled and you think MS is the one that doesn't have a clue?
Most of the public could do all that on their phone. Most of the public don't particularly "need" computers. Seriously, when the hell did "computers should only do exactly what people need them to do the day they buy them and anything else is a waste" become such a fashionable sentiment?
I haven't seen an application that doesn't get its own fader no matter what audio model it uses
An app can request/get exclusive access to the audio card, and bypass everything including the volume control. But that's only used by audio authoring software.
My favorite Win7 audio feature in any case is the ability to redirect live audio. I can now watch a movie and while it's playing switch the audio to/from my headphones painlessly (earlier I would have to restart the movie, and sometimes the whole app). I don't have headphone jacks I can easily reach, so it saves me a bit of trouble.
Merely having bluetooth-capable hardware and software should not expose you to anything. Computers should be secure by default, out-the-box, and it is not unreasonable to expect this.
I am trolling
Depends on what kind of audio card you have. Some support two audio streams, some do not. If you have the same Realtech chip I got then just set it to use separate audio streams for front/back panel, alternately you can also simply have two audio cards.
Then just right click the little speaker icon, select playback devices and change default. Any app that plays to the default playback device will then change to play to the new target.
If you, like me, have more than one audio card there can be a lot of outputs. Outputs you never use can be disabled/hidden by right clicking on them, and audio outputs you use can be renamed. So I got one called headphones, and one called Speakers. Changing between them takes me five mouse clicks.
I am assuming you mean Floating point SOUND MIXING of sound channels.
Here are a few pages that talk about the issues in mixing two audio streams, and lead to the benefits of floating point mixing.
http://stackoverflow.com/questions/376036/algorithm-to-mix-sound
http://www.vttoth.com/digimix.htm
Have a nice day!
At which point you set your application to use WASAPI in exclusive mode, and get all the low latency you want. A hell of a lot lower than WDM offers in Windows XP. Or you use ASIO. Or whatever. I mean, you probably don't need low latency from EVERY application, so it's not exactly borked is it? After all, Microsoft worked with companies like Cakewalk when they were designing their new audio stack back in the Vista days. Which is why there IS low latency support in the stack, and why there are less audio crackles when other stuff is happening in Vista/7 when compared to XP. Besides, there is so much FUD about latency in the audio path. I have a home studio, I deal with a need for low latency all the time... and frankly starting with Windows Vista this became a heck of a lot less painful to get working than it ever was with XP. And for my non-studio stuff, frankly it's not like video and audio are noticeably out of sync on my Win7 system, and that's with onboard audio, and a CRT monitor with pretty much no latency. So there are solutions when it's important, and features when it's not.
Whereas with Windows XP you get none of those things. And frankly, Pulseaudio tries to be Windows 7/Vista audio. Pulseaudio came out in what, 2008/2009? Whereas Vista was available in 2006, and betas were available before then...