Add lazy loaded CRC keys to cache interface for use in login protocol

[titandino]

Feel free to close if it's already implemented somewhere or not planned on being supported, but I didn't see any place where the client's CRCs are validated on login anywhere. Does 667 just not send these values or are they currently just being skipped on the login protocol?

[GregHib]

Hey, yeah Void is skipping the lobby login using two client changes and so doesn't need CRCs as they're only part of the lobby login protocol.

[titandino]

Gotcha gotcha!

…

On Wed, Mar 19, 2025, 5:30 PM Greg ***@***.***> wrote: Hey, yeah Void is skipping the lobby login using two <https://github.com/GregHib/void-client/blob/72fabcdc715b063a4fc7a22d1b66d811898a7ed9/client/src/Class14_Sub4.java#L216> client changes <https://github.com/GregHib/void-client/blob/025e51d0f540fc9c9ebb50fd42ac4507fe43c423/client/src/Class151.java#L75> and so doesn't need CRCs as they're only part of the lobby login protocol. — Reply to this email directly, view it on GitHub <#622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2EWHJZY4D2RRBLVJLXLYT2VID4DAVCNFSM6AAAAABZGQ2SK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGY2DMOBVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: GregHib]*GregHib* left a comment (GregHib/void#622) <#622 (comment)> Hey, yeah Void is skipping the lobby login using two <https://github.com/GregHib/void-client/blob/72fabcdc715b063a4fc7a22d1b66d811898a7ed9/client/src/Class14_Sub4.java#L216> client changes <https://github.com/GregHib/void-client/blob/025e51d0f540fc9c9ebb50fd42ac4507fe43c423/client/src/Class151.java#L75> and so doesn't need CRCs as they're only part of the lobby login protocol. — Reply to this email directly, view it on GitHub <#622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2EWHJZY4D2RRBLVJLXLYT2VID4DAVCNFSM6AAAAABZGQ2SK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZYGY2DMOBVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>