Sponsored Content
Top Forums UNIX for Beginners Questions & Answers SSL_ERROR_SYSCALL in connection to qa-api.ncl.com:443 Post 303011791 by Ayeesha on Tuesday 23rd of January 2018 06:17:57 PM
Old 01-23-2018
Actually before it was TLS1.0 , it was working fine and later endpoint server transition to TLS1.2 , from then onwards it is thrwoing errno 104.

I hope it's not firewall issue because in windows server and soap ui it's working fine.


openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013


Code:
 openssl s_client -showcerts -connect qa-api.ncl.com:443 -tls1_2
CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Key-Arg   : None
    Krb5 Principal: None
    PSK identity: None
    PSK identity hint: None
    Start Time: 1516749422
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
---

 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies

2. HP-UX

What is this error? 443?

# cat /var/log/messages | egrep -i "error|warn|critical|panic|exceed|alert|down|up" Jul 10 09:30:06 plbp1s nanny: shutting down 202.61.9.147:443 due to connection failure Jul 10 10:30:06 plbp1s nanny: shutting down 202.61.9.149:443 due to connection failure 443 is I understood it is port... (1 Reply)
Discussion started by: manalisharmabe
1 Replies

3. UNIX for Advanced & Expert Users

Google Translate API with wget (only one client and connection): Suspected Terms of Service Abuse

Hi Script > grep translate .bashrc translate(){ wget -qO- "http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&q=$1&langpair=$2|${3:-en}" | sed 's/.*"translatedText":"\(*\)".*}/\1\n/'; } error > translate "Ich will schwimmen" de en {"responseData": null,... (5 Replies)
Discussion started by: slashdotweenie
5 Replies

4. UNIX for Advanced & Expert Users

squid: Allow access to only one site and only via 80 or 443

Can someone please give me the conf file line to allow access to myexample.com and only that site, and only through http and https? So far I have only that site accessible via http, but all https sites are opened. Squid 3.1 on Cent 6 ---------- Post updated at 12:06 PM ---------- Previous... (0 Replies)
Discussion started by: glev2005
0 Replies

5. Solaris

Allow usage of port 80 and 443

I am trying to install Sun Java Web Server using an ordinary user with no root/sudo rights. I need to allow this web server to use ports 80 and 443. How can this be done?:confused: (1 Reply)
Discussion started by: emealogistics
1 Replies

6. Shell Programming and Scripting

Need to run an API from a script and extract fields from output of API

Hi, I need to call an API (GetUsageDetails)from inside a shell script which takes an input argument acct_nbr. The output of API will be like : <usageAccum accumId="450" accumCaptn="PM_125" inclUnits="1410.00" inclUnitsUsed="744.00" shared="true" pooled="false" prorated="false"... (1 Reply)
Discussion started by: rkrish
1 Replies

7. IP Networking

DNS requests through SSH/443

Anybody know how to force all DNS requests through port 443 or an SSH tunnel such as Putty in Ubuntu 10.4? (2 Replies)
Discussion started by: 3therk1ll
2 Replies

8. HP-UX

How to open 443 port in HP-UX?

Hello Experts, I want to open the port 443 on my HP-UX system. can you please help ? Thanks in advance. (1 Reply)
Discussion started by: purushottamaher
1 Replies

9. Cybersecurity

Continual knocking on port 443 from foreign IP address

Hello, I have a server in our DMZ that only has ports 80 and 443 open to the public networks. It runs webmail for our 10K employees' accounts. It's not necessary for our employees to access the server from anywhere except North America so I have blocked access from most of the world due to... (5 Replies)
Discussion started by: randomxs
5 Replies
SESS_ID(1SSL)							      OpenSSL							     SESS_ID(1SSL)

NAME
openssl-sess_id, sess_id - SSL/TLS session handling utility SYNOPSIS
openssl sess_id [-help] [-inform PEM|DER] [-outform PEM|DER|NSS] [-in filename] [-out filename] [-text] [-noout] [-context ID] DESCRIPTION
The sess_id process the encoded version of the SSL session structure and optionally prints out SSL session details (for example the SSL session master key) in human readable format. Since this is a diagnostic tool that needs some knowledge of the SSL protocol to use properly, most users will not need to use it. OPTIONS
-help Print out a usage message. -inform DER|PEM This specifies the input format. The DER option uses an ASN1 DER encoded format containing session details. The precise format can vary from one version to the next. The PEM form is the default format: it consists of the DER format base64 encoded with additional header and footer lines. -outform DER|PEM|NSS This specifies the output format. The PEM and DER options have the same meaning and default as the -inform option. The NSS option outputs the session id and the master key in NSS keylog format. -in filename This specifies the input filename to read session information from or standard input by default. -out filename This specifies the output filename to write session information to or standard output if this option is not specified. -text Prints out the various public or private key components in plain text in addition to the encoded version. -cert If a certificate is present in the session it will be output using this option, if the -text option is also present then it will be printed out in text form. -noout This option prevents output of the encoded version of the session. -context ID This option can set the session id so the output session information uses the supplied ID. The ID can be any string of characters. This option won't normally be used. OUTPUT
Typical output: SSL-Session: Protocol : TLSv1 Cipher : 0016 Session-ID: 871E62626C554CE95488823752CBD5F3673A3EF3DCE9C67BD916C809914B40ED Session-ID-ctx: 01000000 Master-Key: A7CEFC571974BE02CAC305269DC59F76EA9F0B180CB6642697A68251F2D2BB57E51DBBB4C7885573192AE9AEE220FACD Key-Arg : None Start Time: 948459261 Timeout : 300 (sec) Verify return code 0 (ok) Theses are described below in more detail. Protocol This is the protocol in use TLSv1.3, TLSv1.2, TLSv1.1, TLSv1 or SSLv3. Cipher The cipher used this is the actual raw SSL or TLS cipher code, see the SSL or TLS specifications for more information. Session-ID The SSL session ID in hex format. Session-ID-ctx The session ID context in hex format. Master-Key This is the SSL session master key. Start Time This is the session start time represented as an integer in standard Unix format. Timeout The timeout in seconds. Verify return code This is the return code when an SSL client certificate is verified. NOTES
The PEM encoded session format uses the header and footer lines: -----BEGIN SSL SESSION PARAMETERS----- -----END SSL SESSION PARAMETERS----- Since the SSL session output contains the master key it is possible to read the contents of an encrypted session using this information. Therefore appropriate security precautions should be taken if the information is being output by a "real" application. This is however strongly discouraged and should only be used for debugging purposes. BUGS
The cipher and start time should be printed out in human readable form. SEE ALSO
ciphers(1), s_server(1) COPYRIGHT
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved. Licensed under the OpenSSL license (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>. 1.1.1a 2018-12-18 SESS_ID(1SSL)
All times are GMT -4. The time now is 09:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy