On Thu, Aug 31, 2006 at 12:11:46 +0400, "Victor B. Wagner" <[EMAIL PROTECTED]> wrote: > > It contains !MD5 element, because MD5 digest algorithm was broken about > year ago, and PostgreSQL expected to work with versions of OpenSSL which > still consider it strong.
MD5 wasn't completely broken and I believe it is still considered safe for the way it is used in SSL. It looks like SHA-1 is pretty much in the same boat now. (See http://www.heise-security.co.uk/news/77244) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
