Installing CW SSH CLI on OpenVMS
From TDiWiki
1) Verify the version of Java you have installed:
$ java -version
That command should return something similar to:
java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition Fast VM (build 1.5.0-6, build J2SDK.v.1.5.0:08/04/2009-08:01, native threads, jit_150)
The important bit is the ' java version "1.5.0" ' --- that tells us we're using Java version 5 which, in turn, tells us which crypto extensions to install.
2) Download the unlimited strength Java crypto extension policy files from Oracle.
Currently, they're found in the 'Other Downloads' section (see image below).
Download them to your workstation.
3) Extract the contents of the JCE to a temporary directory on your workstation.
4) Transfer (IN BINARY) the two JAR files to a temporary location on your VMS system.
5) On the VMS system, repair the file attributes of each of the JAR's using these commands:
$ set file local_policy.jar /att=(rfm=stmlf,mrs=32767) $ set file US_export_policy.jar /att=(rfm=stmlf,mrs=32767)
6) Get the location of the JRE with the following command:
$ SHOW LOGICAL JAVA$JRE_HOME_VMS
The above command should return something similar to this:
"JAVA$JRE_HOME_VMS" = "DISK$PCDISK1:[JAVA$150.jre]" (LNM$PROCESS_TABLE)
7) Add the subdirectory [.lib.security] to the above translation (from YOUR system though) to define a (temporary) logical name as follows:
[example]
$ define JCE_DIR DISK$PCDISK1:[JAVA$150.jre.lib.security]
8) Move the JCE files into the new directory, but make sure and preserve the existing JAR's in that directory by the same name.
The process should look something like this:
$ rename JCE_DIR:local_policy.jar JCE_DIR:local_policy.jar-original $ rename JCE_DIR:US_export_policy.jar JCE_DIR:US_export_policy.jar-original $ copy local_policy.jar JCE_DIR:local_policy.jar $ copy US_export_policy.jar JCE_DIR:US_export_policy.jar $ set file JCE_DIR:local_policy.jar/prot=w:re/own=system $ set file JCE_DIR:US_export_policy.jar/prot=w:re/own=system
9) Download & install cwssh (NOTE: This MUST be on an ODS-5 volume)
a) create/dir [.cwssh] (must be on an ODS-5 volume)
b) set def [.cwssh]
c) unzip where:[ever.it.is]cwssh.zip
10) Test that cwssh AND the newly installed JCE are working correctly: (note that the first test will produce an error)
$ java -jar cwssh.jar -test | java.io.FileNotFoundException: cwssh.key | at java.io.FileInputStream.open(Native Method) | at java.io.FileInputStream.<init>(FileInputStream.java:106) | at java.io.FileInputStream.<init>(FileInputStream.java:66) | at org.tdi.jsshserv.SSHServer.loadPKeyFile(SSHServer.java:60) | at org.tdi.jsshserv.SSHServer.createOrLoadPKeyFile(SSHServer.java:83) | at com.tdi.cwssh.CwSshServ.testServer(CwSshServ.java:134) | at com.tdi.cwssh.CwSshServ.main(CwSshServ.java:72) | Failed : unable to create or load key file
Make sure your DCL parse style is set to extended:
$ SET PROCESS/PARSE=EXTEND
Change the key file name to lower case
$ RENAME cwssh.key cwssh.key
Rerun the test - this time it should indicate test passed:
$ java -jar cwssh.jar -test
Start the cwssh server as follows: (Example assuming that your ConsoleWorks server is on this host, port 5176, and that you want cwssh on port 5177)
$ java -jar cwssh.jar 5177 -cwhost localhost -cwport 5176 -nossl
11) Test access to cwssh from a non-vms host [we are working on having the vms host be able to access it]
example
Linux> ssh -p 5177 console_manager@vmsserver.yourenterprise.com
