星期五, 1月 19, 2018
星期二, 10月 03, 2017
IHS and WAS fix for CVE-2016-2183
For IHS:
IBM HTTP Server and Sweet32: Birthday attack (CVE-2016-2183)
For WAS:
Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affects WebSphere Application Server January 2017 CPU
星期二, 9月 05, 2017
How can I test if my server supports a specific SSL protocol?
1. Linux command line tool:
openssl can help you test which SSL protocols your server is configured to use.
openssl
If a protocol is enabled, the openssl s_client command will wait for input (or Control-D).
If the protocol is disabled, openssl will report an exception similiar to the one reproduced below:
21112:error:1407F0E5:SSL routines:SSL2_WRITE:ssl handshake failure:s2_pkt.c:428:
Openssl examples:
openssl s_client -connect ihshostname:443 -ssl2
openssl s_client -connect ihshostname:443 -ssl3
openssl s_client -connect ihshostname:443 -tls1
#openssl s_client -connect www.google.com:443 -ssl3
CONNECTED(00000003)
23569:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number:s3_pkt.c:293:
#openssl s_client -connect localhost:1414 -cipher ECDHE-RSA-DES-CBC3-SHA
#openssl s_client -connect localhost:1414 -showcerts
#openssl ciphers ==> 列出openssl可用的cipher名稱, 以:分隔
**** perl one liner 可用在此處, 把原本用:分隔不易查看的資訊, 改以每筆一行的方式列出
#openssl ciphers|perl -ne 's/:/\n/g;print'
2. online website check tool
https://www.ssllabs.com/ssltest/
3. standalone test tool (TestSSLServer)
https://www.bolet.org/TestSSLServer/
4. IHS v8 or above version command:
Windows:
httpd -t -D DUMP_SSL_CONFIG
Linux:
apachectl -t -D DUMP_SSL_CONFIG
http://publib.boulder.ibm.com/httpserv/ihsdiag/ssl_questions.html#sslprotsupptest
5. use nmap to help to verify which cipherspec is supported by SSL server
nmap --script ssl-enum-ciphers -p port_number ip_address
# nmap --script ssl-enum-ciphers -p 1477 localhost
Starting Nmap 7.70 ( https://nmap.org ) at 2019-06-03 10:56 CST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00018s latency).
Other addresses for localhost (not scanned): ::1
PORT STATE SERVICE
1477/tcp open ms-sna-server
| ssl-enum-ciphers:
| TLSv1.0:
| ciphers:
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 1024) - A
| compressors:
| NULL
| cipher preference: server
| TLSv1.2:
| ciphers:
| TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 1024) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp384r1) - A
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp384r1) - A
| compressors:
| NULL
| cipher preference: server
|_ least strength: A
Nmap done: 1 IP address (1 host up) scanned in 1.63 seconds
SSL handshake concept:
https://support.f5.com/csp/article/K15292
openssl can help you test which SSL protocols your server is configured to use.
openssl
If a protocol is enabled, the openssl s_client command will wait for input (or Control-D).
If the protocol is disabled, openssl will report an exception similiar to the one reproduced below:
21112:error:1407F0E5:SSL routines:SSL2_WRITE:ssl handshake failure:s2_pkt.c:428:
Openssl examples:
openssl s_client -connect ihshostname:443 -ssl2
openssl s_client -connect ihshostname:443 -ssl3
openssl s_client -connect ihshostname:443 -tls1
#openssl s_client -connect www.google.com:443 -ssl3
CONNECTED(00000003)
23569:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number:s3_pkt.c:293:
#openssl s_client -connect localhost:1414 -cipher ECDHE-RSA-DES-CBC3-SHA
#openssl s_client -connect localhost:1414 -showcerts
#openssl ciphers ==> 列出openssl可用的cipher名稱, 以:分隔
**** perl one liner 可用在此處, 把原本用:分隔不易查看的資訊, 改以每筆一行的方式列出
#openssl ciphers|perl -ne 's/:/\n/g;print'
2. online website check tool
https://www.ssllabs.com/ssltest/
3. standalone test tool (TestSSLServer)
https://www.bolet.org/TestSSLServer/
4. IHS v8 or above version command:
Windows:
httpd -t -D DUMP_SSL_CONFIG
Linux:
apachectl -t -D DUMP_SSL_CONFIG
http://publib.boulder.ibm.com/httpserv/ihsdiag/ssl_questions.html#sslprotsupptest
5. use nmap to help to verify which cipherspec is supported by SSL server
nmap --script ssl-enum-ciphers -p port_number ip_address
# nmap --script ssl-enum-ciphers -p 1477 localhost
Starting Nmap 7.70 ( https://nmap.org ) at 2019-06-03 10:56 CST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00018s latency).
Other addresses for localhost (not scanned): ::1
PORT STATE SERVICE
1477/tcp open ms-sna-server
| ssl-enum-ciphers:
| TLSv1.0:
| ciphers:
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 1024) - A
| compressors:
| NULL
| cipher preference: server
| TLSv1.2:
| ciphers:
| TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 1024) - A
| TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 1024) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp384r1) - A
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp384r1) - A
| compressors:
| NULL
| cipher preference: server
|_ least strength: A
Nmap done: 1 IP address (1 host up) scanned in 1.63 seconds
Ref:
SSL 相關的測試工具
https://www.qa-knowhow.com/?p=3888SSL handshake concept:
https://support.f5.com/csp/article/K15292
標籤:
apachectl,
cipherspec,
command line,
handshake,
httpd,
IHS,
nmap,
one liner,
openssl,
perl,
SSL,
ssllabs,
sslv3,
TestSSLServer,
zenmap
星期三, 3月 15, 2017
Migrate Java of IHS 8 from 1.6 to 1.8
1. Can't directly migrate to Java 1.8 before fixpack 8.5.5.11
2. Must new install IHS 8.5.5.11 to have Java 1.8
4. To install IHS 8.5.5.11 with Java 1.8 using imcl command, you must add "-properties wasjava=java8" option
5. Will be able to migrate to 1.8 directly by applying fixpack 8.5.5.12
6. The incorrect core runtime information in the versionInfo output will be fixed in fixpack 8.5.5.12 (PI77304)
Installing Java SDK 8.0 on WAS 8.5.5.x
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/Installing_Java_SDK_8.0_on_WAS_8.5.5.x?lang=en
7. If you install IHS 5.5.5.11 (new install) using IM GUI (wizard mode), it will install Java 8 default (same as WAS). It is not necessary to add the option "-properties wasjava=java8" like imcl command line.
2. Must new install IHS 8.5.5.11 to have Java 1.8
4. To install IHS 8.5.5.11 with Java 1.8 using imcl command, you must add "-properties wasjava=java8" option
5. Will be able to migrate to 1.8 directly by applying fixpack 8.5.5.12
6. The incorrect core runtime information in the versionInfo output will be fixed in fixpack 8.5.5.12 (PI77304)
Installing Java SDK 8.0 on WAS 8.5.5.x
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/Installing_Java_SDK_8.0_on_WAS_8.5.5.x?lang=en
7. If you install IHS 5.5.5.11 (new install) using IM GUI (wizard mode), it will install Java 8 default (same as WAS). It is not necessary to add the option "-properties wasjava=java8" like imcl command line.
標籤:
EOS,
HttpServer,
IHS,
IM,
imcl,
install,
InstallationManager,
Java 1.8,
Java 8,
migrate,
versionInfo
訂閱:
文章 (Atom)
