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

SSL traffic encryption between OpenIM internal components does not take effect #3159

Open
caesar168 opened this issue Feb 24, 2025 · 1 comment
Open

SSL traffic encryption between OpenIM internal components does not take effect #3159

caesar168 opened this issue Feb 24, 2025 · 1 comment
Labels
bug Categorizes issue or PR as related to a bug. enhancement New feature or request

Comments

@caesar168
Copy link

OpenIM Server Version

3.8.3

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce

SSL traffic encryption between OpenIM internal components does not take effect, but traffic encryption between intranet services is still very necessary. It would be great if the project could support SSL...

Screenshots Link

No response
@caesar168 caesar168 added the bug Categorizes issue or PR as related to a bug. label Feb 24, 2025
@caesar168 caesar168 changed the title [BUG] $ Major bugs：binary openim-rpc-third is not running as expected: /home/vcs/open-im-server/_output/bin/platforms/linux/amd64/openim-rpc-third expected 1 processes, but 0 running SSL traffic encryption between OpenIM internal components does not take effect Feb 24, 2025
@FGadvancer
Copy link
Member

That's a good suggestion. We will add more security measures from a security perspective.

@FGadvancer FGadvancer added the enhancement New feature or request label Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Categorizes issue or PR as related to a bug. enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@caesar168 @FGadvancer