use md5sum-string instead of md5sum-sequence to adjust to upstream changes

https://github.com/marijnh/Postmodern/issues/27 has a good description
of the changes in the MD5 library:

The latest "release" of md5 (dated 20121125 according to quicklisp) will silently cast strings to byte arrays, yielding incorrect checksums and causing cl-postgres to fail to authenticate.

diff --git a/db-postgresql-socket/postgresql-socket-api.lisp b/db-postgresql-socket/postgresql-socket-api.lisp
index 07b979f8042bc9cf8d3fb676dd685ec12ebb1631..879e5bb2a0ede5a358f45e88dad9205676790c87 100644 (file)
--- a/db-postgresql-socket/postgresql-socket-api.lisp
+++ b/db-postgresql-socket/postgresql-socket-api.lisp
@@ -490,7 +490,7 @@ troubles."
 (defun encrypt-md5 (plaintext salt)
   (string-downcase
    (format nil "~{~2,'0X~}"
-           (coerce (md5sum-sequence (concatenate 'string plaintext salt)) 'list))))
+           (coerce (md5sum-string (concatenate 'string plaintext salt)) 'list))))
 
 (defun reopen-postgresql-connection (connection)
   "Reopen the given PostgreSQL connection.  Closes any existing