[Feature] Add version blocking that does not support secure-profile
Open
Nobody has claimed this yet.
type: feature
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
force-key-authentication = true
With this config, players should not be able to connect without a secure-profile, but versions below 1.19 can connect to Velocity without a secure-profile.
Add a feature to the config that blocks versions that do not support secure-profile.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handling for force-key-authentication and the protocol version negotiation or connection checks. Confirm how secure-profile support is identified for client versions below 1.19. Done means the configuration blocks unsupported versions without a secure-profile while preserving connections from supported versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100