viaversion / viaaas Goto Github PK

currently packet registry is using an horrible O(n)

May prevent some abuse and help detect bugs in translation/codecs

https://wiki.vg/Microsoft_Authentication_Scheme

This would centralize the localstorage for multiple VIAaaS instances

may prevent session hash collision when AES key is reused in the same server?

Idea: using a https connection for logging in, so we can just keep the code without PLAY state listening

I personally wouldn't trust it, but...

• add multiversion packet decoding

• refactor connection to connect when frontend state is PLAY

• basic PLAY packets (chat, join game, empty chunks...)

• warn about remote login and mojang blocking accounts

• todo: what does happen if server responds with different UUID or username???

Currently the README.md doesn't list any information on how to test this out.

I've run ./gradlew and can create releases just fine.

However, when it comes to testing VIaaS currently when connecting it just floods open a bunch of UDP ports between the minecraft client and VIAaaS.

I'm aware this is probably incomplete, but I'm interested and code comments aren't helping much.

Something like viaaas:request_auth with the session hash for client signing it

Changing it will prevent bad login in web browser with same account, but will cause bad login when the client connect to next server.

• only add handlers when needed, making pipeline shorter
• merge crypto, framing, compression and cross version translation encoders + decoders into codec handlers?
• do not use replayingdecoder

Needs refactoring packet encoding and decoding

There was a case which secure random was blocking and making VIAaaS not work

• Idea 1: Limbo server which the player connects to manage the Minecraft accounts, like auth.viaaas.localhost
• Idea 2: Login plugin messages viaaas:request_auth
• Idea 3: Chat? Insecure?
• Idea 4: Command-line JAR?