Comment 44 for bug 969343

I think this bug is fixed. At least in Ubuntu 12.04 -- perhaps from the precise-proposed update repository.

I had downgraded openssl and libssl to fix this issue--and it did--but it left me with a heap of issues such as tons of broken packages and thus being unable to install any updates or do any sort of activity with apt.

Here is how I un-did the downgrade and fixed all the issues:
sudo dpkg -r --force-depends "openssl"
sudo dpkg -r --force-depends "libssl1.0.0"
sudo dpkg --configure -a
sudo apt-get install -f

Now, restart. Then run update manager. Then restart again. Now, connecting to your wifi network shouldn't be an issue. I suspect the update I got was from the precise-proposed updates repository. It might be an update of wpasupplicant or libssl or openssl--I don't know. Synaptics Package Manager says I have package "libssl1.0.0" whose installed version is "1.0.1-4ubuntu5.2" which is the same as the latest version. And I have package "openssl" whose installed version is "1.0.1-4ubuntu5.2" which is also the latest version. And wpasupplicant -- of which I have installed version 0.7.3-6ubuntu2, the latest.

Remember, all this was done with the precise-proposed update repository selected.

One thing I still am confused about is why it says I have a package "libssl1.0.0" with version "1.0.1-4ubuntu5.2"....?!?!?