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.

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

Is it possible to hide protocol field names #70

Open
romanholidaypancakes opened this issue Jun 27, 2022 · 4 comments
Open

Is it possible to hide protocol field names #70

romanholidaypancakes opened this issue Jun 27, 2022 · 4 comments

Comments

@romanholidaypancakes
Copy link

image

image

We are using protobuf now, it will keep the protocol in binary, it can almost restore the protocol, I noticed that FastBinaryEncoding also has this problem, I hope not to keep any related strings with the protocol declaration

@chronoxor
Copy link
Owner

You can annotate field as [Hidden]:
image

And its output will be ***:
image

@romanholidaypancakes
Copy link
Author

image
The field names remain in the source code, and as long as you are familiar with fbe, you can still infer the message structure through reverse engineering

@chronoxor
Copy link
Owner

chronoxor commented Jun 30, 2022

Ok, as I understand you want to have 'transparent' fields that are present in objects/clases, but not serializable/deserializable and not output in logger/std::streams. Am I right?

When deserialzed this fields are skip and contain default or prev value.

Something like [NonSerialized] attribute in .NET:
image

@romanholidaypancakes
Copy link
Author

No, serialization/deserialization is still supported, you can check flatbuffers or capnproto (they generate source code that doesn't keep any strings), just to protect data don't want any message interface strings to be preserved in source code. Because once retained it can be easily reverse engineered, which is especially important in our game, where we want to hide the message structure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants