Sponsored Content
Operating Systems HP-UX Issue Patching Secure Shell... Post 302943731 by RavinderSingh13 on Tuesday 12th of May 2015 11:15:43 AM
Old 05-12-2015
Hello chambo,

Welcome to forum, please use code tags as per forum rules for codes/commands/errors etc. http://www11.itrc.hp.com/service/cki/docDisplay.do​?docLocale=en&docId=emr_na-c01743625-2
--
Starting with HP-UX Secure Shell A.05.10 and HP-UX 11.31, OpenSSL is a shared library and is not archived. Secure Shell on HP-UX 11.31 now depends on the System's OpenSSL Version installed, not the one it was linked with.
--
If I look at "new in this release" info
https://h20392.www2.hp.com/portal/swdepot/displayP​roductInfo.do?productNumber=T1471AA
OpenSSH 5.2 is now linked with OpenSSL A.00.09.8k instead of A.00.09.7m

What version of OpenSSL are you running?
Code:
ssh -V

EDIT: Also could you please post result for following command too.
Code:
openssl version


Thanks,
R. Singh

Last edited by RavinderSingh13; 05-13-2015 at 01:34 AM.. Reason: Changed ICODE tags for CODE tags. by rbatte1 + added a command to ask user version of openssl by R. Singh
This User Gave Thanks to RavinderSingh13 For This Post:
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

f-secure sftp in shell script

Hi, I am trying to use sftp in a ksh - Shell script, but not even a simple script like this returns not output: sftp username@remotehost <<END ls END If I do something like this: sftp username@remotehost <<END | tee logfile ls END I get this error message: Warning: tcgetattr... (1 Reply)
Discussion started by: friand
1 Replies

2. Shell Programming and Scripting

Secure coding standards for Shell Programming

Hi, Can anyone point me to Secure coding standards for shell programming guides, links etc etc... Thanks and regards, Vamsi K Surampalli. (2 Replies)
Discussion started by: vamsisurampalli
2 Replies

3. Solaris

ssh login issue after patching

Hi Everybody, Recently i applied patch cluster dated (2009.11.03) for solaris 10 sparc machine(Generic_138888-06) I successfully applied and rebooted the machine , no errors received. But after patching it was not allowing me to login through ssh while telnet was working fine.Logs showed me ... (11 Replies)
Discussion started by: laxmikant
11 Replies

4. AIX

AIX and Secure Shell

I just installed 5.3 TL0 on a B50 server. I need to get ssh installed. I tried the links at http://sourceforge.net/projects/openssh-aix] I downloaded openssh_5.2p1_aix53.tar and openssh-4.5_srcpatch.tar. The installation failed. The notes say that this was compiled for TL 8, and mine is... (3 Replies)
Discussion started by: Geekasaurus
3 Replies

5. Solaris

Issue patching, can't find resolution

I'm trying to install the latest patch cluster on a server running 05/08 (it's a Sunfire v240). When installing, the patch cluster dies at patch 138195-04. Looking at the failure log, here is what it says: baspeans01:/home/10_Recommended# more /var/tmp/138195-04.log.16544 This appears to be... (2 Replies)
Discussion started by: msarro
2 Replies

6. UNIX for Dummies Questions & Answers

GUI via secure shell

Hi i am connected to remote system using putty over ssh-1 version. i can see the command line and able to perform the operations through it. is it possible to have a GUI interface of my login rather than terminal access? do i need to use any client other than putty ? any help is much... (5 Replies)
Discussion started by: rakeshkumar
5 Replies

7. Solaris

Solaris patching issue with Live Upgrade

I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade. Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less... (7 Replies)
Discussion started by: solaris_1977
7 Replies

8. Solaris

Sun Fire V245 patching issue

Hi All, I have an server Sun Fire V245 for which we had been trying to patch. We get a message that the patch has been applied successfully but while trying to reboot after activating the new lu, the server is not booting up. Had reinstalled lustarter pack, required patches during the patching... (5 Replies)
Discussion started by: Rockyc3400
5 Replies

9. UNIX for Beginners Questions & Answers

Red Hat: Error connecting using secure shell

Hi All, I am getting below error when I try to connect with ssh. Not sure why the error is on.I am able to connect from a different login from the same server (local: rhe/home/s3>) ssh acces1@91.1.12.102 Connection closed by 91.1.12.102 (local: rhe/home/s3>) ssh redhlinx102 Connection... (7 Replies)
Discussion started by: arunkumar_mca
7 Replies
SHAPE_PATCH(1)						      General Commands Manual						    SHAPE_PATCH(1)

NAME
shape_patch - shapeTools RMS generate patch file SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>] DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape patch from the top node of the central source repository creates a patch file for the whole system. The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH- FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output. Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure will leave an equally named patch file for each visited subsystem. The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1). INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit. SEE ALSO
shape_releas(1), vdiff(1), patch(1) FILES
<name1>+2+<name2>.pat 9.9.119 SHAPE_PATCH(1)
All times are GMT -4. The time now is 10:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy