I have been trying to pair my windows mobile device with Mercedes Bluetooth unit. For some reason, the Mercedes Bluetooth unit could see the phone, but wasn't successful paring with it. I've been looking around internet for a while now trying to find a solution to the this issue, and have finally found a solution. This is just a combination of instructions from various  sources and I’ve put them together.

It's actually probably not the Bluetooth devices fault. Bluetooth devices identify themselves as a certain type of unit. For example, headsets as headsets, phones as phones. Interestingly, Windows mobile units identify themselves as PDA's not phones.  This need to be changed for the Bluetooth unit to recognize the phone. But this needs editing the registry of the Windows Mobile phone.

If you're not comfortable with editing the registry, don't do it. It can and will mess up your phone if done wrong. 

1. download and install CeReg editor (http://ceregeditor.mdsoft.pl/) on a Desktop PC. Its a simple registry editor for windows mobile.

2. Connect the windows mobile unit using USB and Open the registry using CeReg.

3. Edit the following value

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS]
"COD"=dword:52020C (hex)

4. Change the value to 1048852 (Decimal)

5. Reset the phone

6. If the device is already paired, delete the pairing, and start from scratch. This time it should work as the accessory is seeing the device as a phone, not a PDA.

these patches released today: http://www.cisco.com/en/US/products/products_security_advisory09186a0080b1490b.shtml

This affects Cisco Unified MeetingPlace versions 5, 6, and 7.

Microsoft has released Security Advisory 977981.  It details vulnerabilities in Internet Explorer 6 and 7 on various operating systems.  The advisory does not provide any patches or new versions at this point, but does provide several recommendations for mitigation.

Safari 4.0.4 was released yesterday for download, affecting both OS X and Windows versions.

Multiple security issues are addressed in this version, including remote code execution, process termination and disclosure of information issues.  Also one fix for a specific coss-site request forgery (CSRF)

http://support.apple.com/kb/HT3949

Apple iPhone owners in Australia have reported that their smart phones have been infected by a worm that has changed their wallpaper to an image of 1980s pop crooner Rick Astley.

The worm, which could have spread to other countries although there are no confirmed reports outside Australia, is capable of breaking into jail broken iPhones if their owners have not changed the default password after installing SSH. Once in place, the worm appears to attempt to find other iPhones on the mobile phone network that are similarly vulnerable, and installs itself again

On each installation, the worm - written by a hacker calling themselves "ikex" - changes the lock background wallpaper to an image of Rick Astley with the message:

ikee is never going to give you up

What's clear is that if you have jail broken your iPhone or iPod Touch, and installed SSH, then you must always change your root user password to something different than the default, "alpine". In fact, it would be a good idea if you didn't use a dictionary word at all.

The worm will not affect users who have not jail broken their iPhones or who have not installed SSH.

SophosLabs is analyzing the worm's code, which suggests that at least four variants have been written so far. One of the attributes of the latest variant (labeled the "D" version) is that it tries to hide its presence by using a file path suggestive of the Cydia application.

Presently it appears that the worm does nothing more malicious than spread and change the infected user's lock screen wallpaper. However, that doesn't mean that attacks like this can be considered harmless.