No.  What I am saying is that once I created an RPM from the 1.0.0j source 
package from openssl.org (which includes a .spec file) it doesn't match the 
list of files that are currently installed on the FC16 system.   My concern 
here is that the list of files is different and installed in different places.  
This may be something special/peculiar that someone did on FC16.  My ultimate 
goal is to update the currently installed openssl (1.0.0j) on FC16 to 1.0.0m 
without breaking anything that depends on it.  I will try simply removing 
openssl-1.0.0j-1.i686.rpm that is installed and install the 
openssl-1.0.0m-1.i686.rpm package version.  Following is a detail of the 
differences that I am describing:

Currently installed file list from FC16 openssl-1.0.0j-1.i686.rpm is the 
following:

/etc/pki/CA
/etc/pki/CA/certs
/etc/pki/CA/crl
/etc/pki/CA/newcerts
/etc/pki/CA/private
/etc/pki/tls
/etc/pki/tls/certs
/etc/pki/tls/certs/Makefile
/etc/pki/tls/certs/make-dummy-cert
/etc/pki/tls/misc
/etc/pki/tls/misc/CA
/etc/pki/tls/misc/c_hash
/etc/pki/tls/misc/c_info
/etc/pki/tls/misc/c_issuer
/etc/pki/tls/misc/c_name
/etc/pki/tls/openssl.cnf
/etc/pki/tls/private
/lib/.libcrypto.so.1.0.0j.hmac
/lib/.libcrypto.so.10.hmac
/lib/libcrypto.so.1.0.0j
/lib/libcrypto.so.10
/usr/bin/openssl
/usr/lib/.libssl.so.1.0.0j.hmac
/usr/lib/.libssl.so.10.hmac
/usr/lib/libssl.so.1.0.0j
/usr/lib/libssl.so.10
/usr/lib/openssl
/usr/lib/openssl/engines
/usr/lib/openssl/engines/lib4758cca.so
/usr/lib/openssl/engines/libaep.so
/usr/lib/openssl/engines/libatalla.so
/usr/lib/openssl/engines/libcapi.so
/usr/lib/openssl/engines/libchil.so
/usr/lib/openssl/engines/libcswift.so
/usr/lib/openssl/engines/libgmp.so
/usr/lib/openssl/engines/libnuron.so
/usr/lib/openssl/engines/libpadlock.so
/usr/lib/openssl/engines/libsureware.so
/usr/lib/openssl/engines/libubsec.so
/usr/share/doc/openssl-1.0.0j
/usr/share/doc/openssl-1.0.0j/CHANGES
/usr/share/doc/openssl-1.0.0j/FAQ
/usr/share/doc/openssl-1.0.0j/INSTALL
/usr/share/doc/openssl-1.0.0j/LICENSE
/usr/share/doc/openssl-1.0.0j/NEWS
/usr/share/doc/openssl-1.0.0j/README
/usr/share/doc/openssl-1.0.0j/README.FIPS
/usr/share/doc/openssl-1.0.0j/c-indentation.el
/usr/share/doc/openssl-1.0.0j/openssl.txt
/usr/share/doc/openssl-1.0.0j/openssl_button.gif
/usr/share/doc/openssl-1.0.0j/openssl_button.html
/usr/share/doc/openssl-1.0.0j/ssleay.txt
/usr/share/man/man1/asn1parse.1ssl.gz
. . . <removed list of man pages to make list manageable for this email>
/usr/share/man/man7/des_modes.7ssl.gz

File list in newly built openssl-1.0.0j-1.i686.rpm  from source package (FC16 
openssl-1.0.0j.tar.gz) off the openssl.org site.  I used the 
openssl-1.0.0j.spec file provided in the tar file.  The 
openssl-1.0.0m-1.i686.rpm  I build has almost identical file list.

/usr/bin/c_rehash
/usr/bin/openssl
/usr/bin/ssleay
/usr/lib/libcrypto.so
/usr/lib/libcrypto.so.1.0.0
/usr/lib/libssl.so
/usr/lib/libssl.so.1.0.0
/usr/man/man1/CA.pl.1ssl.gz
. . . <removed list of man pages to make list manageable for this email>
/usr/man/man7/des_modes.7ssl.gz
/usr/share/doc/openssl-1.0.0j
/usr/share/doc/openssl-1.0.0j/CHANGES
/usr/share/doc/openssl-1.0.0j/CHANGES.SSLeay
/usr/share/doc/openssl-1.0.0j/LICENSE
/usr/share/doc/openssl-1.0.0j/NEWS
/usr/share/doc/openssl-1.0.0j/README
/var/ssl/certs
/var/ssl/misc
/var/ssl/misc/CA.pl
/var/ssl/misc/CA.sh
/var/ssl/misc/c_hash
/var/ssl/misc/c_info
/var/ssl/misc/c_issuer
/var/ssl/misc/c_name
/var/ssl/misc/tsget
/var/ssl/openssl.cnf
/var/ssl/private







Reply via email to