Zero Bytes

 

Here are the some of the Best book collections,  High Performance Habits: How Extraordinary People Become That Way , Hardcover  Getting Things Done : The Art of Stress-Free Productivity by David Allen 52 Red Pills You Can't Order Change The 7 Habits of Highly Effective People Rich Dad Poor Dad  The 4 Hour Work Week High Performance Habits Read People Like a Book Getting Things Done The 80/20 Principle Holy Cow  

First of all the following value has to be unique to each install of Sterling Integrator. If you accidentally used shared location for cluster installation your second node installation not going to work. So here is how we can fix this. 1. Go to user home and move $USERHOME$/IBM/IBMSHARED to new local location. 2. Update the reference in  /home/user/var/ibm/InstallationManager/installRegistry.xml           That's it. This will fix First node IBMSHARED location and we can proceed with second node installation. How to verify? 1. Go to InstallManager tools     cd /InstallationManager/IM_Linux/tools  2. ./imcl listInstalledPackages -verbose Validate the output something like below, [Shared] Shared resources directory: /opt/ibm/IBMIMShared [Package group] Name: Sterling Integrator Installation directory: /opt/ibm/sfg Translations: Architecture: 64-bit [Package] Name: IBM Sterling B2B Integrator (com.ibm.sterling.in...

Some of the IBM Sterling B2B Integrator(SI) customers wants to avoid SSH handshake using CBC Cipher as it is vulnerable. The link  http://www.kb.cert.org/vuls/id/958563  explains that CBC Ciphers are security vulnerable and the solution is to use CTR Cipher instead of CBC Cipher. However, in SI versions 5020602 and 5020603, maverick (the third party api used for SSH/SFTP) version used is 1.4.60 which mandates that CBC Cipher should be present in Client side. Hence, disabling the CBC support using the security property supportCBCCiphers=false will result in SFTP communication failure with key based authentication. To enforce the use of CTR Cipher in SI, we have introduced two new properties : SSHServerCipherList, SSHClientCipherList a) security.SSHServerCipherList is the property to restrict the list of server side ciphers. In the SFTP Server adapter, "Preferred Cipher" drop down will pick the values specified in this property list. b) security.SSHClientCipherList is...

Generate PGP Keys gpg --gen-key Enter Key details, Email, Expiration etc., Export Secret Key gpg --export-secret-key -a MY_PGP_KEY >> /tmp/MY_PGP_KEY.key Export Public Key gpg --export -a MY_PGP_KEY >> /tmp/MY_PGP_KEY.asc Import Secret Key gpg --import /tmp/MY_PGP_KEY.key Import Public Key gpg --import /tmp/MY_PGP_KEY.asc Update Key Trust Trust after importing the Key gpg --edit-key $trust $5 $save

Add the following lines of code to the file called config under .ssh folder, If you don't find a file with the name config create one, .ssh\config Host * HostkeyAlgorithms +ssh-dss PubkeyAcceptedKeyTypes +ssh-dss Note: When server respond with ssh-dss some ssh clients don't accept the connection. If you get ssh returns “Bad owner or permissions on ~/.ssh/config” then please change the permissions as follows, chmod 600 ~/.ssh/config

openssl req -newkey rsa:2048 -sha512 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem openssl x509 -text -noout -in certificate.pem openssl pkcs12 -inkey key.pem -in certificate.pem -export -out certificate.p12 openssl pkcs12 -in certificate.p12 -noout -info openssl pkcs12 -inkey key.pem -in certificate.pem -export -out certificate.p12 openssl pkcs12 -in certificate.p12 -noout -info openssl pkcs12 -in /tmp/certificate.p12 -nokeys -out sirish_test.cer