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

It is possible to communicate as TLs1.3 client? I want to test my TLS1.3 custom server[IDEA] #369

Open
NataliaAR22 opened this issue May 21, 2024 · 2 comments
Assignees

Comments

@NataliaAR22
Copy link

Desktop, Mobile, Command Line?
Where will this feature exist?

Describe your idea
A clear and concise description of what you want to happen.

@NataliaAR22
Copy link
Author

It would be very useful a Desktop solution to be able to communicate as a client and or sever.
Adding an option for selecting TLS1.2 or TLS1.3.
A second option where it could be possible to add the certificates.
An option similar to the actual one for being able to select the IP address and Port to communicate
Captura de pantalla 2024-05-23 094932
And a place to add the packet to send as the ASCII or HEX box..

@dannagle
Copy link
Owner

Thanks for opening this issue.

This screenshot looks like you are using Windows. Packet Sender for Windows uses OpenSSL which can send TLSv1.3. You can go to Help --> About, and then you can see the OpenSSL (or native SSL for other installations) library in use.

The currently shipping one inside Packet Sender is v3.0.7, which does support TLSv1.3. If you are looking for specific cipher suites, you can browse the changelog here: https://www.openssl.org/news/changelog.txt

If you want to manipulate the certificates used by Packet Sender server, cert.pem and key.pem can be found at %LOCALAPPDATA%\PacketSender\

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

2 participants