-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
MITM functionality #164
Comments
For this the encrypted packets of minecraft (newer versions) must be decrypted, changed and then re-encrypted. This would be difficult to implement in infrared (many different packets etc.). I may be wrong, but from what I can remember, this is correct. |
I'm not sure what you mean by brand name. Do you mean the version name shown in the server status? |
As in the thing you see when you press F3
…------- Original Message -------
On Wednesday, January 18th, 2023 at 20:18, Hendrik Schlehlein ***@***.***> wrote:
I'm not sure what you mean by brand name. Do you mean the version name shown in the server status?
—
Reply to this email directly, [view it on GitHub](#164 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ARB37VBR7SXXJSB7JE6MUTLWTA6W5ANCNFSM6AAAAAAT2UYIWE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sorry, but that is not possible without breaking encryption. I could add a feature to make Infrared function as a MITM proxy in the future, but currently it breaks how Infrared works. |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. E.g.: "I'm always frustrated when [...]"
Not really a problem, but It'd be neat to be able to modify the brand name of the server sent to the client.
Describe the solution you'd like
A clear and concise description of what you want to happen.
A config option to change the brand name passed through to the client, with a placeholder for the existing brand name.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
There aren't really any alternatives
Additional context
Add any other context or screenshots regarding the feature request here.
Not much
The text was updated successfully, but these errors were encountered: