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

Please verify > get version -- machine identity seems published (MobaXterm setup) #276

Open
KP4AJ opened this issue Nov 12, 2023 · 3 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@KP4AJ
Copy link

KP4AJ commented Nov 12, 2023

Included three captures of the get version functionality. First capture from cygwin (new MobaXterm install methodology). Second from Get version old D-rats 3.10 beta 5 (included only for comparison purposes) the third from Ubuntu.

version-info
version-info-3-10-beta5
version-info-ubuntu

Version information should only provide platform without machine identity, IMO. Last, when I ran the get version from Ubuntu to Win 10 MSYS2 MINGW64 install I get 'No version response from X' (capture not included).

73'

Edfel
KP4AJ

@KP4AJ
Copy link
Author

KP4AJ commented Nov 12, 2023

Additional info: MobaXterm setup used was the installer version (not the portable).

Edfel
KP4AJ

@wb8tyw wb8tyw added documentation Improvements or additions to documentation question Further information is requested labels Nov 12, 2023
@wb8tyw
Copy link
Contributor

wb8tyw commented Nov 12, 2023

"Cygwin" is a different platform than MobaXterm embedded Cygwin as MobaXterm made significant changes in their implementation that affects scripts and program execution.

There are at least to version reports in D-Rats, an RPC get version and a ping reply.

The version report is part of the RPC protocols that we do not have full documentation for. For sending the report, a python dictionary is created and then passed through the RPC code for transmit. Something in that code serializes the data, and somewhere at this time, I do not know where receives that serialized data and converts it to a readable string.

Some clients are over some paths are not returning a version report, and that is something that I have not traced down yet.

It is very possible that a something is broken in the serialization and deserialization code. Until we capture byte level traces of good and bad transfers, it may be hard to fix.

Unfortunately while the "sniff" and "raw" text settings should provide this data, in practice, they do not always provide all that is needed in a usable form.

@KP4AJ
Copy link
Author

KP4AJ commented Nov 12, 2023

Thanks John.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants