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

Proposal to allow MITM capability to be given #6

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

jfberry
Copy link
Contributor

@jfberry jfberry commented Apr 14, 2024

Introduce a capability flag which allows MITM to indicate their capability or make requests of controllers.

Implemented as an uint64 to be binary packed (assuming there may be more of these in future)
The suggested initial option is to allow disabling of fast user switching (i.e. return on jail), which is currently implemented with user agent matching.

Comments? This could equally be done with a series of bools so a bitwise flag may be premature optimisation

@jfberry
Copy link
Contributor Author

jfberry commented Apr 16, 2024

The more I think about this, the more I think a bitwise field is probably overkill. Does it really matter if we have 20 flags and this packet becomes 20 bytes longer? :-)
Thoughts from third parties welcome before I switch to a more obviously self-defining boolean

@na-ji
Copy link

na-ji commented Apr 16, 2024

The more I think about this, the more I think a bitwise field is probably overkill. Does it really matter if we have 20 flags and this packet becomes 20 bytes longer? :-) Thoughts from third parties welcome before I switch to a more obviously self-defining boolean

I was going to comment that bitwise is more than overkill, since it's only on the login proto. Having easy to use boolean would be better.
Also, the supports_compression boolean flag could be considered as a capability.

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

Successfully merging this pull request may close these issues.

2 participants