For the technical aspects there are some links below , ,  being  the best one. There is some weak analysis about impact  . The best analysis consist of getting a copy of users.tar.gz and run some greps and wc.
Adobe reacted fine, there is no leak on the password recovery process and there is even a security alert on the landing page, a hard hit to marketing.
The fact that the users reuse passwords among accounts it's not adobe fault. But encrypting instead of hashing is another thing. This failure opens the door to statistical analysis and the use of the hint field to recover a pretty nice top 100  and somebody says the recovered password list climbs to six millons.
When it started, they say 3 millons, then 38 millons active accounts. The fact is that the list comprises 130 millons of mail/encrypted password/hint.
An attacker can gain some insight in the victim's way of choosing passwords in the best case and using the very same password if the victim reuses it in the worst case.
The best thing to do now as an user is to stop repeating passwords, change them if you are repeating. There is no gain in using a check system like , as we already know that all the database is stolen.
If someone decrypts the password by brute force or because they got it with the rest of the leak, it will be the worst attack, ever.
 spanish version http://seguridad-agile.blogspot.com.ar/2013/11/leak-adobe.html