|
Message-ID: <4D26770D.7020702@quelrod.net> Date: Thu, 06 Jan 2011 20:14:37 -0600 From: James Nobis <quel@...lrod.net> To: john-users@...ts.openwall.com Subject: Re: hmailserver patch has errors, error when compiling in Linux x86 64-bit and 32-bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Solar, > My understanding is that SHA-256 is only available starting with > OpenSSL 0.9.8, whereas the jumbo patches require 0.9.7+ so far (not > necessarily 0.9.8+). So if we merge the hmailserver support patch, we > make the jumbo patch require 0.9.8+, which is a bit of a problem > (although it's becoming more acceptable over time). Maybe we should > include a SHA-256 implementation into the patch itself for now. You are entirely correct regarding 0.9.8+ for SHA-256. It seems it is a problem for Owl but 0.9.7 should really get retired. In general one can always write optimized code that outperforms generic OpenSSL installations so as I noted initially there is a need for optimization. > Another comment I had is that maybe we need "generic salted SHA-256" > support, similar to what I did for SHA-1 and MD4 recently, instead of > the specialized hmailserver support patch. That is also a great idea as hmailserver wasn't even something I had heard of before I wrote the patch. Is this an item you have the time and interest to do? If someone can point me to a license acceptable SHA-256 implementation or someone can add one that would be greatly appreciated. I want to support the patch I wrote as I wrote it for a friend but posted it because I expect it may be of use to someone else as well. However, my free time is quite limited and I wrote this as a short break from work on my project. I welcome any updates to the patch that make it acceptable for the jumbo patch as well as feedback on what items I will have to address myself. James -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCgAGBQJNJncNAAoJEGUWgJyjXssu9hYP/iXeCqu7u5K1S5aLrlXzrSXS Jq7R0zH4GMP2YmObAavOhW96rGN3FBus50Lpcgjad/Mk1f2bDnBCxjYFngsgdRcD cDhWr1scJhcV18s9khyS3eYQRH5lYoAPZxKzrKRLqYI5V4itrZ52/WxBPAdFZ7Zb fDMUYBMlxTY9cayjqc+dUlOiOSYKP7OIr/c5mYbHTAbwvtQKlFB6BagaWjdc7865 N7VMSfQwN4rL/euf406eH+YjWveUFDx+A7Hhpjna7jMgTm33g7iOBUfmwkuCXOD2 Xd943+F8wd4D/yG0cu/tM5/3KHZSmGxB+GaYh+NOBvLcKMQ3+Ysl4n4dKm6ePCvC ZRot5Z/EDUqXGDodYrlARtXVLjkeRTSuvT/1GsVvZGDbBaobaGahr67Ct2vqqK3z sIc0tIPBaquEngIvfRgHgelKCnfqBY/4hLBi5JRY1hoIErPjb7Tv+qCBkVg6liBH 5wf/L21zM4uYGTyEADZwa+zQgxcGWz6obcElMLjTLmWabu4eCaAaEAKQNa6Jj+rJ 4OxqS8G1zq7xpHaGBoPa9F8tFfRd/1SxbrCiMrg5LHUhiedkm6xJErSN8AZwsN9b +PuXxTQB1MlnWFLG8RBZtK1XkfzfyKlRDwT9G1jtpByK3u9yNe2DU42asVHNc8Gk 66ET0vs8eVr2cwa9/7OS =HhV5 -----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.