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.

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

TLS enhancements #28

Open
1 of 2 tasks
ThePrez opened this issue Aug 7, 2024 · 3 comments
Open
1 of 2 tasks

TLS enhancements #28

ThePrez opened this issue Aug 7, 2024 · 3 comments

Comments

@ThePrez
Copy link
Collaborator

ThePrez commented Aug 7, 2024

Moved from checklist in ThePrez/WatsonX-SDK-Db2-IBMi#8

  • possibly fetch the server CA from DCM (low priority)
  • build and test a mechanism for manually-defined certificates
@ThePrez ThePrez added this to the Proper TLS handling milestone Aug 21, 2024
@ThePrez
Copy link
Collaborator Author

ThePrez commented Aug 23, 2024

#45 has a reworked mechanism for manually-defined certs

@richardschoen
Copy link

richardschoen commented Sep 1, 2024

Not sure if this matters since you really want people to use TLS1.3 but it looks like the server only offers up TLS1.3 or none for a TLS option.

This eliminates anything on the desktop older than Windows 11. Windows 10 maxes out at TLS1.2.

Not sure about MacOS or Linux use cases.

This may not be an issue if the intended usage in server to server app rather than desktop to server. But I wanted to note my findings/

@william-xiang
Copy link
Collaborator

@ThePrez Wondering if we need to change the way to obtain the FQDN of IBM i when generating the self-signed certificate. In some scenarios InetAddress.getLocalHost() does not return the correct FQDN. This depends on the network configuration of IBM i. These two issue below are related to this. #64 #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants