-
Notifications
You must be signed in to change notification settings - Fork 10
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
spaces are stripped from SNMP OctetStrings. #43
Comments
Also, de-compiling binary files with spaces in an Octetstring results in the following output:
|
Can you do a HexDump of the input file that is causing the above error and post it in the issues. |
It actually looks like it's something else that's causing the error, so I'm going to track that down some more (the original binary was created with a different compiler, no guarantee this isn't a bug with that compiler). I used a third compiler to create a new file from scratch, and I can decode (using oscar) with spaces intact, but when I encode (with oscar), the spaces get stripped. |
I will look into the spaces issue and treat the compiler error as a different issue, if it is a real issue. |
Found the reason for the compiler error. The compiler I used to create the original file was not padding the file with zero's. Let me know if you'd like more detail, but not a failing of the OSCAR compiler. The only thing would be for oscar to gracefully fail in this situation, but it shouldn't happen that often. :) |
Can you paste the hexdump of the Input file. |
Input file:
hexdump of input file:
hexdump of output file:
|
Spaces are being stripped from SNMP strings.
For example:
after compiling then de-compiling becomes:
The text was updated successfully, but these errors were encountered: