openssl upgrade - U might b need it ;p
Well, about my problem in upgrading my remote server with the latest version of openssl, apache and other its need to avoid getting the error.... Just wanna tell u this, you might be need it, if not... just ignore it.... ;p Well, at the first time, before removing the available openssl, you might have to enable the TELNET CONNECTION first. It's better to completely remove the available openssl first, but remember to ENABLE THE TELNET CONNECTION first. After removing the old openssl, you can not make any other SSH connection to your remote machine. You have got to do this fast, do not let the TELNET CONNECTION enable for a long time period. Get the latest openssl in www.openssl.com, and follow the instruction. Dont be affraid of libcrypto.* proble. Just configured the openssl installation with shared (./configure --prefix=/YOUR_OPENSSL_DIR_TARGET --openssldir=/YOUR_OPENSSL_DIR_TARGET shared) That's the main idean that I would like to say, shared. It's automatically created the latest file of libcrypto.* and other its need. Simple, make the duplicate of the needed file and create a link from a defined .so as .so asked. Then, you can simply close the TELNET CONNECTION (using chkconfig --level 3 telnet off - Redhat) and re-enabling the ssh connection by typing /etc/rc.d/init.d/sshd restart) Good Luck...... ;p
On Wed, Oct 02, 2002 at 12:45:01PM +0700, Aramico wrote:
Just configured the openssl installation with shared (./configure --prefix=/YOUR_OPENSSL_DIR_TARGET --openssldir=/YOUR_OPENSSL_DIR_TARGET shared) That's the main idean that I would like to say, shared.
It's automatically created the latest file of libcrypto.* and other its need. Simple, make the duplicate of the needed file and create a link from a defined .so as .so asked. Then, you can simply close the TELNET CONNECTION (using chkconfig --level 3 telnet off - Redhat) and re-enabling the ssh connection by typing /etc/rc.d/init.d/sshd restart)
Out of curiousity, why are you manually upgrading via tarballs when redhat has shipped patched openssl rpms? Just do an rpm -Uvh on them, and you can do it over an ssh connection just fine. -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 18 Full-time WPI Network Engineer, Part time Linux/Perl guy | "The inside of my head was exploding with fireworks. Fortunately, my last thought turned out the lights when it left." --- Calvin
or if you're running Gentoo, `emerge -u openssl` and forget about it ;D -mike On Wed, 2 Oct 2002, Frank Sweetser wrote:
On Wed, Oct 02, 2002 at 12:45:01PM +0700, Aramico wrote:
Just configured the openssl installation with shared (./configure --prefix=/YOUR_OPENSSL_DIR_TARGET --openssldir=/YOUR_OPENSSL_DIR_TARGET shared) That's the main idean that I would like to say, shared.
It's automatically created the latest file of libcrypto.* and other its need. Simple, make the duplicate of the needed file and create a link from a defined .so as .so asked. Then, you can simply close the TELNET CONNECTION (using chkconfig --level 3 telnet off - Redhat) and re-enabling the ssh connection by typing /etc/rc.d/init.d/sshd restart)
Out of curiousity, why are you manually upgrading via tarballs when redhat has shipped patched openssl rpms? Just do an rpm -Uvh on them, and you can do it over an ssh connection just fine.
-- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 18 Full-time WPI Network Engineer, Part time Linux/Perl guy | "The inside of my head was exploding with fireworks. Fortunately, my last thought turned out the lights when it left." --- Calvin
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (3)
-
Aramico -
Frank Sweetser -
Michael Patrick Frysinger