| From: | "M(dot) Bastin" <marcbastin(at)mindspring(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | MD5 different standards--or not? |
| Date: | 2003-05-29 17:42:17 |
| Message-ID: | a0521060abafbf59211c9@[213.224.115.34] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
I'm even more puzzled now. Following Joe's link I also landed on the
rfc to which I was refering, which made me take a closer look at it.
That rfc starts by stating the outcome is 16 bytes, and then ends
with those results you can test against which are all 32 bytes. All
in the same document!
I tried finding in the C code where the jump to 32 bytes is made. It
could be something silly like appending a 16 bytes MD5 based on the
first 16 bytes MD5 of the original string. But as I wrote before,
I'm not good at reading C and couldn't find a single clue.
I need a C master-brain here! ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincent Hikida | 2003-05-29 20:32:09 | Re: + operator with a possible NULL operand |
| Previous Message | Joe Conway | 2003-05-29 17:30:53 | Re: MD5 different standards? |