Is there a reason why you cannot build it from a controlled build environment and record the hash of the final .so? It seems that it would be pretty non-trivial if not impossible to pull a .o file from a .so in the exact same format that it went in, such that you could check the hash. Being able to check if a .c file is in the same state in the .so afterwards seems pretty much impossible given all the things that would change in the code with compiling and linking in between the .c state and the final .so state. On Mon, Mar 14, 2016 at 5:30 PM, Satya Das <satya at attivonetworks.com> wrote: > Hello, > > > > I have a simple problem I am trying to solve. I have built a fips capable > openssl shared object (.so). I also have the sha1 hash of the > fipscanister.o in a file called fipscanister.o.sha1. I also have the sha1 > hash of fips_premain.c in a file called fips_premain.c.sha1. In order to > make sure the build is good, I want to make sure that the .so was indeed > built with these versions of fipscanister.o and fips_premain. > > > > Is there a way to do this ? I am on centos 6.6 x86_64 and linking to > object module 2.0.11 from openssl 1.0.1e with patches. > > > > Thanks > > -- > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160314/5665c793/attachment.html>
