This bug goes away when I downgrade libssl1.0.0 to 1.0.0h-1. It may be that this bug should belongs to that package instead. -- Michael Welsh Duggan (mwd@cert.org)