THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

snmp v3 not decoding properly [closed]

Running wireshark 3.0.2 (a new version for me), I have entered the snmp v3 username and credentials, same as I have successfully done on previous versions of wireshark, but I am getting "Decrypted data not formatted as expected". I have checked, double checked, and triple checked the credentials (even tried converting them to hex and entering them as hex strings), but it still doesn't work. Is there any known snmp v3 bug in the 3.0.2 release?

psellno's avatar
1
psellno
asked 2019-06-25 22:05:02 +0000
edit flag offensive 0 remove flag reopen merge delete

Closed for the following reason "the question is answered, right answer was accepted" by Guy Harris 2019-06-26 17:45:09 +0000

Comments

add a comment see more comments

2 Answers

0

My apologies, operator error, I had left off a digit on one of the passwords. It is working fine.

psellno's avatar
1
psellno
answered 2019-06-26 17:09:23 +0000
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments
0

If there is a known bug, it'll be in the Wireshark Bugzilla.

If there isn't one, please file one there; that, not the Q&A site, is the best place to report bugs.

If you think 3.0.2 isn't decrypting files that earlier versions did dissect - you might want to try installing an older version to see what it does with that file - then you probably have a bug to report.

If no version decrypts that particular capture, that might be a long-standing bug, or it might be an issue with the network traffic; the best way to get that resolved is to file a bug.

Guy Harris's avatar
19.9k
Guy Harris
answered 2019-06-26 01:23:55 +0000
edit flag offensive 0 remove flag delete link

Comments

Works fine for me (using SHA1 and AES) so be very specific in your bug report as to what you do and illustrate with a proper sample capture file (not screenshots!)

Jaap's avatar Jaap (2019-06-26 09:55:21 +0000) edit
add a comment see more comments