Comment 2 for bug 270812

wouldn't it be reasonable to resolve it in w3c-libwww package too?
as i briefly recall libmd5.so.0 dep being pulled in in some other package

and the libmd5.so.0 was not really same implementation as libcrypto.so.0 from openssl for example provides but package expected (while MD5Init and MD5Update symbols did match).

$ rpm -q w3c-libwww --provides
libmd5.so.0
libpics.so.0
libwwwapp.so.0
libwwwcache.so.0
libwwwcore.so.0
libwwwdir.so.0
libwwwfile.so.0
libwwwftp.so.0
libwwwgopher.so.0
libwwwhtml.so.0
libwwwhttp.so.0
libwwwinit.so.0
libwwwmime.so.0
libwwwmux.so.0
libwwwnews.so.0
libwwwssl.so.0
libwwwstream.so.0
libwwwtelnet.so.0
libwwwtrans.so.0
libwwwutils.so.0
libwwwxml.so.0
libwwwzip.so.0

so there libwwwmd5.so.0 would seem sane choice...