Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

output example of tls-client application should change to reflect current output #250

Open
RonEld opened this issue Jun 10, 2019 · 14 comments
Open

output example of tls-client application should change to reflect current output #250

RonEld opened this issue Jun 10, 2019 · 14 comments
Labels
Found in OOB IOTOSM-3110 Jira status: OPEN mirrored

Comments

@RonEld
Copy link
Contributor

RonEld commented Jun 10, 2019

output example is outdated since the SAN and certificate policies printing have changed and should be updated to something like:

Starting mbed-os-example-tls/tls-client
Using Mbed OS 5.13.0
Successfully connected to os.mbed.com at port 443
Starting the TLS handshake...
Successfully completed the TLS handshake
Server certificate:
  cert. version     : 3
  serial number     : 0F:70:19:FD:F1:73:D0:E6:DF:CF:C9:31:AD:90:2A:26
  issuer name       : C=US, O=Amazon, OU=Server CA 1B, CN=Amazon
  subject name      : CN=*.mbed.com
  issued  on        : 2019-05-09 00:00:00
  expires on        : 2020-06-09 12:00:00
  signed using      : RSA with SHA-256
  RSA key size      : 2048 bits
  basic constraints : CA=false
  subject alt name  :
      dNSName : *.mbed.com
      dNSName : *.core.mbed.com
      dNSName : *.internal.mbed.com
      dNSName : *.pelion.com
      dNSName : *.mbed.org
      dNSName : mbed.com
      dNSName : core.mbed.com
      dNSName : internal.mbed.com
      dNSName : pelion.com
      dNSName : mbed.org
  key usage         : Digital Signature, Key Encipherment
  ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication
  certificate policies : ???, ???

Certificate verification passed
Established TLS connection to os.mbed.com
HTTP: Received 320 chars from server
HTTP: Received '200 OK' status ... OK
HTTP: Received message:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=36000
Content-Type: text/plain
Date: Mon, 10 Jun 2019 08:40:17 GMT
ETag: "5bf0036d-e"
Expires: Mon, 10 Jun 2019 18:40:17 GMT
Last-Modified: Sat, 17 Nov 2018 12:02:53 GMT
Server: nginx/1.15.6
Content-Length: 14
Connection: keep-alive

Hello world!


DONE
@ciarmcom
Copy link
Member

@RonEld thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

11 similar comments
@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 4, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 9, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Dec 5, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Found in OOB IOTOSM-3110 Jira status: OPEN mirrored
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ciarmcom @RonEld