fix: enhance authentication logging and improve server IP handling in FFI Client #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enhances the authentication process in the VPN client by adding detailed logging throughout the authentication flow and improving type safety for FFI operations. The main focus is on making the authentication process more transparent and easier to debug by reporting key events and errors via callback-based logging.
Authentication process improvements:
callbacksparameter to theauthenticatefunction and its callers, enabling logging of important events and errors during authentication. Log messages now report the authentication type, password hash decoding steps, network operations, server responses, and error situations. [1] [2] [3] [4] [5]FFI and type safety improvements:
server_ip_strarray increate_session_from_authto usestd::ffi::c_charfor improved FFI compatibility and type safety.… FFI client