Hi Kern, > I do not see a problem taking the newer RFC 6234 code. However here > are a few points: > > 1. Is the source code available in files (a .h and a .c)? That would > simplify getting the new source. > > 2. As I mentioned previously, the SHA1 code has been in Bacula for a > long time (apparently since 2002) and is well tested and proven > portable. Someone (or multiple people) would need to do tests on a > number of platforms and architectures to make sure the new algorithm > is the same as the old one in all cases. > > I am willing to do a good part of the work -- get the source code, > modify the calling sequences to be the same as Bacula's if they are > not already, make some test cases. However, I no longer have the > means to test it on many platforms so I would need help there. Also, > I am a bit overloaded for the next month or two, so this is not > something that could happen immediately unless someone else does all > the work and testing.
from my side this is nothing that's urgent, and since I've stirred this up again, I can prepare a patch. I already had extracted the code from the RFCs to compare them anyway. Please work on more important things until I come back on this :-) Regards, Carsten ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
